1. Retail Deposits User Guide
  2. Preface
  3. Basic Actions

Basic Actions

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

Table - Basic Actions

Action Description
Approve

Used to approve the initiated report.

This option is displayed when the user clicks Authorize.
Audit Used to view the maker details, checker details and report status.
Authorize

Used to authorize the report created.

A maker of the screen is not allowed to authorize the report. Only a checker can authorize a report, created by a maker.

Note:

The maker checker validation will be provided if the same maker tries to approve the single or multi-level approval tranaction.
Reject

Used to reject the report created.

A maker of the screen is not allowed to authorize the report. Only a checker can reject a report, created by a maker.
Close

Used to close a record.

This action is available only when a record is created.
Confirm Used to confirm the performed action.
Cancel Used to cancel the performed action.
Compare

Used to view the comparison through the field values of old record and the current record.

This option is displayed in the widget when the user clicks Authorize.
Collapse All

Used to hide the details in the sections.

This option is displayed when the user clicks Compare.
Expand All Used to expand and view all the details in the sections.

This option is displayed when the user clicks Compare.

Menu Item Search Used to search and navigate to the required screens.

The user can click Menu Item Search to manually search the maintenance and select the required screen.

New Used to add a new record.

When the user clicks New, the system displays a new record enabling to specify the required data.

OK Used to confirm the details in the screen.
Save Used to save the details entered or selected in the screen.
View

Used to view the report details in a particular modification stage.

This option is displayed in the widget when the user clicks Authorize.

This option is also displayed in the Tile menu.
View Difference only

Used to view a comparison through the field element values of old record and the current record, which has undergone changes.

This option is displayed when the user clicks Compare.
Unlock

Used to update the details of an existing record.

System displays an existing record in editable mode.
Auto Authorization By creating a Rule based on the life cycle code, the user can configure the branch servicing screens with auto authorization.
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.

    While creating a Rule, the user should specify the product processor as DEPOSIT and select the fact as LIFECYCLECODE.

    For Example:

    IF ( LIFECYCLECODE == TDPOMN )

    output

    Section1 LEVEL:0
  3. 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.
Multi-Level Authorization By creating a Rule based on the life cycle code, the user can configure the branch servicing screens with Multi-level authorization.
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.

    While creating a Rule, the user should specify the product processor as DEPOSIT and select the fact 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>
    .
  3. 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 provide if the same maker attempts to authorize the single or multi-level approval transaction.

Note:

The user must specify values for all the mandatory fields, and they are marked as Required.

Parent topic: Preface