My Oracle Support Banner

Incorrect Rules are Fired for "Approve Talent Profile Content" when "Worker's Assignment.result.Business Unit" is Used in the Rule (Doc ID 2809222.1)

Last updated on OCTOBER 01, 2021

Applies to:

Oracle Fusion Profile Management Cloud Service - Version 11.13.21.07.0 and later
Information in this document applies to any platform.

Symptoms

A Content Section has been set up which requires Approval. The following rules have been created in Transaction Console/Approval Rules for "Approve Talent Profile Content". The intention behind the rule is that when an Employee adds a Talent Item to their profile, a different rule will fire, depending on the Business Unit to which the employee belongs.

Rule 1: BusinessUnitExists

((transactionApprovalRequest.attribute2 equalsIgnoreCase "PERSON_APPROVAL_REQD") AND

((Worker's Assignment.result.Business Unit == "BusinessUnitA") OR (Worker's Assignment.result.Business Unit == "BusinessUnitB")))

This rule sends the Approval to ApproverTestX

Rule 2: BusinessUnitNotExists

((transactionApprovalRequest.attribute2 equalsIgnoreCase "PERSON_APPROVAL_REQD") AND

((Worker's Assignment.result.Business Unit != "BusinessUnitA") OR (Worker's Assignment.result.Business Unit != "BusinessUnitB")))

This rule sends the Approval to ApproverTestY

An Employee who is in BusinessUnitA goes to:

However it can be observed that the approval goes to both ApproverTestX and ApproverTestY because both rules have fired. This is unexpected behaviour, because the Employee is in BusinessUnitA, so the expectation was that only the Rule1 "BusinessUnitExists" would fire.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.