Approvals - Student Guide - 19D

Oracle HCM Cloud: Workflows
and Approvals
Student Guide
D105457GC10 | D105658
Learn more from Oracle University at education.oracle.com

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may
copy and print this document solely for your own use in an Oracle training course. The document may not be modified or
altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download,
upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in
part without the express authorization of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document,
please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This
document is not warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the
United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are
restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
130811201919D
Contents
1 Course Overview
Lesson Objectives 1-2
Course Objectives 1-3
Course Agenda 1-4
Information Resources 1-5
2 Approval Management Overview

Learning Objectives 2-2
HCM Approval Management: Overview 2-3
Approval Workflow: Overview 2-4
Roles for HCM Workflow Access 2-5
Approval Policies 2-6
Approval Workflow 2-7
Approval Transactions Explained 2-8
Summary 2-9
3 Approval Rules Configuration

Approval Rules: Overview 3-3
Parts of an Approval Rule 3-4
IF Statements 3-5
THEN Statements 3-6
Creating an Approval Rule 3-7
Configuring IF Conditions 3-8
Adding Rule Conditions 3-9
Approval Attributes 3-10
Worker’s Current Assignment Attribute 3-11
Combining Multiple Rule Conditions 3-12
Condition Details: Views 3-13
Adding Approvers 3-14
Configuring Approver Settings 3-15
Demonstration 3-16
Summary 3-17
iii
4 Approver Types
Approver Types 4-3
Management Hierarchy 4-4
Configuring Management and Line Manager Hierarchy 4-6
Job-Level Based Line Manager Hierarchy 4-7
Position Hierarchy 4-8
Users 4-9
Representatives 4-10
Application Role 4-11
Approval Groups 4-12
Demonstration 4-13
Summary 4-14
5 Oracle BPM Worklist

Configuring BPM Worklist 5-3
HCM Approval Management in Oracle BPM Worklist 5-4
Roles and Rights for Approving Tasks 5-5
Task Aggregation 5-7
Assignment and Routing Policy 5-8
FYI Notifications in BPM 5-9
Notification and Reminder Settings 5-10
Modifying Approval Rule: BPM Worklist 5-11
Rule Sets 5-12
Setting the Transaction to Automatically Approve 5-13
Configurations in the Notifications Tab 5-14
Demonstration 5-15
Summary 5-16
6 Approvals and Notifications

Approval Notifications 6-3
Demonstration 6-4
FYI Notifications 6-5
Configuring Approval Notifications 6-6
Configuring Notifications Based on Reports 6-7
Generating Report-Based Notifications 6-8
Notification Setup for BI Publisher 6-9
Demonstration 6-10
Summary 6-11
iv
7 BPM Worklist and Transaction Console
BPM Worklist – Administrator Options 7-3
BPM Worklist – User Views 7-4
Demonstration 7-5
Transaction Console Transaction Manager: Transactions 7-6
Transaction Console Transaction Manager: Rules 7-7
Archiving and Purging Workflow Tasks 7-8
Vacation Rules 7-9
Demonstration 7-10
Administrator Capabilities - Reassigning a Task 7-11
Summary 7-12
8 Alert Notifications
Alerts Overview 8-3
Alert Composer 8-4
Functions and Groovy Expressions 8-5
Viewing Alerts History 8-6
Alerts Composer Security 8-7
Demonstration 8-8
Summary 8-9
v
1
Course Overview

Lesson Objectives
• Identify the purpose of this course

• Describe the course training approach
Oracle HCM Cloud: Workflows and Approvals 1 - 2

Course Objectives
After completing this lesson, you should be able to:

• Describe Approval Management
• Create Approval Rules
• Describe a Predefined Rule
• Describe Approver Types
• Describe Oracle BPM Worklist
• Explain Approvals and Notifications
• Understand Alert Notifications

Course Agenda
• Approval Management Overview

• Approval Rules Configuration
• Approver Types
• Oracle BPM Worklist
• Approvals and Notifications
• Tasks in BPM Worklist and Transaction Console
• Alert Notifications

Information Resources
Oracle Help Center My Oracle Support Oracle University

Search for solutions
Cloud Readiness/What’s New Training
Download patches and updates
Human Resources Certification
Create a Service Request
Oracle Launchpad
HCM Cloud Common Features Collaborate in the My Oracle Support
Community Essential Training
REST API – Human Resources
Best Practice
Books and Videos 24/7 digital learning experience
Using Global Human Resources Oracle Cloud Customer Oracle Cloud Learning
Connect Subscription
Implementing Global Human
Resources Discussion Forums Training Videos
Idea Labs Certification Exams
Creating and Administering Analytics
and Reports for HCM Updates and Maintenance 24/7 digital learning experience
Events Calendar
Disclaimer: Oracle customers have access to various resources. If you are not a customer, you may not
have access to some of the additional resources referenced in this course.
Oracle Help Center HCM Global Human Resources documentation
https://docs.oracle.com/en/cloud/saas/global-human-resources/19d/faigh/index.html
All White Papers for Fusion HCM on My Oracle Support
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1504483.1
Oracle Cloud Customer Connect https://cloudcustomerconnect.oracle.com/pages/home
Oracle University
• Oracle Launchpad http://education.oracle.com/launchpad
• Oracle Cloud Learning Subscription http://education.oracle.com/cloud
Additional Resources:
• Oracle Product Features:
- You can use the Oracle Product Features tool to compare release features prior to an
upgrade https://apex.oracle.com/pls/apex/f?p=24153:100:100491633520435
• Oracle HCM Cloud Courses: https://education.oracle.com/oracle-cloud-saas
- Using Global Human Resources
- Configure Enterprise and Workforce Structures

2
Approval Management Overview

Learning Objectives
• Understand approval workflow

• Describe approval policies
• Explain approval transactions

HCM Approval Management: Overview
To manage approval processes, • The key components that are used in

Oracle HCM Cloud Applications approvals include:
uses the approval-management
extensions of Oracle Service Oracle SOA
Oriented Architecture (SOA) Suite Approval
Management
human workflow services. Extensions
Oracle
Business Oracle
Human
Process Capital
Management Management
(BPM)
• Oracle SOA Approval Management Extensions (AMX)

