Implementing Workflows, Approvals and Notifications

Priya's promotion must be governed from submission to database commit.

Concept in four layers

What you must understand

• Human workflow routes tasks automatically for consideration or action.
• BPM is the task engine; AMX supports complex multistage routing.
• An approved transaction is committed only after the required approvals complete.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Identify the HCM transaction and its delivered approval policy.
2. 2Confirm the initiating user, worker, effective date, and proposed values.
3. 3Map submission, routing, decision, completion, and notification states.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Approval Architecture scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Transaction identifier
• Approval history
• Final HCM record

Common failure paths

• Approval does not replace function or data security.
• A transaction with no applicable approval policy can auto-approve.

Asha can reassign an HCM task but cannot edit approval rules.

Concept in four layers

What you must understand

• Family-specific workflow roles allow administration of submitted tasks.
• BPMWorkflowAdmin is required to configure workflow tasks and rules.
• BPMWorkflowAllDomainsAdmin spans product families and should be tightly controlled.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Separate operational task administration from rule-design authority.
2. 2Provision least privilege.
3. 3Retest reassign, recover, rule configuration, and cross-domain visibility.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Workflow Roles and Access scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Role inheritance report
• Successful/denied action test

Common failure paths

• Access to Transaction Console does not automatically allow BPM rule design.
• All-domains access is broader than HCM-only administration.

Priya's transfer is pending longer than expected and the HR administrator must locate the bottleneck.

Concept in four layers

What you must understand

• Transaction Summary monitors status and supports search, export, logs, and actions.
• Analytics provides workflow dashboards; Approval Rules controls policies.
• Archived Transaction Summary separates retained completed work from active work.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Search by process, initiator, worker, status, and submission date.
2. 2Open the instance and inspect participants, task history, and diagnostic log.
3. 3Choose the least destructive valid action and verify the resulting state.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Transaction Console scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Diagnostic log
• Participant history
• Action audit

Common failure paths

• Do not recover a transaction that is merely awaiting a valid approver.
• Available actions depend on status and custom-role privileges.

A task is errored, but the business request is still valid.

Concept in four layers

What you must understand

• Recover retries an eligible failed transaction after the cause is corrected.
• Reassign changes the assignee; withdraw removes a submitted request; terminate ends the process administratively.
• Approve, reject, edit cache, resend email, comment, and alert initiator solve different problems.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Classify the issue as routing, data, notification, or cancellation.
2. 2Confirm whether the underlying transaction must remain valid.
3. 3Act, document the reason, and retest the end state.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Transaction Actions scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Before/after status
• Administrator comment
• New assignee or completion state

Common failure paths

• Terminate is not a repair action.
• Resending an email does not change the task assignee or routing.

India promotions to Grade 6 require two management levels; other promotions require one.

Concept in four layers

What you must understand

• IF statements determine when a rule applies; THEN statements identify approvers and expected action.
• AND requires every condition; OR requires at least one; NOT reverses a test.
• Rule priority, status, and validity influence evaluation.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Search the transaction and choose Configure Rules.
2. 2Select the participant and add or edit a rule.
3. 3Name, activate, prioritize, date, build IF conditions, then configure THEN approvers.
4. 4Save, submit, simulate, and test positive and negative cases.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Approval Rules: IF and THEN scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Rule definition
• Simulation result
• Positive and negative routing

Common failure paths

• A condition that never matches can silently fall through to another rule.
• Advanced-mode conditions must continue to be maintained in BPM Worklist.

TechNova needs HR and Finance approvals in parallel, followed by the VP in sequence.

Concept in four layers

What you must understand

• Serial participants act one after another; parallel participants act concurrently.
• Single can use Auto Claim; FYI informs without requiring action.
• Stages and participants can each be arranged sequentially or in parallel.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Draw the required routing before configuring.
2. 2Choose stage order, participant type, and insertion in sequence or parallel.
3. 3Define completion and voting behavior, then test concurrency and rejection.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Participants and Routing scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Routing diagram
• Task creation timestamps
• Completion history

Common failure paths

• Parallel is not the same as first-responder Auto Claim.
• FYI never satisfies an approval requirement.

A promotion must stop when it reaches a manager with sufficient job level.

Concept in four layers

What you must understand

• Management hierarchy follows manager relationships, normally from the primary assignment.
• Job-level routing climbs the supervisory hierarchy until the configured threshold is met.
• Start With, Minimum Job Level, Include, number of levels, and top participant shape the chain.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Verify the worker's primary assignment and manager hierarchy.
2. 2Choose manager type and starting point.
3. 3Set levels or job-level threshold and top participant.
4. 4Test missing-manager and insufficient-level scenarios.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Management and Job-Level Routing scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Hierarchy snapshot
• Derived approver list
• Simulation trace

Common failure paths

