Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Same Person With Different AOR In Approval Workflow Is Getting Skipped At 1st Level
Summary:
Same person is assigned 2 different Areas or Responsibilities (AOR) and are added in the approval process for the Requisition Creation approvals.
The "Task Aggregation" is already set to "None" but still the person is skipped at 1st Level (or at first occurrence) and the transaction approval notification is received at the 2nd Level (or at second occurrence). We want the approval should be triggered twice to the person even if the person is same.
Content (required):
Example:
Approver Level 1: Head of Strategic HR (Mr. ABC)
Approver Level 2: Finance Manager (Ms. XYZ)
Approver Level 3: Executive Business Office (Mr. ABC)
Version (include the version you are using, if applicable):
0