- AMX enables you to define complex, multi-stage, task routing rules for business documents.
• Oracle Business Process Management (BPM)
- The BPM Worklist is a web-based application that enables you to access the tasks assigned
to you and perform actions based on your roles in the approval process.
- The Business Process Owner also sets up and manages approval rules by using the BPM
Worklist Application.
• Oracle Human Capital Management
- AMX integrates with the setup in Human Capital Management to derive the supervisory and
position hierarchybased approvers.

Approval Workflow: Overview
• Workflows are processes in which tasks are routed automatically among users for
consideration or action.
Example: A promotion request for a worker may require approval from two levels of the
manager hierarchy above the task submitter.
First Approver
Task Submitter
Final Approver
Task Approved
• The tasks are routed in a defined sequence to achieve a defined result.

• Workflow tasks for a user appear in the Worklist: Notifications and Approvals work area; the user
also receives an email notification.

Roles for HCM Workflow Access
Predefined roles provide access to workflow functionality.

• Users with these roles can set up approval rules and manage submitted approval tasks.
• If required, you can assign the predefined BPM role to a custom job role.
BPM Role Name BPM Role Code Inherited by Job Role

BPM Workflow Human Capital BPMWorkflowHCMAdmin Human Capital Management Application
Management Administrator Administrator
The table identifies the predefined Oracle Business Process Management (BPM) role for HCM workflow
access and the predefined job role that inherits it.

Approval Policies
• These policies determine the workflow events.

• They include:
– Who approves the transaction
– By when the approver should approve the transaction
• Use these tasks on the Setup and Maintenance page to manage approval policies:
– Manage Approval Transactions for Human Capital Management
– Manage Task Configurations for Human Capital Management
• Predefined approval policies exist for many HCM tasks.
– Tasks with no predefined approval policies are approved automatically.
• Approval Policies:
- In most cases, approval by the requester's first-level and second-level managers is required.
- For some tasks (for example, some absences-related tasks), approval by only the first-level
manager is required.
- For the Share Information task, approval by the employee whose information is shared is
required, if the task is performed by a manager or Human Resource Specialist.
• Typically, approval notifications are issued to:
- Employees to whom an approval task is assigned, when the task is assigned
- The employee who submitted the task, when the approval process completes

Approval Workflow
The figure shows a two-level approval flow:
• When a transaction is submitted, it is routed automatically to the worklist of the submitter's first-level
manager, who is the first approver.
• If the submitter's first-level manager approves the transaction, the transaction is routed automatically
to the submitter's second-level manager, who is the second approver.
• If the submitter's second-level manager approves the transaction, the transaction is committed to the
database tables.
• Either approver can reject the transaction. By default, the approval process stops when the
transaction is rejected.
• Security permitting, either approver may edit the transaction.
A link to edit the transaction is included in all notifications by default; however, the link can be hidden
by using personalization.
• The second-level manager can push the transaction back to the first-level manager, who then has a
second opportunity to review the transaction and either approve or reject it.
• Approvers can delegate their approval responsibilities to other approvers.

Approval Transactions Explained
The Manage Approval Transactions task manages transactions and rules.
Configuring Approval Policies: For a selected task, configure the approval policy by:
• Arranging approvers in the required order
• Defining approval rules for each approver
• Submitting the approval policy
The approval policy takes effect immediately and supersedes the current approval policy for the selected
task.
Failed Processes: For example, an approval process might fail if there is:
• A network outage
• A database outage
• An issue in setting up approval rules
For failed processes, you can:
• View the error message generated in the application
• Withdraw the process to cancel it. The user can begin the flow again.
• Configure the approval rules and submit the process.
Pending Processes
Processes that wait for approval
Approvals Bypassing
To bypass approvals, on the Manage Approval Transactions page, select the Bypass Approvals check box.

Summary
• Understood approval workflow

• Described approval policies
• Explained approval transactions

3
Approval Rules Configuration

Learning Objectives
• Configure approval rules, conditions, and approvers.

• Create conditions by using:
– Attributes
– Attribute values
• Combine conditions by using logical operators.
• Arrange approvers in the required sequence by dragging and dropping the approvers

Approval Rules: Overview
• Approval rules determine a transaction’s • Use the Manage Approval

approval process. Transactions for Human Capital
• You can configure multiple approval Management task to:
rules for a transaction. – Specify one or more approval rules
for each approver type
– Create more than one approval
rule. You either add a rule or
duplicate a selected rule and edit it
as appropriate.
– Create multiple approval rules for
an approver. Multiple approval rules
are evaluated individually in an
undefined order.
Note: If you edit or delete an approval rule on the Manage Approval Rules page, the approvals currently in
progress complete as if the rule had not been edited or deleted. New approvals follow the latest version of
the rule.

Parts of an Approval Rule
Approval rules comprise one or more IF statements and one THEN statement. An approval
rule has the following parts:
• IF conditions determine when an approval rule takes effect.
• THEN statements determine the approvers.
IF
{Workers’ Department = Sales}
Attributes AND Conditions
{GRADE = 3}
THEN
Supervisory Level – Require approvals up to the second level Manager
Action Type Action
IF Conditions
• Combine multiple IF statements by using logical operators.
• If you join multiple statements with the AND operator, all statements must be true before the
approval rule takes effect.
• If you join multiple statements with the OR operator, only one of the statements must be true before
the approval rule takes effect.

IF Statements
• IF statements determine:
– When an approval rule takes effect. For example, you could specify that an approval
rule for a promotion takes effect when the employee's department is Sales or the
employee's job is Area Manager.
– The values in the IF statement are those belonging to the employee's proposed
assignment.
• You can specify multiple IF statements:
– If you join multiple statements with and operators, then all statements must be true
before the approval rule takes effect.
– If you join multiple statements with or operators, then only one of the statements must
be true before the approval rule takes effect.

THEN Statements
Approval Description
THEN statements specify:
Action
Approval Notifications are issued to the identified
Required approvers and their response is required.
• Who the approvers are
Automatic No notifications are issued to the identified
• What actions approvers can take Approval approvers. The transaction is either approved
or rejected automatically, and the approvers
are recorded as having approved or rejected
The table summarizes the approval the transaction. The value of the Set Outcome
To attribute for manager hierarchies
actions determines whether the transaction is
approved or rejected.
FYI only Notifications are issued to the identified
approvers, but no response is expected.
No approval No notifications are issued and no approval is
required recorded for the transaction.
THEN statements determine:

