Professional Documents
Culture Documents
Instructor Guide
Disclaimer
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.
CONTENTS
Lesson 1: Workflow, Approvals, and Notifications ......................1
Objectives ................................................................................................ 1
HCM Approval Management Overview .......................................................... 2
Approval Management Overview ............................................................... 2
Workflow ............................................................................................... 3
Instructor Note: Demo Timing ................................................................ 4
Instructor Note: Demonstration 1 ............................................................ 5
Demonstration 1: Exploring the Welcome Dashboard ................................. 6
Approval Policies ..................................................................................... 8
Typical Approval Workflow ..................................................................... 9
Manage Task Configurations for Human Capital Management ....................... 11
Instructor Note: Manage Task Configurations for Human Capital Management 12
HCM Approvals Setup and Maintenance ...................................................... 13
Approver Types....................................................................................... 14
Instructor Note: Activity Timing .............................................................. 16
Activity 1: Introduction: Creating a Custom Representative Type ................. 17
Activity 1: Creating a Custom Representative Type .................................... 18
Manage Approval Groups for Human Capital Management ............................. 21
Instructor Note: Activity Timing .............................................................. 22
Activity 2: Introduction: Defining an Approval Group .................................. 23
Activity 2: Defining an Approval Group ..................................................... 24
Approval Structure .................................................................................. 26
Employee Supervisory Hierarchy ............................................................. 27
Position Hierarchy ................................................................................. 28
Job Levels ............................................................................................ 29
Approval Groups ................................................................................... 30
Oracle BPM Worklist ................................................................................ 31
HCM Approval Management in Oracle BPM Worklist .................................... 32
Task: Event Driven configuration........................................................... 33
Task Aggregation .................................................................................................35
Error Notification ..................................................................................................36
Assignment and Routing Policy ...............................................................................37
Expiration and Escalation Policy ..............................................................................38
Notification Settings ..............................................................................................39
Reminder Settings ................................................................................................40
Approval Rules ................................................................................... 41
Ruleset ...............................................................................................................42
IF Conditions ....................................................................................................43
List Builder and List Builder Specific Attributes .......................................................44
Approval Group .............................................................................................45
Job Level ......................................................................................................46
Position ........................................................................................................48
Supervisory ..................................................................................................49
Management Chain ........................................................................................50
Resource ......................................................................................................51
Response Type and Auto Action ...........................................................................52
Instructor Note: Demo Timing ................................................................................53
Demonstration 2: Exploring BPM Worklist Task Configuration ......................................54
Instructor Note: Activity Timing ..............................................................................56
Activity 3: Introduction: Modifying Approval Rules for Transfer and Termination ............57
Activity 3A: Modifying Approval Rules for Transfer .....................................................58
Activity 3B: Modifying Approval Rules for Termination ................................................66
Instructor Note: Activity 3 - Troubleshooting Tips ......................................................74
Vacation Rules.................................................................................... 75
i
Instructor Note: Activity Timing ..............................................................................76
Activity 4 Introduction: Enabling Vacation Rules and Delegating Approval Responsibilities
.........................................................................................................................77
Activity 4: Enabling Vacation Rules and Delegating Approval Responsibilities .................78
Lesson Highlights .................................................................................... 79
Lesson Highlight Details ......................................................................... 80
ii
Lesson 1: Workflow, Approvals, and Notifications
You can set up rules to route transactions to approvers in serial or parallel, or set up
rules based on employee supervisory hierarchy, position hierarchy or job levels, by
using these extensions.
- AMX enables you to define complex multi-stage task routing rules for
business documents.
- The Business Process Owner also sets up and manages approval rules using
the BPM Worklist Application
- AMX integrates with the setup in Human Capital Management to derive the
supervisory and position hierarchy based approvers
Workflow
Workflow tasks for a user appear in the Worklist: Notifications and Approvals region on
the user's Welcome Dashboard; the user also receives an e-mail notification.
Workflow is a process in which tasks are routed automatically among users for their
consideration or action. The tasks are routed in a defined sequence to achieve a
defined result.
A workflow human task is any workflow component that requires attention or action from
users. For example, a promotion request for a worker may require approval from the
two levels of the manager hierarchy above the task submitter:
Demonstration Steps
Sign in as mitch.blum.
Start Here
Information
Discuss the sections on this page. Highlight the Promotion Approval Stage
in the History section.
4. Click the Actions button to view the list of actions you can perform.
Information
Discuss each action in the list.
7. Click the Advanced Edit Options icon In the Show Status Filter field.
9. Enter true in the box under the Type a value or expression radio button.
Approval Policies
Approval policies determine workflow events, including when approval of a transaction
is required and who approves the transaction.
Predefined approval policies exist for many Oracle Fusion HCM tasks.
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
using personalization. The approval process continues unaltered after the transaction
has been edited.
Approval Management configuration options for Oracle Fusion Human Capital
Management determine most of the actions that are available to the participants in the
approval process. For example:
· Either approver can reject the transaction. By default, the approval process stops
when the transaction is rejected.
· 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, as appropriate.
· Ad hoc insertion of approvers in the approval list is permitted.
· Approvers can delegate their approval responsibilities to other approvers.
If you change the default settings of the Approval Management configuration options for
a task, then different actions or action outcomes become available to this approval flow.
You also use BPM Worklist to configure details for all approval tasks. These details
include:
You cannot use the Enter key, click the icon instead.
You cannot use % sign for wildcard, use a * for the wildcard.
To perform any HCM approvals task, you need the duty role BPM Worklist
Administration Duty, which is predefined for the Application Implementation Consultant
job role.
Approver Types
You can include any number of approver types in your approval sequence. This section
explains each of the approver types.
Managers
You can include the following predefined types of managers in your approval sequence:
Line manager
Resource manager
Project manager
Regional manager
Approval Groups
An approval group consists of a name and a predefined set of approvers configured to
act on a task. Depending on the approver type defined, approval tasks are routed to all
members of an approval group in serial.
You can create new Approval Groups or edit existing Approval Groups from the
Approvals Group tab on the BPM Worklist Application Administration page. When
defining your approval sequence, you can enter the names of one or more existing
approval groups.
Users
You can include one or more Oracle Fusion Applications users in the approval
sequence.
Representative
You can include holders of the following predefined responsibilities in your approval
sequence:
Human resource specialists assign responsibilities to workers using the Manage Areas
of Responsibility task. A worker becomes an approver for a transaction if he or she has
that responsibility for the transaction subject. For example, if you specify that the
benefits representative is an approver for a promotion, then the benefits representative
of the worker who is being promoted is invited to approve the promotion.
Positions
If you include a position hierarchy in your approval sequence, then position holders are
invited to approve the transaction. For positions with more than one position holder, the
transaction is approved by the first position holder to approve.
Requirements
Use the bold text for the object names, replacing the XX with your student
number, as indicated by your instructor.
You must have access to Oracle Fusion Application InFusion database or
comparable training or test instance at your site, on which to complete this
practice.
Activity Scope
Create a custom representative type and assign it to an employee.
Start Here
Home work area, Welcome tab (default view after sign in).
3. Click Search.
14. In the Search Results section, select the employee assignment Patricia
Smith.
17. In the Responsibility Type field, select Health & Fitness Representative.
Verification
1. In the Search: People section on the left pane, enter Terry Parker.
4. Review the details in the Work Contacts section to ensure that Health & Fitness
Representative and Patricia Smith appear in the Type and Name columns
respectively.
At this point, you should have created a representative type and assigned it to an
employee.
New approval groups can be created, or existing approval groups can be edited from
the Approvals Group tab on the BPM Worklist Application Administration page.
Requirements
You must have access to Oracle Fusion Application InFusion database or compar able
training or test instance at your site, on which to complete this practice.
Activity Scope
Define a new Approval Group.
Start Here
Home work area (default view after sign in)
These task lists are expanded: Define Approval Management for Human Capital
Management - Manage Approval Groups for Human Capital Management
3. Click Search.
5. In the Manage Approval Groups for Human Capital Management task row,
click Go to Task.
11. Repeat steps 8 to 10 to add the following members to your approval group:
kerry.lane
daniel.miller
cheryl.simon
13. You can view the new approval group in the Groups pane.
Approval Structure
Approval routing policies can be defined based on the following:
Approval Groups
Position Hierarchy
Organizations can also choose to route the requisition approvals based on the position
hierarchy defined in Oracle Fusion Human Capital Management. The position hierarchy
needs to be defined, and the workers must be assigned the corresponding positions.
Job Levels
Job level routings are based on the supervisory hierarchy defined in Oracle Fusion
Human Capital Management. The approval list will be generated based on the starting
level specified in a rule and continuing until an approver with a sufficient job level is
found. The job levels must be defined for the jobs. The supervisory hierarchy needs to
be defined and workers must be set up with the appropriate jobs.
Approval Groups
An approval group consists of a name and a predefined set of participants configured to
act on a task. Depending on the participant type defined, approval tasks are routed to all
members of an approval group in serial.
New Approval Groups can be created, or existing approval groups can be edited from
the Approvals Group tab on the BPM Worklist Application Administration page.
Work assignee - An end user who is assigned a task. These users can view
tasks assigned to them and perform actions, and can also define custom views
and define routing rules for their tasks.
Process owner - Typically a business analyst responsible for managing certain
types of approvals. These users can manage tasks for the processes they own,
define approval groups, and change approval policies
Workflow administrator - Typically a system administrator responsible for
managing errored tasks, and administering and monitoring work queues. This
user also may use Oracle Enterprise Manager to monitor the health of the
workflow services.
Manage general administration values for all HCM tasks. These values include
expiration and escalation policies, when approval notifications are issued, and
the access to task data that each approver has for all HCM tasks.
Define approval conditions and rules.
Create and maintain approval groups.
When you perform the tasks Manage Task Configurations for Human Capital
Management and Manage Approval Groups, you navigate automatically to Oracle BPM
Worklist.
Within BPM Worklist application, there are two pages for setting up approvals:
Task: This allows to configure options that affect that entire approval task. These
are options such as a vacation or expiration policy for the approval or error
handling etc.
Rules: This contains the routing & approval conditions, ie, under this condition,
do this routing.
Task Aggregation
Error notification
Assignment and Routing Policy
Expiration and Escalation Policy
Notification Settings
Reminder Settings
Task Aggregation
If an approver is returned as part of the approval routing, in the same task or stage, you
can use the task aggregation setting to reduce the number of worklist tasks (or
notifications) the participant receives for the same requisition. The options include:
Once per task (default setting for requisition approvals task): Within the same
task, if an approver is returned multiple times based on the approval rules, then
the approver will only receive one worklist task (or notification) for action or
review.
Once per stage: If the same approver is returned multiple times based on the
approval rules within the same stage, then the approver will receive one worklist
task per stage for action or review.
Note: The HCM processes are not defined for multiple stages, therefore, if you
select the ‘Once per task’ or ‘Once per stage’ option, then this will lead to the
same result.
Error Notification
The On Error Notify attribute allows you to define an administrator who will be notified
when an error occurs in the approval routing process.
Enable auto claim: This option is selected by default. The claim action is
enabled when a task is assigned to a position, role or a LDAP group (see note
below). Since there can be multiple users in a position, role or group, the user
has to first claim the task to prevent multiple users from updating the task. This
does not include approvals based on approval groups. Enabling auto-claim will
not require a participant to first claim before performing an action, hence
reducing the number of steps.
Note: AMX provides the flexibility to include LDAP groups (groups created in
the user directory) as participants for approval routing.
Task Content and Task Action settings within the Notification Settings section allow
the administrator to control:
Notification Settings
Notifications indicate when a user or group is assigned a task or is informed that the
status of a task has changed. Notifications can be sent through email, voice message,
instant message, or SMS. Notification settings allow users to set up many notifications
based on task status and participant/approver type.
Note: If you are in SaaS mode, you cannot control whether to get notified through
email/voicemail etc. To configure these delivery settings, you need to log into SOA
Suite, through EM, and configure settings at server level.
Don't send multiple notifications for the same human task event:
Reminder Settings
You can use reminder settings to send periodic reminders for tasks. You can specify
options to send number of reminders either ‘before expiry’ or ‘after assignment’ of a
task.
Approval Rules
You can set and manage approval rules through the Rules page on the BPM Worklist
application.
Ruleset
Rule Name
IF Conditions
Priority of evaluation of IF conditions
Ruleset
Ruleset defines a set of rules for each route within an approval set-up.
You can route approvals to a single approver or to multiple approvers in serial, for HCM
processes. It also supports FYI type approvers within the approval rules (FYI approvers
do not directly impact the outcome of a task, but can provide comments or add
attachments).
Rule name
Condition
List Builder and List Builder specific attributes
Response Type
Auto Action
IF Conditions
For example, a rule is created with the condition where the salary increases more than
10% of base salary. If you submit a salary increase transaction that has a salary
increase of 13%, this rule will return a 'true' and the 'then' part will execute. A rule can
contain multiple conditions. 'And' or 'OR' operators can be used to indicate if all
conditions in the approval rule must be true or if only one condition need to be true for
the approval rule to apply.
For example, if salary increase is more than 10% and job grade is M8 (senior
management). A condition is defined using the transaction attributes or other available
worker or requester attributes.
You can use the search icon next to the attribute field to select the attributes to apply in
the rule.
You can select the list builder that is applicable for the approval rule from the list of
values.
You can use the following list builders for HCM approvals. For each list builder, there
are list builder specific attributes that would need to be specified for the rules to work.
Approval Group
Job Level
Position
Supervisory
Management Chain
Resource
Approval Group
You can select relevant Approval Group from the list of values. Select True or False for
the Allow empty groups option. If you set this option to True, then an empty approval
group will not result in an error and instead the routing will continue to the next
participant. If you set this option to False, an empty approval group (no members) will
result in an exception being thrown.
Job Level
You must specify the Number of Levels required to perform the approval action along
with other details.
You must specify a lower bound and an upper bound for job levels. These levels can be
relative to the starting point, the task requester or an absolute job level.
For example, for salary increase more than 10% of base salary, an approval is required
by at least Job Level 1 and at most Job Level 2 (approval rule modeled using absolute
levels). If the salary increase is requested by someone at a higher job level (i.e. job level
3), then it will be automatically approved.
The Starting Participant identifies the first participant in a list. The Starting Participant
attribute can be setup to:
A specific user
The manager of a reference user. For example, get the manager of the
requester
Use customized function to identify the starting participant
The Top Participant identifies the last participant which approvals will not go beyond in a
hierarchy. The Top Participant attribute are similar to starting participant, and can be
setup to:
A specific user
The manager of a reference user
Use customized function to identify the top participant
'Utilized Participants' allows you to control whether everyone returned in the list of
participants from this list builder should be part of the approval process. The possible
options are All Approvers, Final Approver Only, and Manager and Final Approver.
'Include all managers at last level' allows you to control if all holders of the last job level
based on the rule will be returned in the approval list. If you check this option, then all
the holders of the last job level based on the rule will be part of the approval process.
Position
You must specifiy the Number of Levels required to perform the approval action along
with other details.
You must specify a lower bound and an upper bound for positions. These levels can be
relative to the starting point, the task requester or an absolute position.
For example, for salary increase more than 10% of base salary, an approval is required
by 2 levels of position hierarchy starting from the task requester. The Starting
Participant identifies the first participant in a list. You can set up the Starting Participant
attribute to:
A specific user
The manager of a reference user. For example, get the manager of the requester
Use customized function to identify the starting participant
The Top Participant identifies the last participant which approvals will not go beyond in a
hierarchy. The Top Participant attribute is similar to the starting participant, and you can
set it up to:
A specific user
The manager of a reference user
Use customized function to identify the top participant
Utilized Participants allows you to control whether everyone returned in the list of
participants from this list builder should be part of the approval process. The possible
options are All Approvers, Final Approver Only, and Manager and Final Approver.
Supervisory
You must specify the Number of Levels required to perform the approval action along
with other details.
The Starting Participant identifies the first participant in a list. The Starting Participant
attribute can be setup to:
A specific user
The manager of a reference user. For example, get the manager of the requester
Use customized function to identify the starting participant
The Top Participant identifies the last participant to which approvals will not go beyond
in a hierarchy. The Top Participant attribute is similar to the starting participant, and you
can set it up to:
A specific user
The manager of a reference user
Use customized function to identify the top participant
Management Chain
Resource
You can select the Resource list builder to set up approvals by HR representatives.
Response Type
Response Type indicates if the participants are required to approve the task or if they
are FYI participants.
Auto Action
Auto Action settings can be utilized to allow list builder to act automatically on tasks.
The Auto Action Enabled value can be specified as either True or False.
If the Auto Action Enabled option is set to True, then the Auto Action value would allow
a control if the task should be automatically approved or rejected by specifying the value
of either “APPROVE” or “REJECT” (in capital letters).
If the Auto Action Enabled option is set to False, then the Auto Action value should be
set to ‘null’. If auto action is disabled, then the auto action value should be updated with
‘null’ (without the quotes).
Demonstration Steps
Sign in as hcm_impl or hcm_impl1.
Start Here:
Home work area (default view after sign in)
These task lists are expanded: Define Approval Management for Human Capital
Management - Manage Task Configurations for Human Capital Management –
BPM Worklist
3. Click Search.
6. In the Search field in the Tasks to be configured pane, enter Promotion% and
search.
7. Click PromotionsApproval.
Requirements
You must have access to Oracle Fusion Application InFusion database or comparable
training or test instance at your site, on which to complete this practice.
Activity Scope
In this activity, we will modify the termination and transfer approval rules. As per the
new termination and transfer approval rules, if the CEO of the organization
(Samuel.Mabry) terminates or transfers an employee, no approval is required. But if
someone else other than the CEO initiates these actions, two levels of approval will be
required.
Instructor Note: Two students in the same environment cannot change the same
approval rule. Therefore, for this activity, one student can change the transfer approval
rule (Activity 3A) and the other student can change the termination approval rule
(Activity 3B). In case you have three students in the same environment, the third
student can change the promotion approval rule following the same steps.
Start Here:
These task lists are expanded: Define Approval Management for Human Capital
Management - Manage Task Configurations for Human Capital Management –
BPM Worklist
3. Click Search.
6. In the Search field in the Tasks to be configured pane, enter Transfer% and
search.
7. Click TransfersApproval.
9. In the Expiration and Escalation policy section, select Expire After from the
menu.
Note: Steps 17 and 18 are only required in this pre-GA test environment and
will not be required in any real environment.
30. In the Starting Participant field, click the Starting Participant icon.
32. In the *Reference User field, click the Expression Builder icon.
37. In the Top Participant field, click the Top Participant icon.
39. In the *Reference User field, click the Expression Builder icon.
50. Click the Surrounded selected tests with parenthesis icon, and select
Selected Tests>not(…).
60. In the Starting Participant field, click the Starting Participant icon.
63. In the *Reference User field, click the Expression Builder icon.
68. In the Top Participant field, click the Top Participant icon.
75. Select the checkboxes of both the new rules you have defined.
84. Enter Edward Malone in the Keywords field and click Search.
88. In the Location field in the Location Details section, enter London.
90. Review the Approvers region to verify if the approvers are Jessica Mullen
(Director and Mitch Blum’s manager) and Robert Jones (Senior VP and Jessica
Mullen’s manager).
93. Enter Martha Burnham in the Keywords field and click Search.
97. In the Location field in the Location Details section, enter London.
99. Review the Approvers region to verify if the approver is Samuel Mabry
(CEO).
At this point, you should have modified the Transfer approval rule and verified the
approvers for the transfers of Edward Malone and Martha Burnham.
Start Here:
These task lists are expanded: Define Approval Management for Human Capital
Management - Manage Task Configurations for Human Capital Management –
BPM Worklist
3. Click Search.
6. In the Search field in the Tasks to be configured pane, enter Terminat% and
search.
7. Click TerminationsApproval.
9. In the Expiration and Escalation policy section, select Expire After from the
menu.
Note: Steps 17 and 18 are only required in this pre-GA test environment and
will not be required in any real environment.
30. In the Starting Participant field, click the Starting Participant icon.
32. In the *Reference User field, click the Expression Builder icon.
37. In the Top Participant field, click the Top Participant icon.
39. In the *Reference User field, click the Expression Builder icon.
50. Click the Surrounded selected tests with parenthesis icon, and select
Selected Tests>not(…).
60. In the Starting Participant field, click the Starting Participant icon.
63. In the *Reference User field, click the Expression Builder icon.
68. In the Top Participant field, click the Top Participant icon.
75. Select the checkboxes of both the new rules you have defined.
84. Enter Harry Christensen in the Keywords field and click Search.
89. Review the Approvers region to verify if the approvers are Jessica Mullen
(Director and Mitch Blum’s manager) and Robert Jones (Senior VP and Jessica
Mullen’s manager).
92. Enter Michael Shannon in the Keywords field and click Search.
97. Review the Approvers region to verify if the approver is Samuel Mabry (CEO).
At this point, you should have modified the Termination approval rule and verified the
approvers for the terminations of Harry Christensen and Michael Shannon.
If you get the History Tree error, it means that the approver list is not getting
generated correctly based on the rule configuration. Check to see if you have
included the Not condition as indicated in the activity (step 48).
If you are not able to save the newly defined rules, check if you have a blank field
or missed a quote somewhere.
If you are not able to view any direct reports in the organization chart, check the
Data Roles and make sure that the role enables view hierarchy.
Vacation Rules
You can set a vacation period to remove yourself from automatic task assignment
during the dates you specify. Vacation rules are not executed for ToDo tasks.
If there are no vacation rules, then administrators can manually reassign the tasks to
new approvers.
Background
As a Manager, you can define and delegate vacation rules.
Requirements
You must have access to Oracle Fusion Application InFusion database or comparable
training or test instance at your site, on which to complete this practice.
Activity Scope
Enable vacation rules.
In this activity, you enable vacation rules and delegate approval responsibilites.
Start Here:
9. Click Save.
At this point, you should have enabled your vacation rules and delegated approval
responsibilities.
Lesson Highlights
Workflow concepts.
Predefined approval policies exist for many Oracle Fusion HCM tasks.