BPM Approvals Variation

11/5/2019 Document 2546400.
PowerView is Off Switch to Cloud Support Rohit (Available) (0) Contact Us Help
Dashboard Knowledge Service Requests Patches & Updates Community
Give Feedback...
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.
How to Create an Approval Rule Which allows the HR_REP to Create a Document Record without Approval but which To Bottom
Requires a Non-HR_REP to Get Approval via their Line manager (Doc ID 2546400.1)
In this Document Was this document helpful?
Goal Yes
No
Solution
References
Document Details
Type:
HOWTO
Status:
APPLIES TO: Last Major
PUBLISHED
18-Jul-2019
Update:
18-Jul-2019
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.19.01.0 and later Last Update:
Information in this document applies to any platform.
Related Products
GOAL
Oracle Fusion Global Human
Resources Cloud Service
To Create an Approval Rule, which allows the HR_REP to create a document record without approval, but which requires
a non_HR_REP to get approval via their line manager. In this article, the example used is for when the document type is one
which requires authorization. Information Centers
Oracle Applications Cloud –
Please note, that at the moment, it is not possible to retrieve the Requestor's role in the Manage Document Records Approval Information Center for
Rules, so this is a workaround for that. There is an ER logged for this bug:21442000 "ENH 21442000 - NEED DOCUMENT OF Administrators [110.2]
RECORD APPROVAL BASED ON ROLE OF REQUESTOR"
Document References
SOLUTION
No References available for this
document.
1.Choose a test employee and check their HR_REPS
Go to home/my client groups/Person management/search Recently Viewed

search for the employee (who you want to add document records for)
Click on the employee name to bring up the employee record Role based Auto Approval
condition giving error in BPM
At the right hand side, click on the 'headphone' icon.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=293681813297466&id=2546400.1&displayIndex=2&_afrWindowMode=0&_adf.ctrl-state=52b8jivy3_227#FIX 1/19
11/5/2019 Document 2546400.1
It will show the HR reps for this employee. Worklist Advance Mode
Make a note of the HR reps (as you will first do the testing by entering the document record as the HR rep) [2417293.1]
Fusion Global Human
For example: Resources -- Workflow Not
Triggering When Employee
Has Two Roles [1928065.1]
Configuring Approval Rules
using Advanced Mode in
Oracle BPM Worklist: Worked
Example [2267369.1]
Fusion Applications BI
Publisher : When calling the
BI Publisher runReport
method and returning a PDF
document, the reportBytes
output cannot be read as a
PDF once base64 decoded
[2039080.1]
Fusion Applications BI
Publisher: Execute Web
Service Rest Publisher
[2259073.1]
Show More
2.Setup the rule in BPM:
Click on bell icon/more details/drop down (name) menu

Go to Administration/Task Configuration
search for "DocumentOfRecordApproval"
For example:
11/5/2019 Document 2546400.1
Then:
click on 'edit' icon (pencil icon) (next to "tasks to be configured)

click on "Assigness" tab
Click on the blue dot next to the "Document Record Approvers" box and choose "go to rule"
11/5/2019 Document 2546400.1
3.The rule should be entered like this:
If
box 1:Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired
is
box2:"Y"
box3:GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result)
contains
box4: Task.payload.transactionApprovalRequest.Requestor
11/5/2019 Document 2546400.1
Then
List Builder
Response Type: Required
Number of Levels:1
Starting
Participant:HierarchyBuilder.getPrincipal(Task.payload.transactionApprovalRequest.Requestor,-1,"","LINE_MANAGER")
Top Participant:
HierarchyBuilder.getPrincipal(Task.payload.transactionApprovalRequest.Requestor,-1,"","LINE_MANAGER")
Auto Action Enabled:True
Auto action: "APPROVE"
Rule Name: "RequestorIsHR_REP"
The Whole rule looks as follows:
11/5/2019 Document 2546400.1
In non edit mode:
11/5/2019 Document 2546400.1
Which is:
(Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired is "Y" and

GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result)
contains Task.payload.transactionApprovalRequest.Requestor)
When viewed from the transaction console:

Home/tools/transaction console/approval rules tab/Search for “Manage Document Records” – it looks as follows:
11/5/2019 Document 2546400.1
4.Copy the new rule, and give it a new name and a new "Then" action (it needs a new ‘then’ action, because the approval action
needs to be different if the requestor is not a HR_REP). To copy the rule in BPM worklist,:
tick the box next to the rule name

then go to the scissors icon and click on 'copy'
Then click on the scissors icon and click on 'paste'
For example:
11/5/2019 Document 2546400.1
5. Give the new rule, a user friendly name (as by default it will be the name of the copied rule with a number after it). In this
example the new rule is called "RequestorIsNotHR_REP"
6. It's now necessary to edit this rule so that it becomes an inverse (because there isn't a "doesn't contain" operator). This
means it's necessary to negate the whole rule of the second section of the rule, so that it uses a ‘not’ condition. To do this,
Tick the second half of the rule (box 3)