• How individual approvers of the specified type are identified
• Any actions that approvers are expected to take
How individual approvers are identified depends on the approver type. For example, if the selected approver
type is a project manager hierarchy, the THEN statement determines:
• How the project manager hierarchy itself is identified
• How the first approver in the manager hierarchy is selected
• How many levels of the manager hierarchy above the first approver are included
• Available attributes and default values, if any, vary with the approver type

Creating an Approval Rule
Search for the Create an

transaction. approval rule.
Configure Rule
Add approvers.
Parameters.
Configure the Configure the IF

THEN statement. condition.
Define Rule Add Rule
Parameters. Conditions.
Use the Manage Approval Transactions for Human Capital Management task to configure approval
policies for HCM tasks such as Hire or Promote.
1. On the Manage Approvals Transactions page, search for the transaction, such as Promote, and click
Configure.
2. On the Manage Approval Rules page, click the + icon to create a new rule.
Note: You can edit an existing rule to update the existing IF conditions and THEN statements.
3. Add and select the IF condition to:
- Configure rule parameters such as Rule Name, Active, and Priority
- Add the rule conditions
4. Add and select the THEN statement to add and configure approvers.

Configuring IF Conditions
Click the rule box to Search for the Create an approval

transaction rule
configure the rule options.
Configure Rule
Add approvers
Configure the THEN Configure the IF Parameters
statement condition
Customize Rule Add Rule

Parameters Conditions
Determines the order Configure conditions for the

in which rules are run rules by using relational
operators and expressions.
On the Manage Approval Rules page, click the Rule1 oval to configure:
• The Status and Priority of the approval rules
• The rule conditions
Priority
• Within a rule set, higher priority rules run before lower priority rules.
• The default priority is Medium.
Status
• Represents the status of the approval rule

Adding Rule Conditions
• Create conditions by using: Search for the

transaction
Create an approval
rule
– Attributes
– Operators Add approvers
Configure the THEN
statement
Configure the IF
condition
Configure Rule
Parameters
– Attribute values Customize Rule

Parameters
Add Rule
Conditions
• The list of attributes is different for

different transactions.
• Select only those attributes that have
meaningful names.
1. On the Manage Approvals Rule page, select the Rule 1 oval and click Configure Rule Conditions
to open the Condition Details dialog box.
2. Select the 1=1 rectangle and click Edit Selection to open the Approval Rules: Edit Condition
Expression dialog box.
3. Select an attribute. Attributes are grouped into categories.
For example, to select the requestor’s department:
- Click the Select An Attribute choice list
- Click Requestor’s Assignment and Department
4. Select an operator, such as ==, !=.
5. Select one of the following:
- Select from attribute: Compares an attribute with another attribute. The list of values is
filtered based on the selected attribute.
- Select from LOV: Compares an attribute with a value selected from a LOV if a predefined list
of values has been provided for that attribute. The list of values is filtered based on the
selected attribute.
- Enter a Value: Allows you to enter a value. Always enter values within double quotation
marks.

Approval Attributes
Grouped into the following categories:

Attribute Category Commonly Used Attributes
Requestor’s Assignment Business Unit, Department
Requestor’s Role Details Role Name
Worker’s Current Assignment Business Unit, Department
Worker’s Other Compensation Details Stock Plan
Worker’s Proposed Assignment Business Unit, Department
Worker’s Role Details Role Name, Status
Worker’s Salary Component Details Current Change Amount, Proposed Changed Amount
Worker’s Salary Details Current Annual Salary, Proposed Annual Salary
Requestor’s Assignment: Includes attributes that describe the assignment of the person that initiated the
approval request
Requestor’s Role Details: Includes attributes that describe the role of the person that initiated the approval
request
Worker’s Current Assignment Details: Includes attributes that describe the current work assignment of
the worker
Worker’s Other Compensation Details: Includes attributes that describe the compensation details
Worker’s Proposed Assignment: Includes attributes that describe the proposed assignment of the worker
Worker’s Role Details: Includes attributes that describe the current role of the worker
Worker’s Salary Component Details: Includes attributes that describe various salary components of the
worker
Worker’s Salary Details: Includes attributes that describe the salary of the worker

Worker’s Current Assignment Attribute
• Grouping of attributes that describe a worker’s current assignment

• Examples:
– Assignment Number
– Department
– Grade
– Location
– Position
– Worker Type
For example: Construct an IF condition by using the following Worker's Current Assignment Attributes:
• IF Worker's Current Assignment.Location = "Chicago" and Worker's Current Assignment.Department
= "Sales”

Combining Multiple Rule Conditions
• Combine conditions by using logical operators.

• <<Condition 1>> <<Operator>> <<Condition 2>>
Search for the Create an approval
transaction rule
Configure Rule
Add approvers
statement condition
Customize Rule Add Rule

Parameters Conditions
2 3 1
Click the rectangle and

click Edit Selection.
To combine multiple rule expressions:

1. In the Condition Details dialog box, select the 1==1 rectangle and click Edit Selection. As described
in the previous slide, create conditions by using a combination of attributes, operator, and attribute
value.
2. Select the rectangle and click a logical operator to add the operator to the left side of the expression.
- You can select one of the following operators: AND, OR, and NOT.
3. Select the logical operator oval and click Add Expression to add another expression.

Condition Details: Views
• Use one of the following views to add conditions:

– Chart Builder (Default View)
– Block Builder
The Chart Builder view is the default view. Adding conditions in the Block Builder view is similar to adding
them in the Chart View.
To configure conditions in the Block Builder view:
1. In the Block Builder view, select the 1==1 rectangle and click Edit Selection to open the Approval
Rules: Edit Condition Expression dialog box.
2. Select an attribute. Attributes are grouped into categories.
3. Select an operator, such as ==, !=.
4. Select one of the following: Select from attribute, Select from LOV, or Enter a Value.
5. Select the rectangle and click a logical operator to add the operator to the left side of the expression.
6. Select the logical operator oval and click Add Expression to add another expression.
To delete conditions in the Block Builder view, drag and drop the conditions to the recycle bin.

Adding Approvers
On the Manage Approvals Rules page, select the THEN oval and:
• Add approvers for a task
• Arrange approvers in the required sequence
• Define approval settings for each approver
Search for the

Create an approval rule
transaction
Customize Rule
Add approvers
statement condition
Configure Rule
Add Rule Conditions
Parameters
Arrange approvers in the required sequence by dragging and dropping the approvers.
Add the following types of approvers:
• Management hierarchy
• Users
• Approval groups
• Position hierarchy
• Representatives
• Application role
• Job-level based line manager hierarchy
• Self auto approve

