Custom Workflow Using Oracle Approvals Manager(AME)

In most of Oracle standard workflows Oracle Approvals Manager(AME) is used to define approvers. At one of my projects, there was so many workflows that approvers of workflow could be changed. So, my functional consultant advised me to use AME for defining approval groups and rules on which user to send the notification.

I developed a custom method for my workflows that look fine at last.

Here we can see firstly we set the startup values and the first step approvals at set_startup_values.  I got a variable as current_notif_done which i keep for mentioning whether next approver exists or not.

If you are careful enough you can see i make a loop at approval_ntf. Here workflow loops at approval_ntf each time next approval exists. When there is no next approver i set current_notif_done attribute1 to break the loop.

I also make two more loops which does not need approval(FYI notifications at approval and reject).

I settled this structure in two main steps.

1- Getting approvers for current step

Here i use this code for asking AME which approver is the next

ame_api2.getNextApprovers4(applicationIdIn=>your_ame_setups_application_id,
transactionTypeIn=>your_ame_setups_transaction_type,
transactionIdIn=>your_ame_setups_transaction_id,–generally itemkey
flagApproversAsNotifiedIn => ame_util.booleanFalse,
approvalProcessCompleteYNOut => l_complete,–mentions if approval is complete
nextApproversOut=>l_next_approvers);–next approval table for current step

2- Telling approval status to AME

ame_api2.updateApprovalStatus2(applicationIdIn => your_ame_setups_application_id,
transactionIdIn => your_ame_setups_transaction_id,–generally itemkey
approvalStatusIn => AME_UTIL.approvedStatus,–approved_status_or_rejected_status
approverNameIn => approver_or_rejecters_user_name,
transactionTypeIn => your_ame_setups_transaction_type);

 

There are some more keypoints about this. First of all, this generic workflow can be implemented for any needs. So, creating a new workflow time would decrease so much by the help of this generic workflow.

Two AME transaction type is needed to implement both approval and FYI at AME. Because, if it is not done like this FYI notifications could not be sent.

Advertisement