Oracle HCM Cloud: Approvals and Extensibility: license to use this Student Guideฺ

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2018, Oracle and/or its affiliatesฺ
a ble
f e r
ans
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
9 2 @ St
h a d this
s a use
d ( m to
a
ah Oracle ns e
s li c e HCM Cloud: Approvals
m ed
m
M oha and Extensibility
Student Guide
D96189GC20
Edition 2.0 | July 2017 | D100736
Learn more from Oracle University at education.oracle.com

Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
Author
Disclaimer
Roopa Malavally
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
Technical Contributors own use in an Oracle training course. The document may not be modified or altered
and Reviewers 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,
Angela Brown
publish, license, post, transmit, or distribute this document in whole or in part without
Amy Kust the express authorization of Oracle.
Steven Pratt The information contained in this document is subject to change without notice. If you
Deborah Beodeker, 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
Hema Hardikar warranted to be error-free.
Ashita Mathur Restricted Rights Notice
Santhosh
Radhakrishnan
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
a ble
applicable:
f e r
Editor
an s
Arijit Ghosh
U.S. GOVERNMENT RIGHTS
n - t r
The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
a no
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
h a s
Graphic Designer Trademark Notice
m ) e ฺ
Prakash Dharmalingam o
Oracle and Java are registered trademarks of Oracle i d
ฺcowners. Gu its affiliates. Other names
and/or
m
ฺib dent
may be trademarks of their respective
i n
Publishers
9 2 @ Stu
Syed Ali
h a d this
Jayanthy Keshavamurthy sa s e
( m to u
Raghunath M
a d e
s ah cens
ed li
m m
o ha
M
Contents
1 Oracle HCM Cloud: Approvals and Extensibility

Lesson Agenda 1-2
Course Objectives 1-3
Course Audience 1-4
Course Materials 1-5
Information Sources 1-6
a ble
Course Agenda 1-7
f e r
ans
2 Approval Management Overview n - t r
o
Objectives 2-2
s an
HCM Approval Management: Overview 2-3
) ha ฺ
Approval Workflow: Overview 2-4
ฺ c om uide
Approval Policies 2-5
ฺ i b m nt G
Approval Workflow 2-6
@ in tude
2
9 his S
Approval Transactions Explained 2-7
d
Summary 2-9 a
ah use t
s
m to
(Configuration
d
aha3-2cense
3 Approval Rules
s
Objectives
li Overview 3-3
m ed Rules:
Approval
ha m Understanding Approval Rules 3-4
M o Parts of an Approval Rule 3-5
IF Statements 3-6
THEN Statements 3-7
Creating an Approval Rule 3-9
Configuring IF Conditions 3-10
Adding Rule Conditions 3-11
Approval Attributes 3-12
Worker’s Current Assignment Attribute 3-13
Combining Multiple Rule Conditions 3-14
Condition Details: Views 3-15
Adding Approvers 3-16
iii
Configuring Approver Settings 3-17
Demonstration 3-19
Quiz 3-20
Summary 3-21
4 Approver Types
Objectives 4-2
Approver Types 4-3
Approval Types 4-4
Management Hierarchy 4-5
Configuring Management and Line Manager Hierarchy 4-7
Job-Level Based Line 4-8 a ble
f e r
Position Hierarchy 4-9
ans
Users 4-10
n - t r
o
Representatives 4-11
s an
Application Role 4-13
) ha ฺ
om uide
Approval Groups 4-14
Demonstration 4-15 ฺ c
m nt G
ฺ i b
Quiz 4-16
@ in tude
Summary 4-18
d 2
9 his S
a
ah use t
s
5 Approvals and Notifications
(m5-2 to
d
Lesson Objectives
a nse5-3
s ahNotifications
lice5-4
Approval
e dNotifications
FYI
ha mmCustomizing Approval Notifications 5-5

M o Customizing Notifications Using the Composer: Design View 5-6
Customizing Notifications Using the Composer: Source View 5-7
Quiz 5-8
Summary 5-9
6 Oracle BPM Worklist

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

Demonstration 6-18
Quiz 6-19
Summary 6-23
7 Working with Sandboxes

Lesson Objectives 7-2
Sandboxes: Overview 7-3 a ble
f e r
Working with Sandboxes 7-4
ans
Types of Sandboxes 7-5
n - t r
o
Types of Customizations in Sandboxes 7-6
s an
Multiple Users in Sandboxes 7-7
) ha ฺ
om uide
Tips and Tricks About Sandboxes 7-8
Practice 7-9 ฺ c
m nt G
ฺ i b
Demonstration 7-10
@ in tude
Quiz 7-11
d 2
9 his S
Summary 7-14 a
ah use t
s
(m to and Personalization Overview
8 Extensibility,dCustomization,
s aha8-2cense
Objectives
ed
Extensibility, i
lCustomization, and Personalization 8-3
m
m Extensibility 8-4
o ha
M Customizations 8-5
Managing Your Sandbox 8-7
Customization Layers 8-8
Working with Shared Components 8-9
Customizing Page Components 8-10
Customization Flowchart 8-11
Customizing the Springboard 8-12
Rolling Back, Downloading, and Uploading 8-13
Page Composer Migration 8-14
Quiz 8-15
Summary 8-17
9 Working with Page Composer

Objectives 9-2
Adding Content 9-3
v
Page Appearances 9-6
Modifying Page Appearances 9-7
Applying Conditional Changes 9-8
Conditionally Set Read Only Property 9-9
Conditionally Set the Read Only Property 9-10

Customization Migration 9-11
Tips and Tricks about Personalization 9-12
Demonstrations 9-13
Practices 9-14
Quiz 9-15
Useful Sources of Information 9-17
Summary 9-18 a ble
f e r
ans
10 Using Flexfields
n - t r
o
Lesson Objectives 10-2
s an
Flexfield Concepts 10-3
) ha ฺ
om uide
Flexfield Components 10-4
Types of Flexfields 10-6 ฺ c
m nt G
ฺ i b
in tude
Descriptive Flexfields 10-7
@
d 2
Extensible Flexfields 10-8
9 his S
a
ah use t
Ways to Deploy a Flexfield 10-9
s
Flexfield Implementation Flow 10-10
(m to
d
Flexfield and Customization Set Migrations 10-11
s aha cense
Demonstrations 10-12
ed li
Practices 10-13
mm
oha
Summary 10-14
M
A Functional Setup Manager: Enabling Offerings for Initial Use
Objectives A-2
Implementing Oracle HCM Cloud Applications A-3
Key Benefits A-4
Job Roles with Functional Setups User Permissions A-5
Application Implementation Manager A-6
Application Implementation Consultant A-7
Human Capital Management (HCM) Application Administrator A-8
Functional Users A-9
Navigating to Functional Setup Manager A-10
Functional Setup Methodology A-11
Working with the Offerings Page A-12
Working with Configure Offerings A-13
vi
Progressive Decision Making with Offering Hierarchy A-14
Enabling Offering and Functional Areas for Implementation A-15
Selecting Feature Choices A-16
Implementation Projects A-17
Demonstrations A-19
Summary A-20
a ble
f e r
ans
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
vii
Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
1
Oracle HCM Cloud: Approvals and

Extensibility
Course Overview
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Lesson Agenda
This lesson provides an introduction to the following:

• Course
– Audience
– Objectives
– Methodology
– Materials
– Agenda
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha
Oracle HCM Cloud: Approvals and Extensibility 1 - 2

Course Objectives
After completing the course, you should be able to:

• Identify the key concepts of Approval Framework:
– Approvals
– Create Approval Rules

– Describe a Predefined Rule
• Describe Oracle BPM Worklist
• Identify key concepts of Extensibility, Customizations, and Personalizations
• Explain Sandboxes
• Add, Create, and Deploy Descriptive Flexfields
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Course Audience
This course is designed for:

• Application implementation consultants and application administrators for configuring
approvals
• Functional users who are responsible for managing approvals

• Business Analysts responsible for Human Capital Management customizations and
extensibility
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Course Materials
• Course content is delivered over one day.

– Student Guide
All slides presented during lectures
— Student notes with additional information

– Activity Guide
— Hands-on practice
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Information Sources
• The HCM Approvals documentation is available in the HCM Cloud Library.

– Implementing Global Human Resources
– Using Global Human Resources
http://docs.oracle.com/cloud/farel11/globalcs_gs/FAIGH/FAIGH1009980.htm#FAIGH1009980
• White Papers for Oracle Fusion Applications HCM can be found at:
– http://onlyoracleapps.blogspot.in/2016/01/white-papers-for-oracle-fusion.html
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Course Agenda
• Approval Management Overview

• Approval Rules Configuration
• Approval Types
• Approvals Notifications
• Oracle BPM Worklist
• Working with Sandboxes
• Extensibility, Customization, and Personalization Overview
• Working with Page Composer
a ble
• Using Flexfields
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
b m t
i nฺi uden
The lessons provide overviews of approval 9 2 @ St extensibility, customization, and
management,
personalization. The instructor will h a d ththe
demonstrate
is configuration of a new approval rule. Students
s a use
d ( m
can customize pages, including springboards.
to
a
ah cens e
s li
m ed
o ham
M

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
2
Approval Management Overview

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives
After completing this lesson, you should be able to describe the following:
• Approval workflow
• Approval policies
• Approval transactions
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

HCM Approval Management: Overview
• To manage approval processes, Oracle HCM Cloud Applications use the approval-
management extensions of Oracle Service Oriented Architecture Suite human workflow
services.
• The key components that are used in approvals include:

– Oracle SOA Approval Management Extensions (AMX)
– Oracle Business Process Management (BPM)
– Oracle Human Capital Management
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Oracle SOA Approval Management 9 2 @ St (AMX)
Extensions
h a d this
- AMX enables yous ato define
u s e
complex, multi-stage, task routing rules for business
documents. (
d m to
• a
ah cProcess
Oracle Business e
ns Management (BPM)
s e
- edThe BPMliWorklist is a web-based application that enables you to access the tasks
m
ham
assigned to you and perform actions based on your roles in the approval process.
Mo - 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
• Process 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
a ble
Final Approver f e r
an s
n - t r
a no
Task Approved
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• 2 @ toStachieve a defined result.
The tasks are routed in a defined9sequence
h a d this
• Workflow tasks for a user
s aappearusinethe Worklist: Notifications and Approvals region on
d m
the user’s Welcome(dashboard;
to the user also receives an email notification.
a
ah cens e
s li
m ed
ham
Mo

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.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Approval Policies: 9 2 @ St
h a d this
- a ubysthe
In most cases, approval
s e requester's first-level and second-level managers is
required. (
d m to
- Fora a
h tasks
some e
ns(for example, some absences-related tasks), approval by the first-
s c e
li only is required.
m edlevel manager
ham
- For the Share Information task, approval by the worker whose information is being
Mo shared is required.
• Typically, approval notifications are issued to:
- Workers to whom an approval task is assigned, when the task is assigned
- The worker who submitted the task, when the approval process completes

Approval Workflow
The figure shows a two-level approval flow:

a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• When a transaction is submitted,9 it 2
@ S
is routed
t
automatically to the worklist of the submitter's
d approver.
afirst thi s
first-level manager, who isatheh
s manager e
• ( m
If the submitter's first-level
t o us approves the transaction, the transaction is routed
d submitter's
automaticallyhtoathe se second-level manager, who is the second approver.
s a c e n
• d
If theesubmitter'slisecond-level manager approves the transaction, the transaction is
m m
committed to the database tables.
o h• a Either approver can reject the transaction. By default, the approval process stops when the
M 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
On the Manage Approval Transactions page, perform the following actions on a transaction:
Configure Approval
Policies
• Define
• Approvers
• Approval rules
View Failed and Pending Processes Bypass Approvals

a ble
f e r
• For failed processes, view the generated error message. Enable bypass approval for a transaction to
an s
• For pending processes, view the list of approvers. commit the transaction immediately upon submit
and not route it for approval.
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Configuring Approval Policies 9 2 @ St
h a d this
• s a the
For a selected task, configure
u s e
approval policy by:
- ( m
Arrangingdapprovers tino the required order
a
ah approval
Defining
e
ns rules for each approver
-
d s li c e
- e Submitting the approval policy
m
o h• amThe approval policy takes effect immediately and supersedes the current approval policy for
M 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

Failed Processes
• 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.
a ble
f e r
ans
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
• To manage approval processes, Fusion Applications use the approval-management

extensions of the SOA Suite human workflow services.
• Approval workflow is a process in which tasks are automatically routed among users for
consideration or action.
• Approval policies determine the workflow events, which include:
– When approval of a transaction is required
– Who approves the transaction
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
3
Approval Rules Configuration

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives
After completing this lesson, you should be able to configure approval rules.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Approval Rules: Overview
• Approval rules determine a transaction’s approval process.

• They are evaluated individually in an undefined order.
• You can configure multiple approval rules for a transaction.

– Use the Manage Approval Transactions for Human Capital Management task to
configure approval rules.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Understanding Approval Rules
Using the Manage Approval Transactions for Human Capital Management task, you can:
• 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: Approval rules comprise one or more IF statements and one THEN statement.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Note 9 2 @ St
h a d this
a onuthe
If you edit or delete an approvalsrule s eManage Approval Rules page, the approvals currently in
d m
progress complete as if the(rule hadto not been edited or deleted. New approvals follow the latest
version of the rule.ah a ns e
s li c e
m ed
o ham
M

Parts of an Approval Rule
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
a ble
Supervisory Level – Require approvals up to the second level Manager
f e r
an s
n - t r
a no Action Type Action
h a s
m ) e ฺ
o
b m t
i nฺi uden
IF Conditions 9 2 @ St
h a d this
Combine multiple IF statementssby a usingu e operators.
logical
s
d
If you join multiple statements
m
( with the
to AND operator, all statements must be true before the
approval rule takes
a
h ens
aeffect. e
s lic with the OR operator, only one of the statements must be true before
If you joinm ed statements
multiple
am rule takes effect.
thehapproval
o
M

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 worker's department is Sales or the
worker's job is Area Manager.

– The values in the IF statement are those belonging to the worker'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
a ble
be true before the approval rule takes effect. f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

THEN Statements
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
a ble
• How many levels of the manager hierarchy above the first approver are included
f e r
• Available attributes and default values, if any, vary with the approver type an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

THEN Statements
The following table summarizes the approval actions:
Approval Action Description

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. The value of the Set Outcome To attribute for
manager hierarchies determines whether the transaction is
approved or rejected.
FYI only Notifications are issued to the identified approvers, but no
response is expected.
a ble
No approval required No notifications are issued and no approval is recorded for the f e r
transaction.
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Creating an Approval Rule
Search for the Create an

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

THEN statement. condition.
a ble
Customize Rule Add Rule
f e r
Parameters. Conditions.
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
9
1. On the Manage Approvals Transactions2 @ page,Stsearch for the transaction, such as Promote,
and click Configure. h a d this
s a use
2. On the Manage Approval
d m
( Rulesto page, click the + icon to create a new rule.
Note: You a a s e
h edit eannexisting
can rule to update the existing IF conditions and THEN
s li c
ed
statements.
m
ham
3. Add and select the IF condition to:
Mo - Customize 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.
Customize Rule
Add approvers
Configure the THEN Configure the IF Parameters
statement condition

Parameters Conditions
a ble
Determines the order Configure conditions for the
f e r
in which rules are run rules by using relational
ans
operators and expressions.
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
On the Manage Approval Rules page, click
d 2
9 thehRule1
i s Soval to configure:
• The Status and Priority sofathe
a
h approvale t rules
(m to u s
• The rule conditions
d
Priority s aha cense
• m eda rule set,lihigher priority rules run before lower priority rules.
Within
o h• amThe default priority is Medium.

MStatus
• Represents the status of the approval rule

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

transaction
Create an approval
rule
– Attributes
– Operators Customize Rule
Add approvers
statement condition
– 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.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
9
1. On the Manage Approvals Rule page, 2 @selectSthet Rule 1 oval and click Configure Rule
h a
Conditions to open the Condition
d Details
t h isdialog box.
s a use
m
( andtoclick Edit Selection to open the Approval Rules: Edit Condition
2. Select the 1=1 rectangle
d
a
ah cense
Expression dialog box.
s li Attributes are grouped into categories.
edan attribute.
3. Select
m
ham
For example, to select the requestor’s department:
Mo - 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

a ble
f e r
Worker’s Salary Component Details Current Change Amount, Proposed Changed Amount
an s
n - t r
Worker’s Salary Details no
Current Annual Salary, Proposed Annual Salary
a
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Requestor’s Assignment: Includes 9 2 @ S
attributes
tthat describe the assignment of the person
ad e thi s
that initiated the approvala h
request
s Includes
• ( m
Requestor’s Role Details:
t o us attributes that describe the role of the person that
h ad nrequest
initiated the approval
a se
• Worker’s
s
d Current e
licAssignment Details: Includes attributes that describe the current work
m e
assignment of the worker
h a m
Mo • 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
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9
For example: Construct an IF condition by 2 @ Sfollowing
using the
t Worker's Current Assignment
a d h i s
Attributes:
s ah use t
d m to
IF Worker's Current(Assignment.Location = "Chicago" and Worker's Current
a
ah cens
Assignment.Department e
= "Sales”
s li
m ed
o ham
M

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

• <<Condition 1>> <<Operator>> <<Condition 2>>
Search for the Create an approval

transaction rule
Customize Rule
Add approvers
statement condition

Parameters Conditions
2 3 1
a ble
f e r
an s
n - t r
a no Click the rectangle and
h a s click Edit Selection.
m ) e ฺ
o
b m t
i nฺi uden
To combine multiple rule expressions: 92
@ St
h a d this
a box,
1. In the Condition Detailssdialog
u s eselect the 1==1 rectangle and click Edit Selection. As
m
d ( value.
described in the previous slide,
to create conditions by using a combination of attributes,
a
a cens
operator, andhattribute e
s li and click a logical operator to add the operator to the left side of the
m edthe rectangle
2. Select
expression.
o ham - You can select one of the following operators: AND, OR, and NOT.
M
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
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
• 9
The Chart Builder view is the default2 @
view.s S
t
d thi
• ahaBuilder
Adding conditions in thesBlock
u s e view is similar to adding them in the Chart View.
To configure conditions d
m
( BlocktoBuilder view:
in the
a
h eview,
aBuilder n seselect the 1==1 rectangle and click Edit Selection to open the
s
1. In the Block
d Rules:licEdit Condition Expression dialog box.
e
Approval
m
2.
h a mSelect an attribute. Attributes are grouped into categories.
o
M 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
a ble
Customize Rule
f e r
s
Add approvers
an
statement condition
Customize Rule
Parameters
Add Rule Conditions
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Arrange approvers in the required sequence9 2 @ Stand dropping the approvers.
by dragging
h a d this
a use
Add the following types of approvers:
s
• d (
Management hierarchy
m to
a
h ens e
• Users sa
e d groupslic
•
m m
Approval
a
h• Position hierarchy
Mo • 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
a ble
f e r
an s
Identifies the first Indicates the top person in the
-
Indicates the list of approvers
n t r
no
approver in the list approval chain, usually the CEO that will be included
s a
) h a
m d e ฺ
o
ฺc Gu i Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
b m t
i nฺi uden
Action Type 9 2 @ St
h a d this
Select one of the following action
s atypes:use
• Approval required: d m
( Notifications
to are issued to the identified approvers and their response is
required. ah
a ns e
s c e
li No notifications are issued to the identified approvers. The transaction
•
m ed approval:
Automatic
o hamisapproved
either approved or rejected automatically, and the approvers are recorded as having
or rejected the transaction.
M
• 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.
a ble
f e r
ans
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Demonstration
• 3-1: Reviewing the Promotion Approval Rule

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
You can define more than one approver for a transaction.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
• On the Manage Approval Rules page, configure the 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.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
4
Approver Types
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives
After completing this lesson, you should be able to:

• Explain Approval Types
• Create an Approval Group
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uideCopyright © 2017, Oracle and/or its affiliates. All rights reserved.
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
f e r
Project Manager
Union
an s
representative
n - t r
a no Regional Manager
Payroll
h a s representative
m ) e ฺ
o
b m t
i nฺi uden
Application Roles 9 2 @ St
h a d this
• If your enterprise defines s aduty roles
u s efor security purposes, you can enter the duty role to
m
( sequence.
include it in the approval
d to
• A duty rolea a
ishassigned e
nsto several users.
s li c e
ed
Approval Groups
m
o h• amSelect an approval group, which consists of a predefined set of approvers configured to act
M 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 any additional responsibility types that your enterprise defines.
• Example: HR specialist

Approval Types
You can add the following types of approvers:

• Management Hierarchy
• Job-level Based Line Manager Hierarchy

• Users
• Position Hierarchy
• Representatives, who are workers with assigned responsibilities, for example Benefits
Representative
• Application Role
a ble
• Approval groups, which you define in BPM Worklist
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9
Note: Only the Manage Approval Transactions2 @ interface
S t supports Position hierarchies and
anotdsupport s
thithem.
representatives; BPM Worklist does
s a h e
( m t o us
a h ad nse
e d s lice
m m
h a
Mo

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
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9
Note: If your enterprise defines additional 2 @ St
types ofsmanagers, then they appear automatically in the
a d
h seRules
Approvers section of the ManageaApproval h i
t page; You can include them in the approval
sequence. s
(m to u
A business unit is a h
unit
d
a of annenterprise
se that performs one or many business functions that can be
s a e
e d lic hierarchy.
rolled up in a management
m m type defined for the plan determines the approvals hierarchy. You can create an
The hierarchy
a
oh approval hierarchy for a manager that overrides the plan hierarchy.
Malternate
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

a ble
f e r
an s
Mary Walton
n - t r
o
an
Administrator
s
ha ฺ
)
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
f e r
an s
n - t r
a no Contains a list of
h a s approval participants
m ) e ฺ
o
b m t
i nฺi uden
Management Hierarchy 9 2 @ St
h a d this
• Action Type s a use
- ( m
Approvaldrequired: o
tNotifications are issued to the identified approvers and their
h a s e
d sa licen
response is required.
- e Automatic approval: No notifications are issued to the identified approvers.
m
o ham - Information only: FYI only notifications are issued to the identified approvers, but no
M 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
You can include a job level in your approval sequence.

Job level routings are based on the manager hierarchy defined in Oracle Fusion Human
Capital Management. The approval list is generated based on the starting level specified in a
rule and continues until an approver with a sufficient job level is found. The approval flow
uses the job level defined in the Manage Jobs interface.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
f e r
an s
Store Manager n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• To use position trees: 9 2 @ St
h a d this
- s a must
The position hierarchy
u s ebe already defined
- The workers
d m
(must betoassigned corresponding positions
When using
a
h etrees
aposition n sein approvals, you cannot reference the position of a requester or
• s lic point to route the approvals. However, you can use a position tree, and
das the starting
e
worker
m
h a mselect positions within that tree to route an approval. For example, you can select the position
Mo “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
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Representatives
You can include holders of the following predefined responsibilities in your approval
sequence.
Note: 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 Resources Representative - Human Resource specialist assign

responsibilities to workers using Manage Areas of Responsibility task. A worker become
an approver for a transaction if he or she has the responsibility for the transaction
a ble
subject. f e r
For example, if you specify the Benefits Representative as an approver for a promotion, an s
then the Benefits Representative of the worker who is being promoted is invited to n - t r
no
approve the promotion.
a
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
If you use a responsibility holder, then ensure
@that responsibility
S t holders are already defined in the
a d h i s
trepresentative as an approver for an employee
s h asHR
application. For example, if you include
ahave e
process, then all employees ( m
must
t o uHR representatives assigned to them.
a h ad nse
e d s lice
m m
h a
Mo

Representatives
You can include holders of the following predefined responsibilities in your approval
sequence:
• Human Resources Representative
• Benefits Representative
• Union Representative
• Payroll Representative
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2 @ types,
If your enterprise defines additional responsibility S t then they appear automatically in the
ad eRules s
thi page. You can include them in the approval
h
Approvers section of the ManageaApproval
s
sequence. ( m t o us
Human Resource (HR) h d se assign responsibilities to workers using the Manage Areas of
aSpecialists
Responsibilitydtask.
a
s A worker
l i c enbecomes an approver for a transaction if he or she has that
m
responsibilitye for the transaction subject. For example, if you specify the Benefits Representative as
am for a promotion, then the Benefits Representative of the worker who is being promoted
anhapprover
o
Mis 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
• You can use any of the existing duty roles to include in your approval sequence.
• Drag and drop approvers into the approval flow.
Note: You can use any of the existing duty roles to include in your approval sequence. If
your enterprise defines duty roles for security purposes, then you can enter the duty role to
include them in the approval sequence. Users with job or data roles that inherit the duty role
become transaction approvers.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Use the Manage Approval Groups 9 2 @ SCapital
for Human
t Management task to create and
manage approval groups a a d h i s
byhusing the tFusion application or Oracle BPM Worklist.
s u s e
•
d ( m
Depending on the approver
ttype
o defined, approval tasks are routed to all members of an
a
ah cens
approval group serially. e
s li
m ed
ham
Mo

Demonstration
• 4-1: Creating an Approval Group

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
If you edit or delete an approval rule on the Manage Approval Rules page, then approvals
currently in progress complete as if the rule had not been edited or deleted.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
For positions with more than one position holder, the transaction is approved by the first
position holder to approve.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
Now that you have completed this lesson, you should be able to:
• Identify Approval Types
• Create an Approval Group
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

5
Approvals and Notifications

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Lesson Objectives
After completing the lesson, you should be able to:

• Describe approval notifications
• Customize approval notifications

• Describe FYI notifications
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2 @ you
Note that when you define the approval workflow, S tconfigure the approval action that determines
ad and s
hi any action is required from them.
twhether
s a h
how notifications are issued to approvers
e
( m t o us
a h ad nse
e d s lice
m m
h a
Mo

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
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
2
An FYI (For Your Information) participant9just
@ S
receives
ta notification task and the business process
ad e thi s
h
does not wait for the participant’saresponse.
s
( m t o us
a h ad nse
e d s lice
m m
h a
Mo

Customizing Approval Notifications
Add comments and attachments. Change the appearance of the notification.

a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Approvers of a transaction can: 9 2 @ St
h a d this
• a use posted by earlier approvers
View the comments andsattachments
• Add their own comments
d m
( andtoattachments
Any
a
h enand
acomments se attachments that they add are available in the notification only
- s lic as a part of the actual transaction.
dand not stored
m e
• amCustomize the approval notification by using the page composer
h
Mo - To edit the notification, click the Edit button on the top-right corner of the notification.
Note: You cannot edit others’ comments and attachments.
• Customize approval notifications in either the Design View or Source View.

Customizing Notifications Using the Composer: Design View
1 Click the Select pencil icon.

2 Select the field that you want to

customize and click Edit Component.
3 Configure the options.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
Design View is the default view.
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m
o ham
M

Customizing Notifications Using the Composer: Source View
1 Click the View choice

list and select Source.
2 Select the region and

click Add Content.
3 Select the component

that you wish to add to
a ble
your page.
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
9 2
To edit or customize existing fields, select
@ Sand
the field
t click the Edit pencil icon in the composer.
Configure the required options. aha
d thi s
s u s e
d ( m to
a
ah cens e
s li
m ed
m
M oha

Quiz Q
You can customize approval notifications in the following:
a. Design View
b. Source View
c. All of these
d. None of these
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: c d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
Approvers can:
• Customize approval notifications to:
– Add comments and attachments
– Change the appearance of the notification

• Edit a notification by using either of the following modes:
– Design view
– Source view
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
6
Oracle BPM Worklist

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
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
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
f e r
• Can approvers add other approvers
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• 9
Use the Manage Task Configurations 2 @for Human
S t Capital Management and Manage
s
ad etoththei BPM Worklist.
Approval Groups tasks to
s a h
navigate
s can be performed from the Manage Approvals page are
• ( m
The approval rule configurations
t o uthat
h adcan nbesconfigured
a subset of what
a e in the BPM Worklist.
•
s e
lic includes setting up:
d administration
General
e
m- Expiration and escalation policies
h a m
Mo - 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
a ble
Push Back No No Yes
f e r
Purge Yes Yes No
an s
Reassign and Release Yes Yes Yes n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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
a ble
Update Attachment and comment Yes Yes Yes f e r
an s
View Process History, View Sub Tasks, View Task History Yes Yes
n -
Yest r
o
Withdraw
s an Yes Yes No
) ha ฺ
ฺ c om uideCopyright © 2017, Oracle and/or its affiliates. All rights reserved.
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

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.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
You can configure task aggregation and 9 2 @notifications
error S t on the Configuration tab.
s
adcanebethmapped
i
Task aggregation has three stages
s a hthat s to an approval notification:
• Once per task: d (
m to u
a e
ns setting for the requisitions approval task.
aishthecdefault
-
d s
This
li e
m- e Within the same task, if the approver has been returned multiple times, then based on
o ham the approval rules defined, the approver will see only one worklist task or notification.
M • 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.
a ble
f e r
an s
n - t r
no
Allows to decide when to move
the task to Completed status
s a
) h a
m d e ฺ
o
ฺc Gu i Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
b m t
i nฺi uden
Enable Auto Claim: This option is selected9 2 @ S t This action is enabled when a task is
by default.
ad group.
anhLDAP
assigned to a position, a role, or a
s
thi There can be multiple users associated with a
e
s the approver
us claims the task first to prevent multiple users from
( m
group, role, or position; therefore,
t o
updating the task.
a h ad nse
e d s lice
m m
h a
Mo

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.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
d 2 i s S is expected.
FYI notifications are issued to approvers,9but no response
a
ah are:
Some of the FYI notifications insBPM e t h
(m to u s
• d
AbsenceCatchAllExceptionFYI
• s aha cense
ManageJobServiceExceptionFYI
ed li
• m
ManageLocationCatchAllExceptionFYI
o h• amManageOrgServiceExceptionFYI
M • 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
– This facilitates notifying participants about the change in the status of any assigned
task.
– You can set up as many notifications based on task status and message type.
• Reminder Settings
– These are used to send periodic reminders about the tasks assigned.
– You can set to either “before expiry” or “after assignment,” respectively.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Notification Settings 9 2 @ St
h a d this
aSMS,uvoice
Users can be notified via email,
s s e messages, or instant messages.
d ( m to
a
ah cens e
s li
m ed
o ham
M

Modifying Approval Rule: BPM Worklist
Click the
1
Assignees tab. In the SoaLabel box,
2
click the diamond icon.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
Use the Assignees tab to view and modify
@ St rule associated with the transaction.
the approval
h a d this
s a use
d ( m to
a
ah cens e
s li
m ed
o ham
M

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

• Route approvals to a single approver or to multiple approvers
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
An approval rule in a rule set consists of 9
d 2
the following:
i s S
• Rule Name
a
ah use t h
s
(m to
• Condition d
• List Builder
s haListeBuilder
aand n se specific attributes
e d type lic
Response
•
m m
a
oh• Auto Action
MCondition
• 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 list builder that is applicable 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
a ble
f e r
ans
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Vacation Rules
Set a vacation period to remove yourself from automatic task assignment during the dates
you specify.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
• Vacation rules are not applicable9
@ St
to2To Dostasks.
d thi
• If there are no vacation s ahayou
rules,
u s e manually reassign the tasks to new approvers.
can
( m
To set a vacation period,dperform tofollowing steps:
the
a
ah arrow s e
nadjacent
1. Click the s down e to the implementer login. Select Preferences.
e d l i c
m the Enable vacation period check box.
2. Select
m
o h3.a Provide start and end dates.
M 4. 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.

Setting the Transaction to Automatically Approve
Set the transaction to get automatically approved even when a newly added participant
rejects the transaction.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
1. In the Setup and Maintenance work 9 2 @ S t the Search button and search for the task
area,sclick
Manage Task Configurations a h adfor eHuman
thi Capital Management.
2. In the Search Results ( m s click
region, us the task name. This opens the BPM Worklist.
d se
aselect t o
3. Search for a
s h
and
e nan approval process, such as TransfersApproval.
li c
d Configuration
4. Clickethe tab.
m
h5.amIn the Early Completion Settings section, select the Complete task when participant
Mo 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

a ble
– Enable reminders to assignees, but not to the requestor.
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Disabling Email Notifications for Business 9 2 @ S
Processes
t
s
ad eto tspecify
hi when to send (or not send) email notifications.
Use the Notifications tab in BPM s a h
Worklist
If you do not want any email ( m o usto be sent for a specific business process, you can remove
notifications
t
a h
all the rows in the TaskadStatus
n e
stable.
s e
lic for a business process, perform the following steps:
d notifications
e
To disable email
m
1.am In the Setup and Maintenance work area, search for and select Manage Task
h
Mo 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.

Reassigning a Task
1 From the Actions list, select Reassign.

2 Select Reassign.
a ble
f e r
3 Provide a user or select a user group.
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
2 @ St
To reassign a task, perform the following9steps:
h a d this
1. From the HCM Cloud home s a page,
u s e Notification Icon (the Bell symbol).
access
2. Click the More Details
d m
( dropdown,
to select Human Capital Management.
a
ah cepage
3. The BPMsWorklist
e
ns opens.
4. Select
li task from one of these sections:
edthe required
m
o ham - My Tasks
M - 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.

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

• 6-2: Enabling Vacation Rules and Delegating Approval Responsibilities
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
How many approver types can you include in your approval sequence?
a. 4
b. 6
c. 3
d. Several
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: d d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
You can use Oracle BPM Worklist to:
a. Manage general administration values for all HCM tasks
b. Define approval conditions and rules

c. Create and maintain approval groups
d. All of the above
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: d d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
You can delegate your responsibilities to another person.
a. False
b. True
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: b d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
You can route approvals to a single approver or to multiple approvers serially, for HCM
processes.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
• 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.
• Set a vacation period to remove yourself from automatic task assignment during the
dates you specify.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
7
Working with Sandboxes

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Lesson Objectives
After completing this lesson, you should be able to:

• Explain the purpose of sandboxes
• Recognize the difference between the two types of sandboxes

• Identify the types of customizations available in sandboxes
• Create a sandbox
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Sandboxes: Overview
• Use a sandbox to implement and test your changes without impacting other users.
– Perform all customizations in the test-only sandbox.
– Replicate the changes into the integration sandbox and publish them to the mainline
code.
• Use the Sandbox Manager to access sandboxes.
– Sandbox Manager is a tool for managing different
types of customization changes that can be
applied to an application.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 Manage
From the Settings and Actions menu, select
d i s S Sandboxes to:
• Create a sandbox
a
ah use t h
(m tos
• Activate a sandbox
d
• s aha cense
Delete a sandbox
eda sandbox
Publish
li
• m
o h• amView available or published sandboxes
M

Working with Sandboxes
Create a Customize
Activate the
sandbox sandbox Artifacts
a ble
Publish the
f e r
sandbox
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
1. 9
When creating multiple sandboxes, 2 @ Stfor testing. You will never publish a testing
createsone
sandbox. a h ad e thi
2. ( m
To activate a sandbox:
s us
adsandbox t o
1. Select
s a h the
e n se
ic as Active button
2.edClick thelSet
ha mm - Only one sandbox can be active at a time.

M o - When a sandbox is active for your session, the sandbox name is displayed in the
global area.
- A sandbox remains active until you exit the sandbox, publish the sandbox, delete
the sandbox, or set another sandbox as active.
3. Customize your artifacts.
- Change an existing artifact.
- Change how an artifact is displayed on the page.
- Create a new artifact.
4. To publish a sandbox:
- Select the sandbox
- Click the Publish button
After you publish a sandbox, the sandbox session is closed and the sandbox is no longer active.

Types of Sandboxes
1. Sandboxes intended for migration

2. Sandboxes intended for testing only
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Sandboxes intended for migration: 9 2 @ St
h a d this
• a ucode
Are merged back to thesmainline
s e
Sandboxes intended ford
m
( only:to
testing
a
ah cand se produce no concurrent conflicts between sandboxes
ntherefore
• s
Are not published e
li sandboxes at the same time.
You can m edmany testing
have
o ham
M

Types of Customizations in Sandboxes
Sandboxes can contain the following types of customizations:

Metadata Security Flexfield

• This supports • This supports • Use the flexfield
making changes making data pages to make
to the security changes changes to
application's flexfields.
metadata • Capture in data
security enabled • Deploy the
• Capture in sandbox. changes to a
Metadata single flexfield
a ble
sandbox. sandbox. f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
To make sandbox changes available in the 9 2 @ Smetadata,
mainline
t perform either of the following:
a d t h i s
• ah security
Publish the metadata orsdata
s e sandbox.
uthe Deploy Flexfield to Sandbox menu item.
• Deploy the flexfield
d (bymselecting
t o
s aha cense
ed li
m
o ham
M

Multiple Users in Sandboxes
• When multiple users work in a sandbox, one user might overwrite the changes
performed by other as follows:
– Directly: By changing the same artifact object
– Indirectly: By updating metadata files shared between different artifacts

• A sandbox conflict occurs when:
– Multiple users use a single sandbox
— Conflicts within a sandbox
— Conflicts between sandboxes
– Multiple users use multiple sandboxes
a ble
• Sandboxes that are used for testing only and that are not published cause no conflicts
f e r
with each other.
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9
When multiple users customize an application 2 @by using
S t sandboxes, two types of concurrent conflicts
ad e thi s
occur: a h
s When
• ( m
Conflicts within a sandbox:
t o us users overwrite changes created by other users
• h ad sandboxes
Conflicts between
a n se (intended for publishing only): When multiple sandboxes
with e
s li c e
d same customized
the artifact are published to the mainline
m
o ham
M

Tips and Tricks About Sandboxes
• Wherever possible, publish your sandbox to the same release and patch bundle level in
which it was created. This will avoid potential conflicts.
• Always download your sandbox before you publish it and keep the zip file in a safe place in
case you need to re-import the sandbox at a later date. It is a good idea to keep a
spreadsheet where the first column is the sandbox name followed by a column for each
environment used on your project. As you import and publish each sandbox in a specific
environment, record the date in the spreadsheet.
• Once you have downloaded your sandbox, check to ensure the file size is not 0 bytes. This is
a good indication that your sandbox really does contain your personalizations.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Practice
• 7-1: Creating a Sandbox

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 hpractice.
Using your activity guide, perform the specified
d i s S
a
ah use t
s
(m to
d
s aha cense
ed li
m
o ham
M

Demonstration
• 7-1: Creating a Sandbox

• 7-2: Activating a Sandbox
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
You can have many testing sandboxes at the same time.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
More than one sandbox can be active at a time.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: b d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
A sandbox remains active until you:
a. Exit the sandbox
b. Publish the sandbox

c. Delete the sandbox
d. Set another sandbox as active
e. (A), (B), and (D)
f. All of the above
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: f d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
• Perform all customizations in the test-only sandbox.

• Replicate the changes into the integration sandbox and publish them to the mainline
code.
• A sandbox conflict occurs when:

– Multiple users use a single sandbox
— Conflicts within a sandbox
— Conflicts between sandboxes
– Multiple users use multiple sandboxes
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

8
Extensibility, Customization, and

Personalization Overview
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives
After completing the lesson, you should be able to explain:

• Extensibility
• Customization
• Personalization
• Customization Layers
• Advanced concepts:
– Rolling Back
– Downloading
– Uploading a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Extensibility, Customization, and Personalization
Extensibility
• Creating a completely new business object or page
Customization
• Changing an existing business object or page
Personalization
a ble
• Changes that every user of the application can make to f e r
certain artifacts at run time
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Personalization 9 2 @ St
h a d this
• s a for users
Personalization is retained
u s eeach time they log in to the application.
• For example, youdcan
m
( use theto page composer to:
a e
ns of a column in a table
ah thecewidth
-
d s
Change
li
m- e Rearrange regions on a page
o ham - Add or remove content

M

Extensibility
• Define the logo and background.

• Add a new page • Modify color schemes, including

containing an iframe. button colors.
Page Appearance • Create their own themes.
• Edit infolet titles and views. Customize:

• Move infolets. Infolets Structure
• Hide or show infolets.
• Create custom infolets by using
•
•
Navigator
Springboard
a ble
your BI analytics and reports. • Home page
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Customizations
• Use the page composer to customize:

– Dashboards
– Work areas for all or some users based Customize the
on a selected customization layer global area.
Customize a list
of components.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
• 9
The Administration menu is available 2 @ S t have appropriate roles, such as Application
onlysif you
Implementation Consultant h d hi Management Application Administrator.
oraHuman tCapital
s a us e
Customizing the Global Area ( m t o
• Modify the a
ad nse
UIhshell template.
• e d s lice
For example:
m m
o h a - Edit the links available in the global area.
M For example: Removing the Tags link from the header area
- Add company contact information to the footer.

Customizing a List of Components
• Components contain a set of configurable properties that control the appearance and
behavior of a particular component instance.
• Examples of components:
- Task flows
- Portlets documents
- Layout components
• Editable components display a blue outline when you place your cursor over them.
• You can use the page composer to perform the following tasks:
- Add components to a page.
- Change the layout of a page.
- Move components on a page.
a ble
Show and hide components on a page. f e r
-
ans
- Remove components on a page.
n - t r
o
- Customize a page title.
s an
- Customize a tasklist menu.
) ha ฺ
- Customize attributes for a flexfield on a page.
ฺ c om uide
- Customize popup content. ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
(m tos
d
s aha cense
e d li
m m
o ha
M

Managing Your Sandbox
• To customize components by using the page composer, you must create and
activate a sandbox.
• Any customizations made in a sandbox are visible only when the sandbox is active.
• After customizations are complete, publish the sandbox to make the customizations
available to other users.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Customization Layers
• They represent the scope of users that a customization impacts.

• The customization layers within HCM include:
– Site:
— Customizations made for all users.

– Country:
— Customizations made for all users of a specific country.
– Organization:
— Customizations made for a particular organization.
Site
a ble
f e r
an s
Country
n - t r
a no
Organization
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Before you create customizations,9 2 @will need
you S t to select the layer to which you want your
ad e thi s
s a h
customizations to be applied.
• Customization layers( m usonly for user interface customizations made through the
are invoked
t o
h
page composer.
a ad nse
• The e d scustomization
exact lice layers that are available for an application depend on that
m m
application family.
h a
Mo • Important: Use the Site layer for all your customizations.

Working with Shared Components
• The changes that you make to a shared component affects all instances of the
component.
• If an object is not part of a shared task workflow, only the instance that you edit is
affected.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Customizing Page Components
Edit page components in:

• Design View (Default mode): Provides a WYSIWYG rendering of the page and its
contents
• Source View: Provides a combined WYSIWYG and hierarchical rendering of page

components
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
When to use the Design View mode? 92
@ St
h a d this
• When you want to customize
s a content
u s e on dashboard pages, including the Welcome page in
the desktop UI.
d ( m to
• Customizea a ns e
allhthe external-facing landing and transactional partner management pages.
s c e
li result content.
• edthe search
Specify
m
o ham
When to use the Select View mode?
M • When you want to customize the properties of different UI elements, such as fields and table
columns.

Customization Flowchart
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha

Customizing the Springboard
• Use the Structures page to customize the navigator and springboard.

Structure page
Navigator Springboard
Category
a ble
f e r
an s
Page Entries
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
• A page entry is the navigator link9
@ St icon that opens a page.
or2springboard
h a d this
• A page is a single screen
s ato perform
u s erelated tasks.
• A few page entries
d m
( be grouped
may to under a category.
h a s e
On the Structures
d c encan:
sapage,liyou
• m e categories and page entries
Create
o h• amHide page entries

M • Resequence page entries

Rolling Back, Downloading, and Uploading
• Use the Manage Customizations dialog box:

– To roll back customizations for a specific page
– Download and upload a customization file
• Roll back only the customizations for the page.

• Don’t roll back other customizations made at the label’s save point.
• Download or upload a customization file to:
– Diagnose issues seen in the test environment
– Send files to Oracle Support Services for further diagnosing
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
To roll back customizations: 9 2 @ St
h a d this
1. Go to the page for which s ayou wish
u s e view customizations
to
2. From the Administration
d m
( menu, to select Customize <page name> Pages to open the page in
a
ah cens
the page composer. e
s li Manage Customizations.
3. On the
m edtoolbar, click
o h4.amTo promote a customization to the tip, click Promote for the corresponding artifact.
M 5. In the Promote Documents dialog box, select the label that you want to promote to the tip and
click OK.

Page Composer Migration
• After customizing the pages, migrate the metadata from the test to the production
environment.
• Use a single sandbox to publish and migrate customizations.
• Ensure that:
– The source and target environments are at the same patch level
– You do not publish the sandbox in your test environment before downloading the
customization file for migration
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• 2 @ St are at the same patch level. The patch levels
Ensure that the source and target9environments
must be the same when you h a
create
is in your test environment and when you
d thethsandbox
publish the sandbox(m sa use
in production.
a d e to the sandbox in your test environment before downloading the
• Ensure that you
s
do not s
ahfile cforenmigration.
publish
customization
e d purposesli and it is not After you publish a sandbox, it can no longer be used for
ha mm
migration possible to recover from this action.
o Page Composer Migration Steps

M To migrate all customizations from a sandbox to the production environment:
1. In the sandbox, select Manage Sandboxes from the Administration menu
2. Download the unpublished sandbox in which your customizations have been saved
3. Save the file to your local drive
4. Publish the sandbox
5. Log in to the production environment and select Manage Sandboxes from the Administration
menu
6. Import the sandbox file that you just downloaded
7. Set this sandbox as active, and validate that the migration was successful
8. Publish the sandbox to the production environment

Quiz Q
All customizations are applied to the entire site, so all users
see the changes.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
Answer: b d 2
9 his S
a e tenterprise, or user level.
ahat theussite,
s
Customizations can be completed
(m to
d
s aha cense
ed li
m
o ham
M

Quiz Q
Which statement is false about managing customizations?
a. Use the Manage Customizations dialog box to view and diagnose the runtime
customizations made by you or other users.
b. You may need to download or upload a customization to diagnose issues seen in the
test environment.
c. When you roll back customizations, you must roll back the entire file.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Answer: c 9 2 @ St
h a d this
s a youumust
When you roll back customizations, s e roll back the entire file. You can roll back
customizations for a specific
d m
( page, tnot
o all customizations.
a
ah cens e
s li
m ed
o ham
M

Summary
• Extensibility refers to creating a completely new business object or page.

• Customization refers to changing an existing business object or page.
• Personalization refers to the changes that every user of the application can make to certain
artifacts at run time.
• Use the Manage Customizations dialog box:
– To roll back customizations for a specific page
– Download and upload a customization file
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Moha
m
med
s li
d
s
aha cense
(m to
a d 2
ah use t
@
ฺ i b
9 his S
ฺ c
in tude
)
m nt G
s
om uide
ha ฺ
an
on - t r an
sf e r a b
le
9
Working with Page Composer

a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives

• Add content to a page
• Modify page appearances

• Apply conditional changes
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Adding Content
• In Source View, click Add Content to add the following to pages:

– Components
Hyperlink
— Instructional Text
— Image
– Reports
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 within
You can add content only to specific regions
d i s aSpage.
a
ah use t h
s
(m to
d
s aha cense
ed li
m
o ham
M

Adding Content
Navigate to the
Activate a page where you Switch to Source

Sandbox. want to add View.
content.
Close the Add the required

Select a valid
composer to view content, such as
the added hyperlinks or
container to add
content. a ble
component. instructional text.
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
Prerequisite: Ensure that you are in a sandbox.
@ St
Adding Instructional Text h a d this
s a use
1. In Source View, select
d m
( the region
to on the page where you would want to display the text.
a e
ns Text or HTML.
ah cofetype
2. Add a component
s li Content to open the Add Content dialog box. You can select from a wide
- edClick Add
m m range of task flows, portlets, layout components, and other types of resources.
h a
Mo - In the Text row, click Add.
- Click Close.
3. Switch to Design View mode.
- Click the View choice list and select Design.
- Click the Design button.
4. Click the Edit Text link to enter the instructional text.
5. Change font color, font face, and font size.
6. Close the page composer.

Inserting an Image
1. In Source View, select the page where you want to insert the image.
2. Click the Add Content link in the Composer menu to open the dialog box for selecting the
Resource Catalog components.
3. Select Image and click Add to add the image.
4. Click Close to return to the page.
5. Select the image component that has been added to the page and click Edit from the
Composer menu.
6. From the Component properties menu, in the Icon field, select Expression Builder.
7. In the Type a value or expression text box, enter
/personimage?personId=#{pageFlowScope.pPersonId}.
8. Click OK to return to the Component Properties page.
a ble
9. Click OK to return to the page where you inserted the image.
f e r
10. Close the page composer to view the image. ans
n - t r
Adding Reports
a no
1. In Source View, select the region on the page where you would
h a s like the report to display.
2. Click the Add Content link in the Composer menu to open m ) the dialog
e ฺ box for selecting the
Resource Catalog components.
o
ฺc Gu i d
b m t
3. Select an existing OTBI report from the Reports i nฺi uand e n
Analytics folder hierarchy. (Reports
dFolders > <<required folder>>.
and Analytics > BIPresentationServer 2 @ t
> Shared
S
4
4. Cli k th
Click the Add link
li k andd the h a dt 9willill appear
th report t h is on the
th page. Click
Cli k Close
Cl t return
to t to
t the
th page.
s a use
(m toof the embedded report, switch to Design View. Click the Edit
5. To customize the appearance
d
atheapage. e
link. Set stylehand othersproperties by using the Component Properties dialog box. Click OK
s
to return to e n
e d lic
m the page composer to view the page with the styled report.
6. Close
m
h a
Mo

Page Appearances
• Configure properties that control the appearance of components.

• For example:
– Change the label of the field.
– Hide fields.
– Rearrange toolbars and tabs.
– Modify the action menu.
– Mark fields mandatory.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Modifying Page Appearances
Modify page appearances by updating properties for individual components:
Task View Description

Mark fields mandatory. Source Select the Show Required check box.
Hide buttons. Design Deselect the Show Component check box on

the Display Options tab.
Set truncation level of output text. Design or In the Truncate At field, enter the text length. a ble
Source f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 his S
Prerequisite: Ensure that you are in a sandbox.
d
Marking Fields Mandatory sah
a e t
(m s
uthat the field is required.
d
Note: An asterisk is added t o
to indicate
1. In Sourcesa
ha enthe
View, click
serequired field.
e d lic to open the Component Properties dialog box.
m m
2. Click Edit Component
a
oh3. Select the Show Required check box.
MHiding Buttons
1. Highlight the button in Design View and select to edit it.
2. Deselect the Show Component check box on the Display Options tab.
Setting Truncation Level
1. Select and edit the component.
2. In the Truncate At field, enter the text length at which you desire truncation.

Applying Conditional Changes
• Conditionally display or hide components on a page.

• Hide user components and capabilities for which the end user does not have access.
• Use expressions to conditionally change the properties of elements.

• In Design View, to enter expressions:
– Select next to the property
– Select Expression Builder
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Conditionally Set Read Only Property
Requirement: Make the Success Criteria and Comments attributes read-only based on the
user type.
Read-only Editable
Success Criteria Comments

Worker
Editable Read-only
a ble
Success Criteria Comments
Other than
f e r
Worker
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• 9
For workers editing their own goals: 2 @ St
h a d this
- The Success Criteria
s a fielduswille be read-only and the Comments field will be editable.
• For others: d ( m to
The
a
h eCriteria
aSuccess e
ns field will be editable and the Comments field will be read-only.
- s li c
m ed
ha m
M o

Conditionally Set the Read Only Property
Success Criteria Option

Update the Read Only

In Source Mode, navigate to For the Read Only property, property:
Activate the Sandbox. the Goal Details page. navigate to the Expression
Builder. #{pageFlowScope.pParentF
low == ‘WORKER_HOME’}
Comments Option
For the Read Only property,

Update the Read Only
property:
a ble
Activate the sandbox.
In Source Mode, navigate to
the Goal Details page.
navigate to the Expression
Builder. #{pageFlowScope.pParentF
f e r
low ne ‘WORKER_HOME’}.
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Editing the Success Criteria 9 2 @ St
h a d this
• Navigate to the Expression
s a Builder
u s efor the property Read Only and enter the following
d ( m
expression: #{pageFlowScope.pParentFlow
t o == ‘WORKER_HOME’}. When this
ha entostrue,
expression evaluates
s a e which is the case for the worker, the Success Criteria appears
as read-only
e d to the licworker.
Editing
m m
Comments
h a
Mo • Select to edit Comments and, using the Expression Builder for the property Read Only, enter
the following expression: #{pageFlowScope.pParentFlow ne ‘WORKER_HOME’}. This
expression evaluates to true for managers and HR, and makes the Comments attributes
read-only for them.

Customization Migration
You can use the Customization Migration page to:

• Create a set of all customizations and extensions made to an application environment.
• Download the customization set and upload it into another environment.

• The customization set includes customizations across all product families.
• To open the Customization Migration page, select Navigator >Tools > Migration.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
You can use the Customization Migration9page 2 @to move S t customizations and extensions from any
ad e thHowever,
i s
s h
source environment to any targetaenvironment.
s
you must always perform your
customizations and extensions ( m in a
t
full
o u
test environment. Then use the Customization Migration
a h ad ntosaeproduction environment. As customization set migration doesn't

page to move these changes
provide a merge s
licein the database that are not preconfigured are updated if a matching
dset,capability, never customize or extend a production environment. When you import a
m e
customization the rows
record
a mexists. Otherwise a record is inserted.
oh customization set doesn't include all deletions. For example, the set does not include the
MThe
removal of a customization document using the Manage Customizations dialog box. After you import
a customization set into the target environment, you must examine the environment for any deletions
that you must make manually. Similarly, the customization set does not include roles or role
hierarchy changes. Changes made to Security Console have to be manually updated in the target
environment.

Tips and Tricks about Personalization
• Use a mouse when personalizing. Trying to personalize the application using the
Touchpad on your laptop will only lead to frustration. A mouse with a good scroll wheel
will allow for more effective scrolling in Source mode.
• Always carry out your personalizations in a sandbox. That way if you mess up, you just
need to delete the sandbox and start again. If you use a sandbox, as long as other users
are logged in under a different User Name, they can still use the same environment
without being affected by your changes. Also, a sandbox is the only way of migrating
your personalization between environments.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Demonstrations
• 9-1: Customizing Tabs on Application Pages Using Page Composer

• 9-2: Hiding the Submit Button on Workforce Modeling Page
• 9-3: Securing the Submit Button on Workforce Modeling Page

• 9-4: Enabling Infolets
• 9-5: Displaying a Button Conditionally
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Practices
• 9-1: Hiring an Employee

• 9-2 : Activating a Sandbox
• 9-3: Customizing the Springboard

• 9-4: Adding Hyperlink to a Page
• 9-5: Modifying Page Appearances
• 9-6: Change Menu Options in Smart Navigation
• 9-7: Renaming and Reordering Folder Tab
• 9-8: Reorder Fields on Job Table
a ble
• 9-9: Customizing Biographical Information in Page Composer f e r
an s
• 9-10: Viewing a Worker's Job and Position Name
n - t r
o
•
an
9-11: Hiding Popup on Manage Person Page
s
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 hpractices.
Using your activity guide, perform the specified
d i s S
a
ah use t
s
(m to
d
s aha cense
ed li
m
o ham
M

Quiz Q
Always activate a sandbox before performing customizations:
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Quiz Q
To hide a component, deselect the Show Component check box on the Display Options tab.
a. True
b. False
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
Answer: a d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Useful Sources of Information
• Fusion Applications Dev eloper Relations Blog

https://blogs.oracle.com/fadevrel/
• Personalizations – YouTube
https://www.youtube.com/user/FADeveloperRelations
• An open Forum Site for technical questions from the development community.
https://community.oracle.com/community/oracle-
applications/fusion_applications/customizations__extensions_and_integrations
• Setting Properties on Page Components
http://docs.oracle.com/cd/E15586_01/webcenter.1111/e10149/pages_build.htm
a ble
• Oracle Cloud Customer Connect -
f e r
https://cloudcustomerconnect.oracle.com/resources/c6fa0d1f1a/summary
an s
• Oracle HCM Cloud Developer Relations Resources n - t r
a no
https://blogs.oracle.com/fadevrel/developer-relations-resources
h a s
m ) e ฺ
o
b m t
i nฺi uden
Expression Language 9 2 @ St
h a d this
Expression Language Expressions s a use
( m to
http://docs.oracle.com/cd/E15586_01/webcenter.1111/e10149/wcsugappb.htm
d
a e
ns Pages
ah to cApplication
Expressions Relevant
s li e
ed
http://docs.oracle.com/cd/E15586_01/webcenter.1111/e10149/wcsugappb.htm
m
o ham
M

Summary
• To perform customizations, you must activate the sandbox.

• Add content to pages
• Configure properties that control the appearance of components.

• Use EL expressions to conditionally change
the properties of elements.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

10
Using Flexfields
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Lesson Objectives

• Describe flexfields and their components
• Describe the flexfield types

• Deploy flexfields
• Migrate flexfields
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Flexfield Concepts
• These are an extensible set of placeholder fields associated with business objects.
• Use flexfields to customize an application’s features without programming.
• Example: An airline manufacturer may require specific attributes for its orders that aren’t
predefined. Using a flexfield for the order business object, you can create and configure
the required attribute.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• Use flexfields to extend business9 2 @ andSmeet
objects
t enterprise data management
s
adthe edatathmodel
i or performing any database programming.
requirements without changing
s a h
• Flexfields help you (tom us data on the same database table.
captureodifferent
t
a h ad nse
e d s lice
m m
h a
Mo

Flexfield Components
Represents attribute
Segment
of information
A set of valid values

Specific configuration assigned to a flexfield
Structure Flexfield Value Set
of segments segment or other entity
outside of flexfields
a ble
f e r
A grouping of attributes
an s
that make segments Context
n - t r
a no available to an application
h a s
m ) e ฺ
o
b m t
i nฺi uden
Segments 9 2 @ St
h a d this
• a auflexfield.
Segments are subfieldsswithin
s e
• m
When configuringda(flexfield,to
define the appearance and meaning of individual segments.
h a s e
• Assign a s
d
value
l i en determines which values are valid for the segment.
a setcthat
• m e appear:
Segments
o ham - Globally wherever the flexfield is implemented

M - Based on a structure or context

Value Sets
• The basis of validation for a value entered into a flexfield segment by an end user
• Defined before configuring the flexfield, because you assign value sets to each segment as
you configure a flexfield
The validation type determines how the value of the field is validated for the assigned value set.
The types of validation are:
• Format Only, where you enter data rather than selecting values from a list
• Independent, where the list of values consists of valid values that you specify
• Dependent, where a valid value in a list of values derives from the independent value of
another segment
• Subset, where the list of values is a subset of the values in an existing independent value set
• Table, where the values derive from a column in an application table, which can optionally be
a ble
limited by a WHERE clause
f e r
ans
n - t r
The validation type determines how the value of the field is validated for the assigned value set.
no
The following are the seeded values:
a
• Format Only: End users enter data rather than selecting values
h a s from a list.
• Independent: The list of values consists of valid values m )
that you e ฺ
specify.
o
ฺcfrom the i d
uindependent value of another
• m
Dependent: A valid value in a list of values derives
b t G
segment. i nฺi uden
9
Subset: The list of values is a subset2 @of the S t in an existing independent value set.
values
•
ada column s
thini an application table, which can optionally be
• Table: The values derive s a h
from s e
limited by a WHERE ( clause.to u
m
Context a h ad nse
• e d sis relevant
A context liceto descriptive and extensible flexfields.
m m
o •
h a Descriptive flexfield segments can be context-sensitive.
M • Extensible flexfield segments must be context-sensitive.
• This is a way of reusing the same database column for a similar or different segment based
on different needs.
Structures
To produce different structures:
• Add segments
• Remove segments
• Rearrange the segment order
The database columns on which segments in different structures are based can be reused in
multiple structures.

Types of Flexfields
Types of flexfields:
• Descriptive flexfields:
– Add custom attributes to business object entities.
– Define validation for those object entities.

• Extensible flexfields
– Add multiple context-sensitive segments to the flexfield.
– There is no dependency on the number of segments predefined and registered for the
flexfield.
• Key flexfields
a ble
– Use key flexfields to capture a key, such as: f e r
Part number an s
—
n - t r
—
a no
Job code
Account code
h
—
a s
m ) e ฺ
o
b m t
i nฺi uden
Extensible Flexfields 9 2 @ St
h a d this
• Configure a one-to-many s arelationship
u s e between an entity and its extended attribute rows.
• Configure contexts d m
(in groupstoso that the attributes in the context always appear together in
a
ah cense
the user interface.
s li
d hierarchical
• Use e existing categories so that entities inherit the contexts that are configured
m
h• amOne-to-many relationship:
for their parents.
M o
- A product business object row can be extended to have multiple contexts.
- A product business object row can have multiple occurrences of the same context.
• Contexts are reusable throughout categories.

Descriptive Flexfields
• Only one context segment provides context sensitivity.

• The same underlying database column can be used by different segments in different
contexts.
Dimension Context Measurement Context
Attribute 1= Attribute 2 = Attribute 3= Attribute 1= Attribute 2 = Attribute 3=

Height Weight Depth Weight Volume Density
a ble
f e r
an s
Attribute 1 Attribute 2 Attribute 3 n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Example 9 2 @ St
h a d this
s a that
You can define a Dimensions context
u s e the following attributes:
uses
• d
ATTRIBUTE1 column
m
( for height
to
a
ahcolumn e
s width
nfor
• ATTRIBUTE2s li c e
• m ed
ATTRIBUTE3 column for depth
malso define a Measurements context that uses the same columns for other attributes:
hacan
You
o
M • ATTRIBUTE1 column for weight
• ATTRIBUTE2 column for volume
• ATTRIBUTE3 column for density
They are enabled for all business entities, but are optional.
They are of three types:
• Global segment, which is always available
• Context segment, which determines the context-sensitive segments that are displayed
• Context-sensitive segment, which is displayed depending on the value of the context
segment

Extensible Flexfields
• An extensible flexfield context:

– Can be defined as a single row, the same as descriptive flexfields contexts
– Can be defined as multi-row so multiple sets of values can be associated with the
same product business object row

– Can be set for translatable free form text values
– Are reusable throughout extensible flexfield categories
• An extensible flexfield category:
– Provides a means of organizing related data in associated contexts
– Can serve to associate any combination of contexts
a ble
– Can be in a hierarchy that logically organizes sets of categories that support
f e r
inheritance of contexts
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Ways to Deploy a Flexfield
• Deploy a flexfield to a sandbox to test the flexfield configuration before deploying it to the
production environment.
– In the Actions menu, click Deploy Flexfield to Sandbox.
• Deploy a flexfield to the production environment.

– Click the Deploy Flexfield button.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
To deploy a flexfield to a sandbox: 9 2 @ St
h a d this
• With flexfields, you do not
s aneedutoscreate
e a sandbox, because the deployment process
manages the flexfield
d m
( sandbox
to creation.
• a
ahhascitsenown
Each flexfield e
s sandbox.
s
d log outliand log back in to the application to see the updated flexfield
• You emust
m
mconfigurations.
h a
Mo • When you are satisfied with the changes, deploy the flexfield to the production environment.
To deploy a flexfield to the production environment:
• If a sandbox exists for the flexfield, it is automatically deleted after it successfully deploys.
• You must log out and log back in to the application to see the updated flexfield
configurations.

Flexfield Implementation Flow
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
• Managing flexfields involves:
d 2
9 his S
- Registering
a
ah use t
s
- Planning d (m to
a
ah cens
Configuring
e
-
d s li
m- e Deploying Flexfields
h• amApplications developers develop and register flexfields.
Mo • Administrators and implementers:
- Configure flexfields
- Optionally customize their appearance in the user interface
• The two types of deployment are for:
- A sandbox-enabled flexfield for testing flexfield behavior in a sandbox MDS
repository that is accessible only to the administrator who activates and accesses it,
not to users generally
- A mainline-enabled flexfield for applying the flexfield definition to the mainline MDS
repository where it is available to end users

Flexfield and Customization Set Migrations
Flexfield Migration
• To avoid synchronization issues, migrate flexfield customizations before migrating page
and BI customizations.
• Only flexfields with a deployment status of Deployed or Deployed to Sandbox are eligible
for migration.
Customization Set Migration
• This is used to move customizations from one environment to another.
• The customization set includes only the customizations and extensions. Personalizations
are not included.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Flexfield Migration 9 2 @ St
h a d this
• s aall your
After you are satisfied with
u s e extensible, and descriptive flexfield changes, you
key,
need to migrate these
d m
( customizations
to from the test to the production environment.
• a ns e
ah Configuration
Use the Manage Packages task to migrate flexfield customizations.
s
d process c e
li to the target environment automatically submits affected flexfields for
• The eimport
m
mredeployment.
h a
Mo • Important: Ensure that the source and target environments are at the same patch level. This
means that the patch levels must be the same when you create your sandbox in your test
environment and when you publish the sandbox in production.
Customization Set Migration
It is not a tool for backing up and restoring customizations in the same environment.

Demonstrations
• 10-1: Enabling Descriptive Flexfields on Personal Information Page

• 10-2: Hiding Descriptive Flexfields on Personal Information Page
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Practices
• 10-1: Exiting a Sandbox

• 10-2: Updating a Descriptive Flexfield
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
In this lesson, you should have learned how to:

• Define a flexfield
• Recognize flexfield components

• Determine types of flexfields
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

A
Functional Setup Manager: Enabling

Offerings for Initial Use
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
mm
M oha
Objectives
After completing this lesson, you should be able to do the following:

• Describe the applications implementation process
• Explain the different implementation roles

• Navigate to Oracle HCM Cloud Functional Setup Manager
• Identify the Functional Setup Methodology
• Enable offerings, functional areas, and features for initial use
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
2
9 Functional
This lesson introduces you to Oracle Fusion
d i s S Setup Manager.
a
ah use t h
(m tos
d
s aha cense
ed li
m
o ham
M
Oracle HCM Cloud: Approvals and Extensibility A - 2

Implementing Oracle HCM Cloud Applications
Compensation
Management
Lines
of
Business Workforce
Deployment
Oracle Fusion
a ble
Functional Setup Manager
f e r
an s
n - t r
n oDevelopment
Workforce
s a
a
) h eฺ
m
m ฺco Guid Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
t
i nฺib uden
9 2 @ inSOracle
Functional Setup Manager (FSM) is an application
t Fusion Applications suite, which is used
s
ad eofferings.
thi FSM provides an efficient and consistent
a h
to implement all Oracle Fusion Applications
sentire applications
implementation process for(them t o us implementation life cycle. The life cycle includes
a h ad implementation,
the planning, configuration,
n s e deployment, and ongoing maintenance steps of the
d s the applications.
functional setup of
l i ce Using FSM, you can:
• m e
Understand implementation requirements and plan accordingly.
m
h• a Configure applications to match your business needs.
o
M • Get complete visibility to set up requirements through guided, sequential task lists.
• Enter setup data through easy-to-use user interfaces available directly from the task lists.
• Export and import to rapid-start functional setup at different instances.
• Validate setup by reviewing setup data reports.

Key Benefits
FSM key benefits provide:

• Self-service administration
• Complete transparency
• Configurable and extensible features
• Reusable templates for rapid start and consistency across applications
• Comprehensive reporting
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
ฺc Gu i d
b m t
i nฺi uden
• 9 2 @ guided
Self-service administration: An integrated, S t process for planning, configuration,
aand thi s
d maintenance
implementation, deployment,
s a h s e enables management of all aspects of
( m
functional setup of Oracle Fusion
t o u applications at the business user level.
• h ad nsAuto-generated,
Complete transparency:
a e sequential task lists include prerequisites and
address s e
lic to give full visibility to end-to-end setup requirements of Oracle Fusion
d dependencies
m e
applications.
a m
h• Configurable and extensible: Prepackaged list of tasks for setting up Oracle Fusion
Mo applications can be easily configured and extended to better fit with the business
requirements.
• Reusable for rapid start: Specific implementations can be templatized to facilitate reuse and
rapid start of consistent Oracle Fusion applications setup across many instances.
• Comprehensive reporting: A set of built-in reports help to analyze, validate, and audit
configurations, implementations and setup data of Oracle Fusion applications.

Job Roles with Functional Setups User Permissions
The delivered job roles that inherit permissions from the Functional Setups User abstract
role are:
• Application Implementation Consultant
• Human Capital Management Application Administrator

• IT Security Manager
• Other functional users, such as line managers
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Application Implementation Manager
Users with this job role typically are responsible for managing the overall implementation of
the Oracle Fusion applications.
Plan Configure Implement
Analyze Requirements & Configure to Business

Generate Setup Tasks Monitor Progress
Design Implementation Requirements
a ble
f e r
Offerings Configure Offerings Manage Implement Projects
an s
n - t r
o
s an
) ha ฺ
ฺ i b m nt G
@ in tude
d 2
9 access
Application implementation managers have
i s S
to:
• Setup and Maintenancesah
a e t h
(m to u s
• Configure Offerings
d
• aha censeProjects
Manage Implementation
s
• Manage
li Packages
ed Configuration
m
o ham
M

Application Implementation Consultant
This is a super user job role for Functional Setup Manager with access to all setup
functionality.
Plan Configure Implement Deploy
Analyze Configure to Generate Collect Data Enter Setup

Setup Tasks Setup Export/Import
Requirements & Business Data
Design Requirements
Implementation
a ble
f e r
an s
Monitor
Progress Test
n - t r
a no& Import
Offerings
Export
Configure
Manage Implement Projects
h a s Offerings
m ) e ฺ
o
b m t
i nฺi uden
Users with this role can fulfill all aspects 9
@ St
of2the implementation life cycle.
a d t h i s
• Setup and Maintenancesah e
(m to u s
• Configure Offerings
d
• s aha censeProjects
Manage Implementation
Assigned
li
ed Implementation Tasks
•
m m
o h• a Manage Configuration Packages
M • Export and Import
• All Tasks
This role is usually granted sparingly to a limited number of individuals, and is mostly used during
smaller projects such as conference room pilots.

Human Capital Management (HCM) Application Administrator
• Users with this job role have access to all HCM setup tasks.
• This job role is typically used when you implement Oracle Fusion Human Capital
Management applications.
– Example: Users with this job role set up common objects owned by HCM, such as
departments and jobs.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Functional Users
• Subject matter experts from the lines of business

• Responsible for managing the setup data of their specific functional areas
Implement Deploy
Collect Data Enter Setup Data Test Verify Setup after

Export/Import
a ble
Manage Implement Projects Export & Import
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
Functional users have job roles that include
@ S
Functional
t Setups Duty or the equivalent product-
ad e thi s
specific setups duty. a h
s Dutyutos other job roles according to your business requirements.
d m
You can assign Functional (Setups to
a
ah access
Functional users have s e
nto:
s li c e
•
m ed Implementation
Assigned Tasks
o h• amSetup and Maintenance

M • Getting Started
• Tasks and Task Lists

Navigating to Functional Setup Manager
The Oracle HCM Cloud applications work area for Functional Setup Manager is called Setup
and Maintenance. Users with any of the Functional Setup–related enterprise roles use one
of the following two paths to navigate to Setup and Maintenance work area:
1. Settings and Actions > Administration > Setup and Maintenance

a. The Settings and Actions menu is accessed by clicking the user name.
2. Navigator > Setup and Maintenance
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Functional Setup Methodology
Guided Process for Application Implementation Life Cycle

Application Implementation Lifecycle
Export/ Transact Maintain

Plan Configure Implement Import
Configure
Offering Setup
or
Export Offering Setup
Data or Manage
a ble
Offerings Offerings Implementation Configuration Task Search
f e r
Projects Packages
an s
Functional Setup Manager Modules n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Whether you are implementing Oracle HCM 9 2 @Cloud S t
applications for the first time or making
a d h i s
h se t Functional Setup Manager provides an end-to-
incremental change to an existingaimplementation,
s
( m
end guided process for managing your
t o ufunctional setups throughout the entire implementation life
cycle.
a h ad nse
Every phase of s liceimplementation life cycle is supported by Functional Setup Manager.
d application
Each step e
mbuilds upon the decisions you make in the previous steps to provide a fully integrated
h a m
applications implementation process. You:
o
M • Analyze implementation requirements, design setup, and plan overall implementation using
Offerings.
• Configure applications to match your business requirements using Configure Offerings.
• Follow a predefined list of tasks required for the features you selected to implement using
Offering Setup or Generate setup tasks using Manage Implementation Projects.
• Export and import setups from one Oracle Fusion Applications instance to another using
Export Offering Setup or Manage Configuration Packages.
• Maintain setup over time by searching and performing tasks from Search.

Working with the Offerings Page
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
Implementers should start planning Oracle 9 2 @ St Applications implementation from the
HCM Cloud
h a d twork
Offerings page in the Setup and Maintenance h is area.
s a use
Before starting to implement,
d m
( the implementers
tothem with need to understand what functionality is offered by
a a
h ens
Oracle Fusion Applications, e
compare the business requirements, and then plan for
implementation s lic
d accordingly.
e
mwhich is a self-service portal, shows all Oracle Fusion Offerings in a single interface
m
Offerings,
a
oh implementers to easily get an overview of the applications.
Mallowing
• A standard set of reports for each Offering, which shows detailed information on various
implementation requirements, is also provided.
• The reports help implementers to plan for decisions that need to make in the later phases of
the implementation.

Working with Configure Offerings
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2 @ Stshould use Configure Offerings to select the
After finishing analysis of the Offerings, implementers
Offerings, Functional Areas, and a h
Features
isapplicable to their business.
ad ethatthare
Why Configure Offerings? (m
s us
t o
ad thensOfferings
e
•
s a h
How you configure
e determines how Oracle HCM Cloud application setups and
transactional
e li
d processes c work in your implementation. For setup, when Functional Setup
m
mManager generates a list of setup tasks during the implementation phase, only those tasks
h a needed to implement the selected Offerings, Functional Areas, and Features are included in
Mo the task list. Therefore, you get a targeted task list necessary to meet your implementation
requirements while irrelevant tasks are excluded.
• For transactional processes, application functionality and controls such as, form region, table
columns, buttons, or links, could be displayed or be hidden according to your Offering
configuration.
• Although offering configuration can be changed any time, the changes are not influence on
any of the existing implementation task lists. However, results of the changed configuration
are reflected in any new implementation task list generated after making the change.

Progressive Decision Making with Offering Hierarchy
Workforce
Local Install of Help
Deployment
(Feature)
(Offering)
Payroll Help Customization

(Functional Area) (Feature)
Workforce
Scheduling Custom Help Security
(Functional Area) (Feature)
Time and Labor

(Functional Area)
Workforce
a ble
Management
(Functional Area)
f e r
an s
Human Resources BI
Analytics
n - t r
a no (Functional Area)
h a s
m ) e ฺ
o
b m t
i nฺi uden
Offerings, Functional Areas, and Features 9 2 @ St in multilevel hierarchy to help implementers
are organized
in making decisions progressively h a
during t h is of Offerings. If an implementer decides that a
d configuration
s a usisenot applicable to his or her implementation, then making
certain module or application
d m functionality
(or application
to functionality that depends on the first one becomes
a
decision on other modules
ahSetup ns e
s
irrelevant. Functional
dparents.li c e Manager, therefore, presents the Functional Areas and Features in the
e
context of their
m
h a m
Mo

Enabling Offering and Functional Areas for Implementation
• An Offering or its Functional Areas can either be selected or not selected for
implementation. You select or deselect the Enable For Implementation check box to
specify your selection.
• The Provisioned column in Configure Offerings shows whether or not an Offering is

provisioned.
– Although Functional Setup Manager does not prevent users from enabling Offerings
that have not been provisioned, ultimately users are not able to perform the tasks
needed to enter setup data for those Offerings.
– When a user starts configuring a nonprovisioned Offering, Functional Setup Manager
shows a warning message explaining the consequence.
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Selecting Feature Choices
• If the selected Offerings and Functional Areas have dependent features, those features
are applicable when the corresponding Offering and Functional Area is implemented.
• In general, the features are set with default configuration based on their typical
usage. Implementers should always:

– Review the available feature choices for their selected Offerings and Functional
Areas.
– Configure the features as appropriate for their implementation.
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
A Feature provides one of the following three
@ types S
of
tselection choices:
adapply i
thnots
• Yes/No: If a Feature can s a h
either
s e or apply to an implementation, a single check box is
m
( Users
presented for selection. u
o select or deselect to specify yes (if it applies) or no (if it does
texample,
a d
h ens
not apply), respectively. e
For when implementing Sales offering, companies or
s a
enterprises
e ic decide to use Local Installation of Help or not.
d can leither
• m m Select: If a Feature has multiple choices but only one can be applicable to an
Single
a
h implementation, selection choices are presented as radio buttons. Users are able to turn on
Mo only one of the choices. For example, when implementing Financials offering a company or
an enterprise can choose to implement Subledger Accounting Method or Subledger
Applications Method, but not both.
• Multi-Select: If the Feature has multiple choices but one or more can be applicable to an
implementation, then feature choices are presented as check boxes. Users select all that
applies by selecting the appropriate choices. For example, in Incentive Compensation
(Offering), companies or enterprises can choose to implement reporting hierarchy as
Supervisor Hierarchy, Resource Management Hierarchy, or both.

Implementation Projects
a ble
f e r
an s
n - t r
a no
h a s
m ) e ฺ
o
b m t
i nฺi uden
9 2
An implementation project is the list of setup
@tasks S t are required for implementation of specific
that
ad e thi s
s a h
offerings and related functional areas.
The Implementation Project(m o us the following table columns.
page includes
t
Go to Task a h ad nse
d s lice
Opens a m e
task page that is assigned to you.
ha
Status
m
o
MDisplays the current status of the task. The status of a task or task list can be:
• Not Started
• In Progress
• Completed
• Execution Frozen
• Completed with errors

Predecessor Tasks
If any task list or task requires that another task be completed first, the other task is listed as a
predecessor task. The name of the predecessor task is displayed when the mouse is over the
number in that column. If there are multiple predecessor tasks, all are listed.
Assigned To
Displays the user or role to which the task is assigned.
Notes
If there are notes associated to the task, a number is displayed. Clicking the number displays the
note window.
View Reports
Click the icon to see any of the reports available for the task list.
a ble
f e r
ans
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Demonstrations
• Appendix A-1: Exploring Oracle HCM Cloud Applications Help

• Appendix A-2: Enable Offerings
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Summary
In this lesson, you should have learned how to:

• Describe the applications implementation process
• Explain the different implementation roles

• Navigate to Oracle HCM Cloud Functional Setup Manager
• Identify the Functional Setup Methodology
• Enable offerings, functional areas, and features for initial use
a ble
f e r
an s
n - t r
o
s an
) ha ฺ
ฺ c om uide
ฺ i b m nt G
@ in tude
d 2
9 his S
a
ah use t
s
(m to
d
s aha cense
ed li
m m
M oha

Oracle HCM Cloud: Approvals and Extensibility: license to use this Student Guideฺ

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle HCM Cloud: Approvals and Extensibility: license to use this Student Guideฺ

Uploaded by

Copyright:

Available Formats

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2018, Oracle and/or its affiliatesฺ

Learn more from Oracle University at education.oracle.com

1 Oracle HCM Cloud: Approvals and Extensibility

ha mmCustomizing Approval Notifications 5-5

6 Oracle BPM Worklist

Reassigning a Task 6-17

7 Working with Sandboxes

9 Working with Page Composer

Conditionally Set the Read Only Property 9-10

Oracle HCM Cloud: Approvals and

This lesson provides an introduction to the following:

Oracle HCM Cloud: Approvals and Extensibility 1 - 2

After completing the course, you should be able to:

– Create Approval Rules

Oracle HCM Cloud: Approvals and Extensibility 1 - 3

This course is designed for:

• Functional users who are responsible for managing approvals

Oracle HCM Cloud: Approvals and Extensibility 1 - 4

• Course content is delivered over one day.

— Student notes with additional information

Oracle HCM Cloud: Approvals and Extensibility 1 - 5

• The HCM Approvals documentation is available in the HCM Cloud Library.

Oracle HCM Cloud: Approvals and Extensibility 1 - 6

• Approval Management Overview

Oracle HCM Cloud: Approvals and Extensibility 1 - 7

Approval Management Overview

Oracle HCM Cloud: Approvals and Extensibility 2 - 2

• The key components that are used in approvals include:

Oracle HCM Cloud: Approvals and Extensibility 2 - 3

Oracle HCM Cloud: Approvals and Extensibility 2 - 4

• These policies determine the workflow events.

– By when the approver should approve the transaction

Oracle HCM Cloud: Approvals and Extensibility 2 - 5

The figure shows a two-level approval flow:

Oracle HCM Cloud: Approvals and Extensibility 2 - 6

View Failed and Pending Processes Bypass Approvals

Oracle HCM Cloud: Approvals and Extensibility 2 - 7

Oracle HCM Cloud: Approvals and Extensibility 2 - 8

• To manage approval processes, Fusion Applications use the approval-management

Oracle HCM Cloud: Approvals and Extensibility 2 - 9

Approval Rules Configuration

Oracle HCM Cloud: Approvals and Extensibility 3 - 2

• Approval rules determine a transaction’s approval process.

• You can configure multiple approval rules for a transaction.

Oracle HCM Cloud: Approvals and Extensibility 3 - 3

Oracle HCM Cloud: Approvals and Extensibility 3 - 4

An approval rule has the following parts:

• THEN statements determine the approvers.

Oracle HCM Cloud: Approvals and Extensibility 3 - 5

worker's job is Area Manager.

Oracle HCM Cloud: Approvals and Extensibility 3 - 6

THEN statements determine:

• Any actions that approvers are expected to take

Oracle HCM Cloud: Approvals and Extensibility 3 - 7

The following table summarizes the approval actions:

Approval Action Description

Oracle HCM Cloud: Approvals and Extensibility 3 - 8

Search for the Create an

Configure the Configure the IF

Oracle HCM Cloud: Approvals and Extensibility 3 - 9

Click the rule box to Search for the Create an approval

Customize Rule Add Rule

o h• amThe default priority is Medium.