Configuring Approver Settings
The following figure describes the values that you specify in the THEN statements of
approval rules for position hierarchy.
Indicates the number of job

Indicates all position
levels that are required to
hierarchies in the enterprise
perform the approval action
Identifies the first Indicates the top person in the Indicates the list of approvers
approver in the list approval chain, usually the CEO that will be included
Action Type
Select one of the following action types:
• Approval required: Notifications are issued to the identified approvers and their response is
required.
• Automatic approval: No notifications are issued to the identified approvers. The transaction is
either approved or rejected automatically, and the approvers are recorded as having approved or
rejected the transaction.
• FYI only: Notifications are issued to the identified approvers, but no response is expected.
• No approval required: No notifications are issued and no approval is recorded for the transaction.
Minimum Job Level
• Approvals are routed to approvers between the initial and topmost approvers in the position
hierarchy based on this value.
• Approval routing stops when either the number of job levels or the topmost approver is reached,
whichever is sooner.
Include:
• Indicates if all approvers will be included, the first and last approver from the list will be included, or
only the last approver will be included
Starting Position and Top Position
• An approval notification is sent to all workers who have the position, and the transaction is approved
by the first worker to approve.

Demonstration
• 3-1: Reviewing the Promotion Approval Rule

Summary
• Configured approval rules, conditions, and approvers

• Created conditions by using:
– Attributes
– Attribute values
• Combined conditions by using logical operators
• Arranged approvers in the required sequence by dragging and dropping the approvers

4
Approver Types

Learning Objectives
• Explain Approver Types

• Create an Approval Group

Approver Types
• Include any number of approvers in the approval sequence.

• Drag and drop approvers into the approval flow.
Approver Types
Management Job
Application Roles Approval Groups Position Hierarchy Representative Self Auto Approve User
Hierarchy Level
HR
Line Manager
Representative
Resource Benefits
Manager representative
Union
Project Manager
representative
Payroll
Regional Manager
representative
You can add the following types of approvers:

• Application Roles: If your enterprise defines duty roles for security purposes, you can enter the
duty role to include it in the approval sequence. A duty role is assigned to several users.
• Approval Groups: Select an approval group, which consists of a predefined set of approvers
configured to act on a task.
• Management Hierarchy: Include the predefined managers in the sequence, for example, Project
Manager.
• Position Hierarchy: Add position holders. For positions with more than one position holder, the
transaction is approved by the first position holder to approve.
Representative: Include one of the predefined responsibilities in the approval sequence. Include
workers with assigned responsibilities, for example Benefits Representative.
• Job Level Based Line Manager Hierarchy: Include a job level in your approval sequence.
• User: Include one or more Oracle Fusion Applications users in the approval sequence.
Note: Only the Manage Approval Transactions interface supports Position Hierarchies and
Representatives; BPM Worklist does not support them.

Management Hierarchy
You can set up approvals using the employee supervisory hierarchy. You must set up
employee with appropriate job and supervisors such as:
Line Manager Resource Manager
Project Manager Regional Manager
Note: If your enterprise defines additional types of managers, then they appear automatically in the
Approvers section of the Manage Approval Rules page; You can include them in the approval sequence.
A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up
in a management hierarchy.
The hierarchy type defined for the plan determines the approvals hierarchy. You can create an alternate
approval hierarchy for a manager that overrides the plan hierarchy.
You can also specify:
• Approvals in a different sequence
• Approvals by different people
• When managers can submit their worksheets for approval
• When they can approve their lower managers' worksheets

You can set up employees with appropriate jobs and supervisors.

An example of an employee-supervisor approval structure is as follows:
• Mary Walton, Administrator Assistant reports to
• Pat Stock, Manager, reports to
• Casey Brown, Director
Casey Brown Director
Pat Stock Manager
Mary Walton
Administrator

Configuring Management and Line Manager Hierarchy
Controls how far up in the management The starting participant in
hierarchy approval requests are sent the approval hierarchy
Specifies an approver
above whom approvals
are not routed
Contains a list of
approval routes
Indicates the number of job levels
that are required to perform the
approval action if the rule applies
Contains a list of
approval participants
• Action Type
- Approval required: Notifications are issued to the identified approvers and their response is
required.
- Automatic approval: No notifications are issued to the identified approvers.
- Information only: FYI only notifications are issued to the identified approvers, but no
response is expected.
• Number of Levels: The first level is based on both the Initial Approver and the Initial Approvers
to Skip values.

Job-Level Based Line Manager Hierarchy
You can include a job level in your approval

sequence.
Job level routings are based on the
manager hierarchy defined in Oracle Human
1. Manager
Capital Management. The approval list is
2. Senior Manager
generated based on the starting level 3. Director
specified in a rule and continues until an 4. Senior Director
approver with a sufficient job level is found. 5. Vice President
The approval flow uses the job level defined Manager Hierarchy
in the Manage Jobs interface. Example

Position Hierarchy
You can use position trees in approvals. An example of a position hierarchy approval
structure is as follows:
• Store Manager reports to
• Regional Manager reports to
• General Manager
General Manager
Regional Manager
Store Manager
• To use position trees:

- The position hierarchy must be already defined
- The workers must be assigned corresponding positions
• When using position trees in approvals, you cannot reference the position of a requester or worker
as the starting point to route the approvals. However, you can use a position tree, and select
positions within that tree to route an approval. For example, you can select the position “Works
Council” as an approver for all promotions.

Users
You can include one or more Oracle HCM Cloud users in the approval sequence. You can
include any number of approvers of various types in your approval sequence by dragging
and dropping them into the approval flow.
You can configure

users in this section

Representatives
You can include holders of the following predefined responsibilities in your approval
sequence:
Human Resources Benefits

Representative Representative
Payroll
Union Representative
Representative
If your enterprise defines additional responsibility types, then they appear automatically in the Approvers
section of the Manage Approval Rules page. You can include them in the approval sequence.
Human Resource (HR) Specialists assign responsibilities to workers using the Manage Areas of
Responsibility task. A worker becomes an approver for a transaction if they have responsibility for the
transaction subject. For example, if you specify the Benefits Representative as an approver for a promotion,
then the Benefits Representative of the employee who is being promoted is invited to approve the
promotion.
Note: If you use a responsibility holder, then ensure that responsibility holders are already defined in the
application. For example, if you include an HR representative as an approver for an employee process, then
all employees must have HR representatives assigned to them.