• An incorrect or future-dated manager changes routing.
• Job-level routing still depends on the supervisor hierarchy.

A confidential transfer requires the HR Director position and a compliance duty-role population.

Concept in four layers

What you must understand

• Position hierarchy routes to position holders using the position tree.
• Named users are explicit but harder to maintain.
• Application-role routing includes users whose assigned roles inherit the selected duty role.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Choose the approver source that matches governance and maintenance needs.
2. 2Validate the hierarchy or role membership effective on the transaction date.
3. 3Test multiple position holders and changing role membership.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Position, User and Role Routing scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Position tree or role hierarchy
• Derived assignee list

Common failure paths

• Application role routing can be broader than expected because access is inherited.
• Multiple position holders can create first-responder behavior.

Priya's transfer requires her HR representative and a three-person mobility committee.

Concept in four layers

What you must understand

• Responsibility-holder routing derives representatives such as HR, Benefits, Union, or Payroll from AoR.
• Approval groups are maintained in BPM Worklist.
• Group behavior differs for serial and parallel routing.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Validate AoR scope and effective dates.
2. 2Create or maintain the approval group and membership.
3. 3Choose serial or parallel behavior and test absence of a valid representative.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Representatives and Approval Groups scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• AoR preview
• Group membership
• Claim/approval history

Common failure paths

• No matching AoR can produce a null or empty approver.
• A parallel group's task may disappear for others after one member claims it.

TechNova's routing exceeds the simplified Transaction Console rule designer.

Concept in four layers

What you must understand

• BPM Worklist supports advanced-mode rules, approval groups, notifications, reminders, expiration, and routing policy.
• Transaction Console does not display more than 25 rules and permits no more than 10 approvers in a single rule.
• Rules originally created in Advanced Mode must continue to be maintained there.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Open the correct HCM task and confirm domain.
2. 2Review stages, participants, rulesets, and advanced expressions.
3. 3Validate task-level settings and regression-test all affected paths.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured BPM Worklist and Advanced Rules scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Rule export/screenshots
• Regression matrix

Common failure paths

• Do not switch an advanced rule into the simple designer.
• BPM changes can affect every transaction instance using that task.

Approvers should be reminded after three days; unresolved tasks must expire after ten days.

Concept in four layers

What you must understand

• Due date guides timeliness but does not itself stop action.
• Expiration places the task in a final state where no further updates are allowed.
• Reminders can be initiated after assignment or before expiration.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Define business SLA and time units.
2. 2Configure reminders, due date, and expiration separately.
3. 3Test elapsed-time behavior and escalation recipients.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Reminders, Due Dates and Expiration scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Notification timestamps
• Expired/overdue status

Common failure paths

• Due date and expiration are not synonyms.
• An expired task cannot simply be approved by the original assignee.

Priya's approver is away during the promotion window.

Concept in four layers

What you must understand

• Reassign transfers the task to another user or group.
• Delegate allows another person to act on behalf of the original assignee while ownership remains associated.
• Vacation rules automate handling for a defined absence period.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Confirm policy permits delegation.
2. 2Set start/end dates and target user.
3. 3Submit a test transaction and verify ownership, action history, and post-vacation behavior.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Vacation, Delegation and Reassignment scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Original and acting user
• Action audit
• Rule dates

Common failure paths

• Delegation is not equivalent to permanent reassignment.
• Avoid circular delegation.

A manager approved by email, but the global-header notification still appears.

Concept in four layers

What you must understand

• Users receive notifications in the header, Things to Finish, Approvals work area, email, and selected mobile flows.
• Synchronize Notifications in Global Header refreshes inconsistent in-app task states.
• Notification Mode controls email and in-app delivery globally.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Verify the underlying task state before treating the issue as routing.
2. 2Run Synchronize Notifications in Global Header when interfaces are stale.
3. 3Confirm Notification Mode: All, None, Email, or In-app.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Notifications and Synchronization scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Task status
• Channel comparison
• Process log

Common failure paths

• A stale notification does not prove an unapproved transaction.
• None disables both email and in-app workflow notifications.

TechNova wants promotion notifications with its own subject, layout, and current/proposed values.

Concept in four layers

What you must understand

• Configurable notifications use BI Publisher reports for email and in-app content.
• Data Source feeds Data Model; Layout, Subtemplate, and Style Template produce the BI Report and HTML output.
• Relevant profile options choose BI Publisher instead of default notifications.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Copy the delivered report and template to a custom location.
2. 2Preserve the data model contract and edit the layout safely.
3. 3Enable the correct profile option and test email plus in-app rendering.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Configurable BI Publisher Notifications scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Rendered email
• In-app notification
• Catalog path

Common failure paths

• Editing delivered catalog content risks loss during updates.
• A template change does not change routing or approvers.

TechNova must remind workers and managers before visas expire.

Concept in four layers

