Version: Release 9.

There are three departments (HR, Sales and Marketing). Now an HR Specialist AA transfers an employee EE
from Sales department to Marketing department. Below is the picture showing the supervisory reporting
hierarchies and the Job Level information. LL is the CEO (the topmost supervisor).

Supposing the expected approval rule for the transfer is: Supervisor holding Job Level 3 within the
requestor’s supervisory hierarchy -> Supervisor holding Job Level 5 within the worker’s current
supervisory hierarchy -> Supervisor holding Job Level 4 within the worker’s proposed supervisory
hierarchy.

For this example, the requestor is AA, the worker is EE, and the approvers will be CC -> LL -> KK.

Here are the details/screenshots for making the approvals via BPM Worklist and via FSM task of Manage
Approval Transactions for Human Capital Management.

1. In the BPM Worklist, three sections are included in the rule sequentially as shown in the following
screenshot.

The first section is for Supervisor holding Job Level 3 within the requestor’s supervisory hierarchy.
※ List Builder is Job Level
※ Number of Levels is 3 (both for “At most” and “At least”, “relative to” is set as Absolute)
※ Starting Participant (from the requestor’s 1st level manager):
HierarchyBuilder.getManager("supervisory",Task.payload.transactionApprovalRequest.Req
 uestor,-1,null,"LINE_MANAGER")
※ Top Participant (to the topmost supervisor in the system. "YIMING.LU@FUSIONSTAR.COM" is
the user name for the CEO LL in my example, the customers need replace it with the user name
for the topmost supervisor (usually CEO) in their own systems):
HierarchyBuilder.getPrincipal("YIMING.LU@FUSIONSTAR.COM",-1,null,"HierType")
※ Utilized Participants is Final Approver only

The second section is for Supervisor holding Job Level 5 within the worker’s current supervisory
hierarchy.
※ List Builder is Job Level
※ Number of Levels is 5 (both for “At most” and “At least”, “relative to” is set as Absolute)
※ Starting Participant (from the worker’s current 1st level manager):
HierarchyBuilder.getPrincipal(GetManager("LINE_MANAGER",Task.payload.Worker's
Current Assignment.result.Assignment Supervisor),-1,null,"LINE_MANAGER")
※ Top Participant (to the topmost supervisor in the system. "YIMING.LU@FUSIONSTAR.COM" is
the user name for the CEO LL in my example, the customers need replace it with the user name
for the topmost supervisor (usually CEO) in their own systems):
HierarchyBuilder.getPrincipal("YIMING.LU@FUSIONSTAR.COM",-1,null,"HierType")
※ Utilized Participants is Final Approver only

The third section is for Supervisor holding Job Level 4 within the worker’s proposed supervisory
hierarchy.
※ List Builder is Job Level
※ Number of Levels is 4 (both for “At most” and “At least”, “relative to” is set as Absolute)
※ Staring Participant (from the worker’s proposed 1st level manager):
HierarchyBuilder.getPrincipal(GetManager("LINE_MANAGER",Task.payload.Worker's
Proposed Assignment.result.Assignment Supervisor),-1,null,"LINE_MANAGER")
※ Top Participant (to the topmost supervisor in the system. "YIMING.LU@FUSIONSTAR.COM" is
the user name for the CEO LL in my example, the customers need replace it with the user name
for the topmost supervisor (usually CEO) in their own systems):
HierarchyBuilder.getPrincipal("YIMING.LU@FUSIONSTAR.COM",-1,null,"HierType")
※ Utilized Participants is Final Approver only

2. FSM task of Manage Approval Transactions for Human Capital Management provides a more direct and
easier way for editing the approval roles, so a lot of customers prefer this way on managing the HCM
approval rules. Three nodes are needed in the rule sequentially as shown in the following screenshot,
via the FSM task of Manage Approval Transactions for Human Capital Management, all of them are
based on “Job-Level-Based Line Manager Hierarchy”.
The details of the first node (for Supervisor holding Job Level 3 within the requestor’s supervisory
hierarchy):

※ “Approval Chain of” is Requestor

※ “Start With” is Manager (the 1st level manager of the requestor)
※ “Minimum Job Level” is 3
※ “Top Approver” is user
※ “User Name” : "YIMING.LU@FUSIONSTAR.COM" is the user name for the CEO LL in my example,
the customers need replace it with the user name for the topmost supervisor (usually CEO) in
their own systems
※ “Include” is Last approver only

The details of the second node (for Supervisor holding Job Level 5 within the worker’s current
supervisory hierarchy):

※ “Approval Chain of” is Worker’s Current Line Manager

※ “Start With” is Employee. Note: on this UI, when “Approval Chain of” is Worker’s Current Line
Manager (or Worker’s Proposed Line Manager) and you want to start with the worker’s current
1st level manager (or worker’s proposed 1st level manger), you have to set “Start With” as
Employee, if you set “Start With” as Manager then the approval chain will start with worker’s
current 2nd level manager (or worker’s proposed 2nd level manger) actually. Please remember
this.
※ “Minimum Job Level” is 5
※ “Top Approver” is user
※ “User Name” : "YIMING.LU@FUSIONSTAR.COM" is the user name for the CEO LL in my example,
the customers need replace it with the user name for the topmost supervisor (usually CEO) in
their own systems
※ “Include” is Last approver only

The details of the third node (for Supervisor holding Job Level 4 within the worker’s proposed
supervisory hierarchy):

※ “Approval Chain of” is Worker’s Proposed Line Manager

※ “Start With” is Employee. Note: on this UI, when “Approval Chain of” is Worker’s Proposed Line
Manager (or Worker’s Current Line Manager) and you want to start with the worker’s proposed
1st level manager (or worker’s current 1st level manger), you have to set “Start With” as
Employee, if you set “Start With” as Manager then the approval chain will start with worker’s
 proposed 2nd level manager (or worker’s current 2nd level manger) actually. Please remember
this.
※ “Minimum Job Level” is 4
※ “Top Approver” is user
※ “User Name” : "YIMING.LU@FUSIONSTAR.COM" is the user name for the CEO LL in my example,
the customers need replace it with the user name for the topmost supervisor (usually CEO) in
their own systems
※ “Include” is Last approver only