Application Role
• Any existing duty roles can be included in the approval sequence.

• Users with a Job or Data Role tied to the Duty Role become transaction approvers.
• Drag and drop or click on the plus icon to add approvers into the approval flow.

Approval Groups
You can create approval groups using the BPM Worklist. When defining your approval
sequence, you can enter the names of one or more existing approval groups.
• Include a set of users that you configure to act on tasks in a certain pattern.
• Add an approval group to the approval rule.
– You can nest approval groups within approval groups.
• Approval tasks are routed serially to all members of an approval group.
• Use the Manage Approval Groups for Human Capital Management task to create and manage
approval groups by using the Fusion application or Oracle BPM Worklist.
• Depending on the approver type defined, approval tasks are routed to all members of an approval
group serially.

Demonstration
• 4-1: Creating an Approval Group

Summary
• Identified Approver Types

• Created an Approval Group

5
Oracle BPM Worklist

Learning Objectives
• Use BPM Worklist to configure approval rules

• Explain these approval options:
– Task aggregation
– Notification and reminder settings
– Rule sets
• Enable vacation periods and vacation rules

Configuring BPM Worklist
As an administrator, you can use the Business Process Management (BPM) Worklist to
review and configure approval policies for HCM tasks using the Manage Approval
Transactions for Human Capital Management task. You can use the BPM Worklist to
configure the following approval details:
• When to issue approval notification
• Who can access task contents
• What actions are available to approvers
• What to do when errors occur during approval routing
• When tasks expire or when should tasks be escalated
• Can approvers add other approvers

HCM Approval Management in Oracle BPM Worklist
• You can use the BPM Worklist to:

– Manage general administration values
– Define approval conditions and rules
– Create and maintain approval groups
• Use the Manage Task Configurations for Human Capital Management and Manage Approval
Groups tasks to navigate to the BPM Worklist.
• The approval rule configurations that can be performed from the Manage Approvals page are a
subset of what can be configured in the BPM Worklist.
• General administration includes setting up:
- Expiration and escalation policies
- When approval notifications are issued

Roles and Rights for Approving Tasks
The following table describes the actions that can be performed on tasks by various task
approvers:
Role Name Admin Owner Assignee
Acquire No Yes Yes
Delegate and Delete No No Yes
Error No No Yes
Escalate Yes Yes Yes
Info Request and Submit No No Yes
Override Routing Slip Yes Yes No
Push Back No No Yes
Purge Yes Yes No
Reassign and Release Yes Yes Yes
Task Approvers:
• Admin: Administrators are users who have been granted the BPM Workflow System Admin role.
• Owner: The user (if any) that owns the task instance.
• Assignee: The users or groups whom the task is currently assigned to.

Roles and Rights for Approving Tasks
The following table describes the actions that can be performed on tasks by various task
approvers:
Role Name Admin Owner Assignee

Renew No Yes Yes
Resume Yes Yes Yes
Route No Yes Yes
Skip Current Assignment Yes Yes No
Suspend Yes Yes Yes
Update No Yes Yes
Update Attachment and comment Yes Yes Yes
View Process History, View Sub Tasks, View Task History Yes Yes Yes
Withdraw Yes Yes No

Task Aggregation
• Controls the number of worklist tasks or notifications that the participant receives for the
same requisition
• Has three stages mapped to an approval notification:
– Once per task
– Once per stage
– None
• Use the On Error Notify option to define who would be notified when an error occurs.
You can configure task aggregation and error notifications on the Configuration tab.
Task aggregation has three stages that can be mapped to an approval notification:
• Once per task:
- This is the default setting for the requisitions approval task.
- Within the same task, if the approver has been returned multiple times, then based on the
approval rules defined, the approver will see only one worklist task or notification.
• Once per stage:
- Within the same stage, if the approver has been returned multiple times, then based on the
approval rules defined, the approver will receive only one worklist task per stage.
• None:
- No aggregation will be initiated.
Note: HCM processes are not defined (by default) for multiple stages. Therefore, during implementation, if
you select once per task or once per stage, the result will be the same, unless you configure it accordingly.

Assignment and Routing Policy
Allows approvers to modify the
approval list by inserting other
approval or FYI participants
Allows approvers to update

or remove future participants
from the approval list
Allows the requester to

insert ad hoc approval
or FYI participants
Approver claims
the task first.
Allows to decide when to move

the task to Completed status
Enable Auto Claim: This option is selected by default. This action is enabled when a task is assigned to a
position, a role, or an LDAP group. There can be multiple users associated with a group, role, or position;
therefore, the approver claims the task first to prevent multiple users from updating the task.

FYI Notifications in BPM
• Some of the FYI notifications in BPM are:

– AbsenceCatchAllExceptionFYI
– ManageOrgServiceExceptionFYI
– TimecardApprovalFYI
• Configure the Notifications tab to send only one FYI for a task.
FYI notifications are issued to approvers, but no response is expected.

Some of the FYI notifications in BPM are:
• AbsenceCatchAllExceptionFYI
• ManageJobServiceExceptionFYI
• ManageLocationCatchAllExceptionFYI
• ManageOrgServiceExceptionFYI
• TimecardApprovalFYI
To avoid sending multiple notifications for a task, perform the following steps:
1. Search for and select the required BPM task.
2. Click the Notifications tab.
3. Select the Don't send multiple notifications for the same human task event check box.

Notification and Reminder Settings
• Notification Settings • Reminder Settings

– This facilitates notifying – These are used to send periodic
participants about the change in reminders about the tasks
the status of any assigned task. assigned.
– You can set up as many – You can set to either “before expiry”
notifications based on task status or “after assignment,” respectively.
and message type.
Notification Settings
Users can be notified via email, SMS, voice messages, or instant messages.

Modifying Approval Rule: BPM Worklist
In the SoaOLabel.PromotionApprovers
Click the 2
1 Assignees tab.
box, click the diamond icon and select
Go to rule.
Use the Assignees tab to view and modify the approval rule associated with the transaction.

Rule Sets
• Define a set of rules for each route within an approval setup

• Route approvals to a single approver or to multiple approvers
An approval rule in a rule set consists of the following:

