[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: --
651: l_current_approver.orig_system_id || ' -- orig_system :' || l_current_approver.orig_system );
652: END IF;
653:
654: -- Update the Approval status with the response from the approver.
655: ame_api2.updateApprovalStatus( applicationIdIn=>applicationId,
656: transactionIdIn=>l_document_id,
657: transactionTypeIn=>l_transaction_type,
658: approverIn => l_current_approver);
659:
1712:
1713: /*
1714: g_next_approvers(l_approver_index).approval_status := ame_util.noResponseStatus;
1715: -- Update the Approval status with the response from the approver.
1716: ame_api2.updateApprovalStatus( applicationIdIn =>applicationId,
1717: transactionIdIn =>documentId,
1718: transactionTypeIn =>documentType,
1719: approverIn => g_next_approvers(l_approver_index)
1720: );
1777: l_process_out VARCHAR2(10);
1778:
1779: BEGIN
1780:
1781: ame_api2.getAllApprovers7( applicationIdIn =>applicationId,
1782: transactionIdIn =>documentId,
1783: transactionTypeIn =>documentType,
1784: approvalProcessCompleteYNOut => l_process_out,
1785: approversOut =>tmpApproverList