[Home] [Help]
100: l_need_to_get_next_approver := FALSE;
101: BEGIN
102:
103: ame_util2.detailedApprovalStatusFlagYN := ame_util.booleanTrue;
104: ame_api2.getNextApprovers4( applicationIdIn=>applicationId,
105: transactionIdIn=>l_document_id,
106: transactionTypeIn=>l_transaction_type,
107: approvalProcessCompleteYNOut=>l_completeYNO,
108: nextApproversOut=>g_next_approvers
201: --Locks:
202: -- None.
203: --Function:
204: -- Workflow activity PL/SQL handler. This procedure is used to send the notification for the approvers.
205: -- Iterate through the list of approvers got from the API call ame_api2.getNextApprovers4.
206: -- Get the next approver name from the global variable g_next_approvers and for each retrieved approver
207: -- separate workflow process is kicked. Each process is called child process.
208: -- If there are 3 approvers, then 3 child process will be created and each of them will be notified at the same time.
209: --
650: l_current_approver.orig_system_id || ' -- orig_system :' || l_current_approver.orig_system );
651: END IF;
652:
653: -- Update the Approval status with the response from the approver.
654: ame_api2.updateApprovalStatus( applicationIdIn=>applicationId,
655: transactionIdIn=>l_document_id,
656: transactionTypeIn=>l_transaction_type,
657: approverIn => l_current_approver);
658:
1710:
1711: /*
1712: g_next_approvers(l_approver_index).approval_status := ame_util.noResponseStatus;
1713: -- Update the Approval status with the response from the approver.
1714: ame_api2.updateApprovalStatus( applicationIdIn =>applicationId,
1715: transactionIdIn =>documentId,
1716: transactionTypeIn =>documentType,
1717: approverIn => g_next_approvers(l_approver_index)
1718: );
1775: l_process_out VARCHAR2(10);
1776:
1777: BEGIN
1778:
1779: ame_api2.getAllApprovers7( applicationIdIn =>applicationId,
1780: transactionIdIn =>documentId,
1781: transactionTypeIn =>documentType,
1782: approvalProcessCompleteYNOut => l_process_out,
1783: approversOut =>tmpApproverList