Basic Actions

The basic actions performed in the screens are as follows:

Table - Basic Actions

Actions Description
New Click New to add a new record. The system initiates a new record and enables the user to specify the required data. The fields marked with required are mandatory.
Save Click Save to save the details entered or selected in the screen.
Unlock Click Unlock to update the details of an existing record. The system displays an existing record in editable mode.
  • This button is displayed only for the records that are already created.
Authorize Click Authorize to authorize the record created. A maker of the screen is not allowed to authorize the same. Only a checker can authorize a record.
  • This button is displayed only for the already created records. For more information on the process, refer Authorization Process.
Approve Click Approve to approve the action on selected record.
  • This button is displayed once you click Authorize.
Reject Click Reject to reject the action on the selected record.
  • This button is displayed once you click Authorize.
Audit Click Audit to view the maker details, checker details of the record.
  • This button is displayed only for the records that are already created.
Close Click Close to close a record. This action is available only when a record is created.
Confirm Click Confirm to confirm the action performed.
Cancel Click Cancel to cancel the action performed.
Compare Click Compare to view the comparison of the field values of previous record and the current record.
  • This button is displayed in the widget once you click Authorize.
View Click View to view the details in a particular modification stage.
  • This button is displayed in the widget once you click Authorize.
View Difference only Click View Difference only to view a comparison through the field element values of old record and the current record, which has undergone changes.
  • This button is displayed once you click Compare.
Expand All Click Expand All to expand and view all the details in the sections.
  • This button is displayed once you click Compare.
Collapse All Click Collapse All to hide the details in the sections.
  • This button is displayed once you click Compare.
OK Click OK to confirm the details in the screen.
Auto Authorization The 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:
  1. Create the fact value as LIFECYCLECODE.
  2. Create Rule to enable Auto authorization for any servicing screen and add the expression in Rule for that screen's lifecycle code.
  3. While creating a Rule the product processor should be given as LOAN and fact should be selected as LIFECYCLECODE.
For example:
  1. IF ( LIFECYCLECODE == LNRDCH ) 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.
    • For more information, refer to the Oracle Banking Common Core User Guide to create Fact, Rule and Rule Group. Multi-Level Authorization Initiation Multi-level authorization can be configured for the branch servicing screens by creating a Rule based on life cycle code.
    • 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
Multi-Level Authorization The 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:
  1. Create the fact value as LIFECYCLECODE.
  2. Create Rule to enable Multi-level authorization for any servicing screen and add the expression in the Rule for that screen's lifecycle code.
  3. While creating a Rule the product processor should be given as LOAN and fact should be selected as LIFECYCLECODE.
For Example: IF ( LIFECYCLECODE == LNRDCH )

output

Section1 LEVEL:1~LSR_FA_LNRDCH_AUTH, LEVEL:2~LSR_FA_LNRDCH_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).
  • 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.
  • The maker checker validation will be provided if the same maker tries to authorize the single or multi-level approval tranaction.

Parent topic: Preface