Basic Actions

This topic describes about basic actions that can be performed on a screen.

Table - Basic Actions

Action	Applicable Stages	Description
Approve	Approval	The system displays a section where approval remarks if any can be input. Click OK to submit. The transaction is sent to the Host system through Oracle Banking Routing Hub. The Host system validates the transaction again and the transaction is created if all the validations are successful. If the transaction fails, the transaction is moved to Handoff retry stage, and user can view the error message. In this stage, the authorizer can retry or reject the transaction. On reject, the transaction is sent back to the maker to modify or delete it. Note: The maker checker validation will be provided if the same maker tries to approve the transaction.
Audit	Initiation, Approval, and Hand off Retry	Audit details provide the logs of users who have acted on the transaction, the transaction date, and the time for all stages that the transaction has passed through.
Auto Authorization	Initiation	Auto authorization can be configured for the branch servicing screens by creating a Rule based on life cycle code. The steps to create the Auto authorization as follows: Create the fact value as LIFECYCLECODE. Create Rule to enable Auto authorization for any servicing screen and add the expression in Rule for that screen's lifecycle code. While creating a Rule the product processor should be given as DEPOSIT and fact should be selected as LIFECYCLECODE. For Example: `IF ( LIFECYCLECODE == TDPOMN )` output `Section1 LEVEL:0` Create or modify a Rule Group with Name ApprovalRuleGroup and map the Rule(s) created in the step (2). Note: You can define one single Rule for all the screens and add the expression for the life cycle code or you can define individual Rule for each screen and map to the Rule group. Note: For more information, refer to the Oracle Banking Common Core User Guide to create Fact, Rule and Rule Group.
Back	Initiation, Approval, and Hand off Retry	In case the user missed to specify or need to modify the details in the previous segment, click to navigate to the previous segment.
Cancel	Initiation, Approval, and Hand off Retry	Cancel operation cancels the transaction input midway without saving any data. The user is alerted that the input data would be lost before confirming the cancellation.
Change Log	Approval	When the authorizer clicks on the Change Log button, the system displays the changes made to the transaction in a pop-up window. By default, the change log is set to display only modified values. The Change Log button has two options, they are, All and Updated. The All button displays both modified and non-modified fields and the Updated button displays only the modified fields. The old and new values are displayed so that the authorizer can compare or verify the values and decide on further action. Also, the new values appear is red for easy recognition.
Close	Initiation, Approval, and Hand off Retry	Users can close the transaction input screen. The system displays a warning message to the user that any unsaved data would be lost. User can either choose to ignore the message and close the screen or choose to Save and Close the transaction.
Delete	Initiation	Delete operation deletes the transaction without saving any data. The user is alerted that the input data would be lost before confirming the deletion.
Document	Initiation, Approval, and Hand off Retry	The maker of the transaction can click on Document to upload documents that are relevant to the transaction. Once uploaded, the documents are available for viewing during authorization or by the maker.
Host Error	Hand Off Retry	Hand off Retry comes into use whenever a transaction input from the mid-office system fails authorization due to Host System rejection. The authorizer of the transaction can view the reason for Host rejection and take appropriate action.
i icon	Initiation, Approval, and Hand-off Retry	To view the Customer details such as the photograph, signature, customer ID, Account Branch, and balance, the i icon is used. The i icon becomes active once the maker of the transaction inputs the account number and tabs out of the field. The i icon is useful to inquire customer information about both the debit and the credit account numbers.
Maximize	Initiation, Approval, and Hand off Retry	User can maximize the transaction input screen.
Minimize	Initiation, Approval, and Hand-off Retry	Users can minimize the transaction input screen. When the screen is minimized, it appears as to a separate tab within the same web page.
Multi-Level Authorization	Initiation	Multi-level authorization can be configured for the branch servicing screens by creating a Rule based on life cycle code. The steps to create the Multi-level authorization as follows: Create the fact value as LIFECYCLECODE. Create Rule to enable Multi-level authorization for any servicing screen and add the expression in the Rule for that screen's lifecycle code. While creating a Rule the product processor should be given as DEPOSIT and fact should be selected as LIFECYCLECODE. For Example: `IF ( LIFECYCLECODE == TDPYIN )` output `Section1 LEVEL:1~DSR_FA_TDPAYIN_AUTH, LEVEL:2~DSR_FA_TDPAYIN_AUTH` Note: If customer wants to use separate Functional Activity Code for each Level then Rule output need to be define like `LVELE:1~<FUNCTIONAL_ACTIVITY_CODE1>, LVELE:2~<FUNCTIONAL_ACTIVITY_CODE2>` . Create or modify a Rule Group with name ApprovalRuleGroup and map the rule(s) created in the step (2). Note: You can define one single rule for all the screens and add the expression for the life cycle code or you can define individual rule for each screen and map to the rule group. Note: The maker checker validation will be provided if the same maker tries to authorize the single or multi-level approval tranaction.
Overrides	Initiation, Approval, and Hand-off Retry	If override messages had appeared during initiation stage and they were accepted by the maker during submission, the Overrides button appears in the Initiation screen if the transaction is subsequently rejected by the authorizer. On the Override Details section, click Decline to go back to the transaction screen to modify or cancel it, or click Accept to complete the initiation stage and move the transaction to the approval stage.The Overrides button is displayed in the Approval and Hand-off retry stage if there were any override messages generated during initiation and accepted by the maker. When the Overrides button is clicked, the system displays the overrides accepted by the maker. After verifying the transaction and override details, the authorizer can either approve or reject the transaction. Existing Approve Transaction section is modified to display the overrides if any overrides are raised during the initiation submits.
Reject	Approval, and Hand off Retry	When an authorizer chooses to reject a transaction, the Reject icon is used. The system displays a pop-up screen to capture the Rejection remarks if any. Click OK for the transaction to be routed back to the initiation stage. Subsequently, the maker can modify or delete the transaction details.
Remarks	Initiation, Approval, and Hand-off Retry	Remarks can be used either by the maker or the authorizer of the transaction to optionally capture useful information about the transaction.
Reset	Hand off Retry	The reset button clears all the details displayed on the screen and allows input or selection of a different customer number.
Retry	Hand off Retry	The possibility of retrying a transaction arises when transaction input from the mid-office system fails authorization due to Host System rejection. Such host-rejected transactions will be present in the Hand off Retry queue in the Task Wizard. The Retry option is available only to the authorizer. Upon Retry, the transaction is sent to the host once again through Oracle Banking Routing Hub. Optionally, the authorizer can also Reject the transaction in which case it is routed back to the maker.
Save and Close	Initiation	In case a transaction has to be closed midway due to a lack of sufficient information, the maker of the transaction can choose this option. On Save and Close, the input details are saved and the transaction screen is closed. Saved transaction details will be available in My task. Users can select the transaction from My Task and proceed with the transaction or delete it.
Submit	Initiation	After submitting the initiation stage, the system validates the transaction with the host and displays the errors or overrides if any. In case of an error, you can modify and resubmit or cancel the transaction. In case of an override, you can modify and resubmit or proceed with the transaction by accepting the overrides.

Parent topic: Preface