Authorizing the Library Request

When a request is submitted, the system puts it through the authorization process where the levels of authorization required is determined and delegated for that particular request. See Authorization for more details.

Perform the following steps:

1. Login into CT Model House with the user entitled with approve/reject privilege.
   
   
2. Select Payments workspace.
   
   
3. Navigate to Activity Summary widget. This multi-app has three main tabs namely, Library Maintenance, Transactions, and Services that contain the library, transaction, and services requests respectively. These tabs in-turn consist of the following tabs:
   
   
   • Saved - This tab will show the requests that have been submitted and saved as draft. It is to be noted that the users who have the initiate privilege and access to the Activity Summary app can only see the requests that they have saved as draft or submitted.
   • Pending - This tab will show the requests that have been initiated and in queue for approval. It is to be noted that the users who have the approve/reject privilege and access to the Activity Summary app can only see the requests that are pending for approval. This tab also respects the maker-checker criteria i.e., even if a user has authorization rights, it will show the data only if the user has not modified the transaction earlier. This is achieved by tracking and maintaining the list of user IDs who have performed any action on the transaction.

   For example: Consider a request that has to be approved by multiple approvers say, John and Wills. Initially, the request will be visible for both the approvers but once John approves it, the request will be visible only for Wills for the next level of approval and vice versa. And, once Wills approves it, the request will disappear from the pending tab.

   The hierarchy based approval workflow configuration is yet to be brought in the Request Modeler whereas the developer can provide a custom JSON based on the necessity. See Authorization for more details.

   • Processed - This tab will show the requests that have been approved but which have to be manually pushed into the live database table. The users who have the approve/reject privilege and access to the Activity Summary app can only see the related requests.
   • Rejected - This tab will show the requests that have been rejected. The users who have the initiate privilege will be able to view only their requests that have been rejected by the approvers.

   
   Also, the expand/collapse button in the Activity Summary widget enables you to have a quick peek at the summary of the requests without navigating to the form through the Edit option in the widget.

4. Select the Library Maintenance tab in the Activity Summary widget.
   
   
5. Select the Pending tab.
   
   
6. Click Approve to view, approve, or reject the request.
   
   
7. In the following window, check the details within the request before approving or rejecting it:
   
   
8. Click Approve.
   
   

9. Enter the approval comments.
   

   If the Transaction Amount and Transaction Currency fields are configured while creating the request, then the Request Modeler verifies the field values and puts the request through the respective authorization workflow for approval. See Authorization for more details. 

10. Click Submit.
    
    
11. Once the request is authorized, it is sent for publishing after verifying the publish mode associated with the request. See Publishing for more details. After the request is published successfully, the following pop-up window appears with the reference number:
    
    
12. Click Ok.