• Rule Name
• Condition
• List Builder and List Builder specific attributes
• Response type
• Auto Action
Condition
The IF condition indicates when the approval rule will be applied. Define conditions by using the following:
• Transaction attributes
• Available worker attributes
• Requester attributes
Use the search icon to select the attributes to apply in the rule. Define IF conditions and Then options.
List Builder and List Builder Specific Attributes
Route the approvals serially to a list of approvers. All approvers must approve for the task to be approved.
Select the applicable list builder for the approval rule from the list of values. Use the following list builders for
HCM Approvals. For each list builder, specify the list builder specific attributes for the rules to work:
• Approval Group
• Job Level
• Position
• Supervisory
• Management Chain
• Resource

Setting the Transaction to Automatically Approve
Set the transaction to get automatically approved even when a newly added participant
rejects the transaction.
1. In the Setup and Maintenance work area, click the Search button and search for the task Manage
Task Configurations for Human Capital Management.
2. In the Search Results region, click the task name. This opens the BPM Worklist.
3. Search for and select an approval process, such as TransfersApproval.
4. Click the Configuration tab.
5. In the Early Completion Settings section, select the Complete task when participant chooses
Reject option.

Configurations in the Notifications Tab
Use the Notifications tab in the BPM Worklist to:

• Disable email notifications for business processes
• Send periodic reminder emails for pending transactions

– Enable reminders to assignees, but not to the requestor.
Disabling Email Notifications for Business Processes

Use the Notifications tab in BPM Worklist to specify when to send (or not send) email notifications. If you
do not want any email notifications to be sent for a specific business process, you can remove all the rows
in the Task Status table. To disable email notifications for a business process, perform the following steps:
1. In the Setup and Maintenance work area, search for and select Manage Task Configurations for
Human Capital Management to open the BPM Worklist.
2. Search for and select an approval process, such as ApproveGoal, and click Edit Task.
3. Click the Notifications tab. This tab is specific to email notifications only.
4. In the Task Status table, click Delete Notification.
To configure reminder notifications, perform the following steps:
1. In the BPM Worklist, search for and select an approval process, such as CreateGradeApproval.
2. Click the Notifications tab.
3. Select the Enable Reminder option.
Task Status
Task Status options include:
• Update: Update status indicates a change that is made that doesn't affect the approval history or
routing of the task. For example, if a task is assigned to a user and all they do is add an attachment,
without approving the task or delegating it to someone else.
• Update Outcome: This state applies to a business process flow beyond a human task, such as
programmatically through the task service updateTaskOutcome method from the ITaskService API.
• Alerted: Alerted state typically indicates error conditions that can be rectified. In this case, the task is
moved to ALERTED state and assigned to error assignee if configured.

Demonstration
• 5-1: Modifying Approval Rules Using the BPM Worklist

Summary
• Explained how to use BPM Worklist to:

– Manage general administration values
– Define approval conditions and rules
– Create and maintain approval groups
• Used the Manage Task Configurations for Human Capital Management and Manage
Approval Groups tasks to navigate to the BPM Worklist

6
Approvals and Notifications

Learning Objectives
• Describe approval notifications

• Configure approval notifications
• Describe FYI notifications
• Enable and disable Workflow Notifications

Approval Notifications
• When defining the approval workflow, configure who is notified at each event.
• On the Home page, click the Notifications icon to view a list of your recent notifications.
This image is for the news feed layout, which is the layout used in the class environment. If your
administrator has selected a different default home page layout, then you get an alternate UI when you click
the Notifications icon. If you or another administrator selected news feed as the default home page layout,
then users also get notifications in the Things to Finish section on the home page, as well as the
Notifications page.
Note: When you define the approval workflow, you configure the approval action that determines how
notifications are issued to approvers and whether any action is required from them.

Demonstration
• 6-1: Approving a Promoted Worker

FYI Notifications
• These are sent to approvers whose approvals are not required.

• To make a notification as FYI, on the Manage Approval Rules page:
– Select the approver
– In the Action Type field, select Information Only
An FYI (For Your Information) participant just receives a notification task and the business process does not
wait for the participant’s response.

Configuring Approval Notifications
Add comments and attachments.
Note: The class environment is set to the News Feed layout with responsive UI pages enabled. If your
administrator has selected a different default home page layout, then you get an alternate UI.
Approvers of a transaction can:
• View the comments and attachments posted by earlier approvers.
• Add their own comments and attachments.
- Any comments and attachments that they add are available in the notification only and not
stored as a part of the actual transaction.
• Configure the approval notification by using the page composer, in either the Design View or Source
View.
- To edit the notification, click the Edit button on the top-right corner of the notification. If the
current approver edits a transaction and clicks Submit, it is considered an implicit approval
and the task is assigned to the next approver.
- You can remove the edit link using page composer.
- For reports-based notifications you can remove the edit link by customizing the BI template.
Note: You cannot edit others’ comments and attachments.

Configuring Notifications Based on Reports
• Oracle Business Intelligence (BI) Publisher reports determine the notification content
and format for some workflow notifications.
• You can edit a report to configure the email and in-app notifications.
• Report-based notifications are optimized for viewing on mobile devices.
Report
BI Publisher
Email In-App
Notification Notification
An example of a reports-based notification is the approval request notification an approver receives when a
user submits a performance goal for approval.
Note: You can modify the BI report templates only if you have the BI Administrator role.
For a full list of the reports-based workflows, see the help topic HCM Configurable Workflow Notifications:
Overview.
For more information about editing reports-based notifications, see Oracle HCM Cloud Configurable Email
Notifications (Doc ID 2331021.1) on My Oracle Support.

Generating Report-Based Notifications
The process to generate email and in-app notifications is the same as generating other
types of report output. This figure shows how BI objects work together to generate
notifications:
Subtemplate
Email
Layout Template Notification
Data Model
BI Report
Data Source HTML

Style Template
In-App
Notification
The notification generation process involves various types of objects in the business intelligence catalog,
including data models, subtemplates, style templates, and reports.
• Data Sources: Stores the attributes and attribute values for business objects and transactions in the
application. An example of data sources is the transaction tables.
• Data Model: Determines which attributes from data sources are available to be included in the
notification and how that data is retrieved.
• Subtemplate: Provides common components, for example a branding logo and buttons, that can be
reused in multiple reports.
• Style Template: Provides styles such as the type of lines and fonts to use in tables, or the font type,
size, and color to use for headings.
• Report: Contains a layout template that determines:
- Which attributes appear in the notification, from the data model used for the report.
- What the notification looks like, leveraging components from the subtemplate and styles from
the style template used for the report.
• HTML: Is the output generated from the report.
• Email Notification: Has the HTML output embedded in the email body.
• In-App Notification: Has the HTML output embedded in the application UI.