Click the green cog icon
choose selected tests/not
For example:
11/5/2019 Document 2546400.1
It should look like this:
11/5/2019 Document 2546400.1
To enter it:
If
box1:Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired
is
box2:"Y"
and
NOT
box3:GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result)
contains
box4: Task.payload.transactionApprovalRequest.Requestor
The “Then” part will look like:
11/5/2019 Document 2546400.1
In non-edit mode, it looks like this:
11/5/2019 Document 2546400.1
which is:
(Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired is "Y" and

NOT(GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result)
contains Task.payload.transactionApprovalRequest.Requestor))
In the transaction console/approval rules, it will look like this
((getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "Y") AND

(NOT (GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result)
contains transactionApprovalRequest.Requestor)))
for example:
11/5/2019 Document 2546400.1
7. Test the rule as someone who is a HR_REP:
11/5/2019 Document 2546400.1
8. Test the rule as someone who is not a HR_REP:
11/5/2019 Document 2546400.1
Variations on the Above
The above is a detailed example of how the approval rules can be set for this particular scenario. Normally this would be done in
conjunction with other rules, for example, the default rule 'DocumentAutoApprovalRule' would still be needed, as this is a rule that
self approves all documents that do not require authorization. The above example, is only for documents which require
authorization. It may also be a customer requirement to create rules that act differently, according to the name of the document
being uploaded.
How can the above rule be modified so that if the HR_REP is uploading their own document record, then it still
needs approval from their line manager. But if the same HR_REP is uploading for anyone else (who they are
the HR_REP for), then it doesn't need approval?
This can be achieved by adding in the following clause:
getRequestorInformationByPersonIdResponse.User Name == transactionApprovalRequest.Requestor
If the above needed to be implemented (HR_REP cannot upload their own document records without approval from their own
manager), in total the rules would look like this:
Rule 1:DocumentAutoApprovalRule
11/5/2019 Document 2546400.1
This rule fires if:
the document does not require authorization
The example requirement is for documents which don't require authorization to be self auto approved.
Rule name: DocumentAutoApprovalRule

status:active
rule conditions: (getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "N")
then: self auto approve
Rule 2:HR_REPButOwnRecord
This rule fires if:
the document requires authorization and

the requestor is a HR_REP and
the requestor is updating their own record
The example requirement is that this will need line manager approval
rule name:HR_REPButOwnRecord
status: active
rule condition: ((getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "Y") AND
(GetAllRepresentatives("HR_REP",Task.payload.getRepresentativeListWrapperResponse.result) contains
transactionApprovalRequest.Requestor) AND (getRequestorInformationByPersonIdResponse.result.User Name ==
transactionApprovalRequest.Requestor))
then : job level based line manager hierarchy
Rule 3: HRREPbutNOTOwnRecord
This rule fires if:
the document requires authoriziation

and the requestor is a HR_REP
and the requestor is not updating their own record
The example requirement is that this will be automatically approved
rule name:HRREPbutNOTOwnRecord
status: active
rule condition: ((getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "Y") AND
11/5/2019 Document 2546400.1
transactionApprovalRequest.Requestor) AND (getRequestorInformationByPersonIdResponse.result.User Name !=
transactionApprovalRequest.Requestor))
then: self auto approve
Rule 4: RequestorIsNotHR_REP
This rule fires if:-
the document requires authorization and

the requestor is not a hr rep
The example requirement is that this will go for line manager approval
rule name:RequestorIsNotHR_REP
status: Active
rule condition:((getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "Y") AND (NOT
transactionApprovalRequest.Requestor)))
then: job level based line manager hierarchy
Please note that the previously created rule "RequestorIsHR_REP" (which was created at the start of this note) needs to be set to
'inactive' or removed. Because now in this new scenario it has been replaced by rule 2 and 3 above, which will check whether the
requestor (eg. HR_REP) is the same person, as the person for who the document is being uploaded.
11/5/2019 Document 2546400.1
REFERENCES
BUG:21442000 - NEED DOCUMENT OF RECORD APPROVAL BASED ON ROLE OF REQUESTOR.

Didn't find what you are looking for? Ask in Community...
Related
Products
Oracle Cloud > Oracle Software Cloud > Oracle Human Capital Management Cloud > Oracle Fusion Global Human Resources Cloud Service > Global Human Resources > Approvals
Back to Top
Copyright (c) 2019, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

BPM Approvals Variation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BPM Approvals Variation

Hochgeladen von

Copyright:

Verfügbare Formate

11/5/2019 Document 2546400.

Dashboard Knowledge Service Requests Patches & Updates Community

In this Document Was this document helpful?

Go to home/my client groups/Person management/search Recently Viewed

2.Setup the rule in BPM:

Click on bell icon/more details/drop down (name) menu

click on 'edit' icon (pencil icon) (next to "tasks to be configured)

3.The rule should be entered like this:

Response Type: Required

Auto Action Enabled:True

Auto action: "APPROVE"

Rule Name: "RequestorIsHR_REP"

The Whole rule looks as follows:

In non edit mode:

(Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired is "Y" and

When viewed from the transaction console:

tick the box next to the rule name

Tick the second half of the rule (box 3)

It should look like this:

In non-edit mode, it looks like this:

(Task.payload.getNewDoRByTransactionIdResponse.result.AuthorizationRequired is "Y" and

In the transaction console/approval rules, it will look like this

((getNewDoRByTransactionIdResponse.result.AuthorizationRequired == "Y") AND

7. Test the rule as someone who is a HR_REP:

8. Test the rule as someone who is not a HR_REP:

Variations on the Above

This can be achieved by adding in the following clause:

getRequestorInformationByPersonIdResponse.User Name == transactionApprovalRequest.Requestor

This rule fires if:

the document does not require authorization

Rule name: DocumentAutoApprovalRule

This rule fires if:

the document requires authorization and

This rule fires if:

the document requires authoriziation

The example requirement is that this will be automatically approved

This rule fires if:-

the document requires authorization and

BUG:21442000 - NEED DOCUMENT OF RECORD APPROVAL BASED ON ROLE OF REQUESTOR.

Das könnte Ihnen auch gefallen