What you must understand

• Event alerts use calling-client context and fixed triggering criteria.
• Resource alerts use deployed REST resources and can filter resource attributes.
• Functions, Groovy expressions, templates, schedules, and activity logging shape delivery.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Choose event or resource alert based on the trigger.
2. 2Confirm resource deployment and REST privileges.
3. 3Configure filter, recipients, templates, schedule, and activity logging.
4. 4Review Processed, Running, and Scheduled history.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Alerts Composer scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Alert history
• Recipient output
• Scheduled process

Common failure paths

• Event-alert trigger criteria cannot be modified.
• Resource access privileges are required in addition to Alerts Composer privileges.

A new promotion rule must be proved without submitting another promotion.

Concept in four layers

What you must understand

• Simulation can test pending, in-progress, or failed transactions.
• HCM_TEST_APPROVAL_RULES_ENABLED must exist, be site-updateable, and be true.
• The administrator needs ORA_PER_REVIEW_HCM_APPROVAL_TRANSACTIONS including PER_TEST_APPROVAL_RULES_PRIV.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Enable the profile option and verify security.
2. 2Select a representative transaction instance.
3. 3Run simulation and compare derived participants with the requirement.
4. 4Test boundaries, nulls, and alternate paths before release.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Simulation and Configuration Assessment scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Simulation result
• Expected-versus-actual matrix

Common failure paths

• A successful simulation does not prove notification delivery.
• One happy-path instance does not cover rule boundaries.

TechNova must retain approval evidence while keeping Transaction Console responsive.

Concept in four layers

What you must understand

• Eligible final statuses include Completed, Errored, Expired, and Withdrawn.
• Archive retains task data for audit and analysis.
• Purge permanently deletes original data after the configured retention period.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Confirm legal and audit retention requirements.
2. 2Select archive interval and purge period.
3. 3Verify archived retrieval before enabling purge.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Archive, Purge and Audit scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Archived transaction
• Retention approval
• Purge schedule

Common failure paths

• Purge is destructive and is not a performance-only decision.
• Archive and purge apply only to eligible final states.

Priya's transfer is stuck and no approver received a notification.

Concept in four layers

What you must understand

• Diagnose in order: transaction data, rule match, participant derivation, assignee security, task status, channel delivery.
• A null approver, failed rule expression, stale notification, and missing user account require different fixes.
• Evidence should distinguish root cause from symptom.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Capture transaction ID, status, subject, initiator, and effective date.
2. 2Download diagnostic log and inspect approval history.
3. 3Simulate rules; validate hierarchy, AoR, role/group membership, and user status.
4. 4Correct the smallest configuration item, recover or resubmit as appropriate, and retain evidence.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured End-to-End Troubleshooting scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Before/after diagnostic log
• Simulation
• Positive and negative retest

Common failure paths

• Do not change rules before proving the failed condition.
• Do not terminate a valid business transaction simply to clear an error.

Approved promotion rules must move from test to production without manual drift.

Concept in four layers

What you must understand

• Approval changes need inventory, dependency mapping, controlled migration, and regression testing.
• Advanced BPM artifacts, HCM approval rules, BI templates, profile options, roles, and groups may move differently.
• Future-dated or in-flight transactions need a cutover decision.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Inventory changed artifacts and dependencies.
2. 2Export or package using the supported mechanism for each artifact type.
3. 3Import in dependency order, validate access, and run route regression tests.
4. 4Document effective timing and rollback.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured Workflow Migration and Release Control scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Migration log
• Configuration comparison
• Signed test matrix

Common failure paths

• Do not assume every workflow artifact uses the same migration path.
• Test in-flight transactions separately from new submissions.

An AI assistant helps Priya prepare a transfer request but must not choose or bypass approvers.

Concept in four layers

What you must understand

• Use Request → Assist → Approve → Complete as the governing pattern.
• AI can clarify policy, gather data, draft content, and help complete follow-on steps.
• Routing, decisions, security, auditability, and compliance remain policy-controlled.

Dependency and impact map

Read left to right, then use the evidence and failure columns to explain and troubleshoot the route.

Cross-system context

Oracle navigation

Administrator sequence

1. 1Define the agent's precise phase and allowed data.
2. 2Identify the governed handoff to the HCM transaction.
3. 3Test role boundaries, unsupported requests, audit capture, and human review.

Administrator reference

These details identify where the object lives, when Oracle evaluates it, what it produces, and how to prove or correct it.

Certification lens

• Be able to assess a configured AI-Assisted Workflows and Governance scenario, not only define it.
• Predict the derived approver, task state, and administrator action.
• Distinguish the best fix from destructive or unrelated actions.

Evidence pack

• Policy test
• Access-denied test
• Approval history

Common failure paths

• An AI agent is not an alternative approval engine.
• Assistance must remain within the user's functional and data security.