Notification Setup for BI Publisher
• You configure profile options to specify the HCM applications that use the BI Publisher
reports rather than the default FYI and approval notifications.
• To use BI Publisher reports rather than the default workflow and approval notifications,
you must:
– Configure profile options for email and in-app notifications to specify the HCM
applications that use the BI Publisher reports.
– Download and install the Template Builder for Word add-in.
You configure profile options using the Manage Administrator Profile Values task in the Setup and
Maintenance work area. The profile options for this setup are prefaced with BIP_EMAIL or BIP_ONLINE.
For more information, see the following help topics:
• Create and Edit Profile Options
• HCM Configurable Workflow Notifications
• Templates and Data Models Used for HCM Notifications Based on Reports
• Configure Workforce Deployment Notifications Using Reports

Demonstration
• 6-2: Modifying a Report-Based Notification

Summary
• Described approval notifications

• Configured approval notifications
• Described FYI notifications
• Enabled and disabled Workflow Notifications

7
BPM Worklist and Transaction Console

Learning Objectives
• Perform administrator tasks in BPM Worklist

• Use Transaction Console
• Set vacation rules

BPM Worklist – Administrator Options
Click to create user
view
Administrators can configure task list in several
ways, including:
• Adding worklist views,
• Selecting which columns to display
• Displaying a subset of the tasks based on
filter criteria
You can resize the task list display area to
increase the number of tasks fetched.
For example, from a worklist, a loan agent can
review loan applications or a manager can
approve employee vacation requests. These Administrator
processes are defined in human tasks. options
Note
Oracle BPM Worklist provides different functionality based on the user profile. Standard user profiles include
task assignee, supervisor, process owner, and administrator. For example, worklist users can update
payloads, attach documents or comments, and route tasks to other users, in addition to completing tasks by
providing conclusions such as approvals or rejections. Supervisors or group administrators can use the
worklist to analyze tasks assigned to a group and route them appropriately.
For more information on BPM Worklist, see:
https://docs.oracle.com/cd/E15586_01/integration.1111/e10224/bp_worklist.htm

BPM Worklist – User Views
Users can customize their task lists, as

required, by adding worklist views.
For example, selecting the columns to display
or a specific assignee, or displaying a subset
of the tasks based on filter criteria.
Using Oracle BPM Worklist, task assignees can do the following:

• Perform authorized actions on tasks in the worklist, acquire and check out shared tasks, define
personal to-do tasks, and define subtasks.
• Filter tasks in a worklist view based on various criteria.
• Work with standard work queues, such as high priority tasks, tasks due soon, and so on. Work
queues allow users to create a custom view to group a subset of tasks in the worklist, for example,
high priority tasks, tasks due in 24 hours, expense approval tasks, and more.
• Define custom work queues.
• Gain proxy access to part of another user's worklist.
• Define custom vacation rules and delegation rules.
• Enable group owners to define task dispatching rules for shared tasks.
• Collect a complete workflow history and audit trail.
• Use digital signatures for tasks.

Demonstration
• 7-1: Administrator Tasks in BPM Worklist

Transaction Console Transaction Manager: Transactions
Transaction Summary tab
The Transaction Manager: Transactions
page enables you to:
• Apply filters to view transactions
based on status, name, process
name, issue date and assigned to.
• Access a transaction to see a detailed
history and/or transaction log.
• Access a transaction to take actions
such as withdraw, reassign,
recover, add comments.
Filters offer superior search

capabilities
The Transaction Console provides a centralized console where HCM Administrators can:
• Set up approval rules and routing policies
• Set up task configurations like escalation and reminder policies, expiration policies, email
notification-related configurations and so on
• Set up transaction flows to bypass approvals
• Monitor approval tasks and take appropriate actions to resolve errors
• Monitor pending tasks and take appropriate actions like withdraw or reassign to resolve stuck
transactions
You can secure access to transactions so that users can manage only certain categories of transactions,
such as Talent or Compensation.
For more information on the Transaction Console, see Oracle HCM Cloud Common Features Release 13
Transaction Console (Doc ID 2430452.1) on My Oracle Support.

Transaction Console Transaction Manager: Rules
Check to bypass
approvals rules
The Transaction Manager: Rules page

offers Human Capital Management (HCM)
Administrators a search capability to find
Process Types. Additionally, HCM
Administrators can configure approval rules
and manage task configurations like
Bypass Approvals from the console.
The Transaction Manager: Rules page is used to perform the following tasks:
• Search and find a specific rule
• Access and configure approval rules within HCM Cloud
• Enable the bypass rule functionality by clicking on the circle/check icon in the middle column
You can secure access to the Approval Rules tab in the Transaction Console using the new functional
privilege: PER_CONFIGURE_APPROVAL_RULES_PRIV
Note: To configure complex rules, it is recommended that you use the BPM Worklist because there are
certain limitations using the Transaction Console:
• It does not display more than 25 rules
• More than 10 approvers are not allowed in a single rule

Archiving and Purging Workflow Tasks
Workflow tasks with a final status, such as Completed and Expired, can be archived and
purged.
Archive Purge
• Keeps a copy of the task data • Removes the completed tasks
for audit, data retention or from users’ worklists and
analysis, and other purposes. permanently deletes the original
data.
Archive: Tasks are automatically archived once a month without you doing any setup. You can't change or
stop this automatic archive. You can also run the Archive Workflow Tasks scheduled process as needed; for
example, if you need the latest data archived immediately for reporting purposes. The process includes all
eligible tasks that aren't yet archived.
Archived data includes task details, approval history, comments, and attachments. How you view or use the
archived data depends on the products you're using. For example, the data might be displayed in a table on
a page, or available through a business intelligence subject area that you can select to create an analysis.
Purge: Archived tasks that were last updated over 30 days ago are immediately purged after the monthly
automatic archive, without you doing any setup. You can't change or stop this automatic purge.

Vacation Rules
Set a vacation period to remove yourself from automatic task assignment during the dates
you specify.
Vacation rules are not applicable for To Do tasks. If there are no vacation rules, you can manually reassign
the tasks to new approvers.
To set a vacation period, perform the following steps:
1. In the Worklists window, click the down arrow adjacent to the implementor login.
2. Select Preferences.
3. Select the Enable vacation period check box.
4. Provide start and end dates.
5. Click Save.
To create a new vacation rule, perform the following steps:
1. Click the My Rules node.
2. Click Add New Rule to open the My Rules page.
As an alternative to using the BPM UI, you can delegate role and approval responsibilities to others on the
Account Management self-service page. This is available through the Employee and Contingent Worker
roles. Navigate to this page by going to Me, Roles and Delegations. In the Approval Delegations section,
there is now an option to restrict or allow the person who is being delegated to, to approve their own
transactions.

Demonstration
• 7-2: Enabling Vacation Rules and Delegating Approval Responsibilities

Administrator Capabilities - Reassigning a Task
1 From the Actions list, select Reassign.
2 Provide a user or select

a user group.
To reassign a task, perform the following steps:

1. From the HCM Cloud home page, access Notification Icon (the Bell symbol).
2. Click the More Details dropdown, select Human Capital Management.
3. The BPM Worklist page opens.
4. Select the required task from one of these sections:
- My Tasks
- Initiated Tasks
- Administrative Tasks
5. From the Actions list, select Reassign to open the Reassign Task dialog box.
6. Select the Reassign option. Delegate differs from Reassign in that the privileges of the delegatee
are based on the delegator’s privileges. This function can be used by managers’ assistants, for
example.
7. In the users’ choice list, select either Users or Groups.
8. In the text box, enter the first name of the user or group and click Search.
9. In the Available section, select the required user and click Move.

Summary
• Performed Administrator Tasks in BPM Worklist

• Used Transaction Console
• Set vacation rules

8
Alert Notifications

Learning Objectives
• Describe the two types of alert notifications

• Understand the Alerts Composer tool
• Explain how to view Alerts History

Alerts Overview
Alerts are informational

notifications sent to users Event Alerts: Triggered when a specific
by email or worklist. They event occurs in the application. Example:
A predefined time exceptions event alert
are triggered based on is triggered when compliance exceptions
predefined conditions for are available. Notifications are sent to
the following alert types: managers informing them of the
exceptions.
Types of
Alerts Resource Alerts: Based on Oracle
HCM Cloud REST API resources
deployed in the environment.
Example: A predefined visa
expiration resource alert is triggered
when a worker visa is approaching
expiration.
You can’t modify the triggering criteria for Event Alert notifications.
You can modify the triggering criteria for Resource Alert notifications by defining filters on the resource
attributes if you have the required privileges to access the REST resources. For the predefined Visa
Expiration notification, a filter is defined on the emps resource for the visa attribute.
For more information about deploying and using REST APIs, see the Quick Start section of the REST API
for Oracle HCM Cloud guide, available on OTN:
• https://docs.oracle.com/en/cloud/saas/global-human-resources/19d/farws/Quick_Start.html

Alert Composer
• You use the Alerts Composer to configure the notification templates and add recipients.
To open the Alerts Composer, go to the Navigator menu and click Tools > Alerts Composer.
Using the Alerts Composer, you can:
• Configure the notification templates and email formats and define language-specific templates.
• Define multiple templates for the same triggering criteria.
• Use Groovy expressions and define variables to substitute runtime values.
• Schedule jobs for processing the Resource alert notifications.
• Verify the alerts history and notifications activity.

Functions and Groovy Expressions
When you configure alerts using the Alerts Composer, you can use a variety of functions
and Groovy expressions.
• Functions return values such as an employee’s manager or benefits representative.
• Groovy expressions substitute variables and add conditions based on runtime values.
For additional information, including a list of supported functions, see the help topic Functions and Groovy
Expressions.

Viewing Alerts History
• Use the Alerts History page to view the history of alerts that are enabled for activity
logging.
• You can view statistics such as alert status, start date, duration, messages, and
processing errors.
• Click the alert name to view detailed information about an alert.
Alerts on the Alerts History page are classified into three categories.
• Processed: Displays the alerts that are processed
• Running: Displays the alerts that are currently being processed.
• Scheduled: Displays the alerts that are scheduled to run on a future date.

Alerts Composer Security
You must have these functional security privileges to use the Alerts Composer and run
alerts:
Functional Security Privilege Description Assigned to Job Role
Access Alerts Composer Allows access to Alerts Human Capital Management Integration
Composer. Specialist
Process a Predefined Alert Allows processing of Human Capital Management Integration

predefined alerts. Specialist
In addition, you must have the functional privileges to access REST API resources to create or modify user-
defined and predefined resource alerts. For example, you must have the functional privilege Use REST
Services - Employees to access the emps resource and its child resources to manage the alert templates
that are based on this resource.

Demonstration
• 8-1: Reviewing Event Alerts

• 8-2: Creating a New Resource Alert

Summary
• Described the two types of alert notifications

• Understood the Alerts Composer tool
• Explained how to view Alerts History

Approvals - Student Guide - 19D

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Approvals - Student Guide - 19D

Загружено:

Авторское право:

Доступные форматы

Oracle HCM Cloud: Workflows

Learn more from Oracle University at education.oracle.com

Restricted Rights Notice

U.S. GOVERNMENT RIGHTS

2 Approval Management Overview

3 Approval Rules Configuration

5 Oracle BPM Worklist

6 Approvals and Notifications

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

• Identify the purpose of this course

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 1 - 2

After completing this lesson, you should be able to:

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 1 - 3

• Approval Management Overview

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 1 - 4

Oracle Help Center My Oracle Support Oracle University

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 1 - 5

Approval Management Overview

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

• Understand approval workflow

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 2

To manage approval processes, • The key components that are used in

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

• Oracle SOA Approval Management Extensions (AMX)

Oracle HCM Cloud: Workflows and Approvals 2 - 3

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

• The tasks are routed in a defined sequence to achieve a defined result.

Oracle HCM Cloud: Workflows and Approvals 2 - 4

Predefined roles provide access to workflow functionality.

BPM Role Name BPM Role Code Inherited by Job Role

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 5

• These policies determine the workflow events.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 6

The figure shows a two-level approval flow:

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 7

The Manage Approval Transactions task manages transactions and rules.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 8

• Understood approval workflow

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 2 - 9

Approval Rules Configuration

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

• Configure approval rules, conditions, and approvers.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 3 - 2

• Approval rules determine a transaction’s • Use the Manage Approval

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 3 - 3

Action Type Action

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 3 - 4

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

Oracle HCM Cloud: Workflows and Approvals 3 - 5

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

THEN statements determine: