SYSTEM RULES

System rules are defined to set different parameters for each enterprise role (User Type- Retail, Corporate and AdministratorClosedAdministrator is a set of individuals that administer the applicant/Affiliate entity. For example, Accountants, Authorized Signatories for organizations, Power of Attorney for individuals.). Various parameters that can be set for each enterprise role are PartyClosedA party is any individual or business entity having a banking relationship with the bank. Mapping required, Limits check, Party Preferences check, Account Transaction Mapping and Approvals check. Enabling these parameters at enterprise role, enforces the system to check if respective maintenances are available for users associated with those enterprise roles.

E.g. if Approval check flag is enabled for ‘Corporate User’ type of enterprise role; then transactions initiated by corporate type of users will follow the approval maintenance for a party mapped to user and vice versa.

This screen allows the System Administrator to search and view existing system rules, and create new system rule.

Pre-Requisites

Workflow

Workflow

Features Supported In Application

This option allows the System Administrator to:

You are here How to reach here:

System Administrator Dashboard > Configuration > System RulesClosedRules are set of application instructions to form the logic and basis of calculation across various modules. Multiple conditions can be set in a single Rule ID. These rules are used across modules to calculate interest rates, service charges, and so on.
OR
System/ Bank Administrator Dashboard > Toggle Menu > Configuration > System Rules

Field Name

Description

Enterprise Role

Name of enterprise roles set in application.

The options can be:

  • Corporate User
  • Administrator
  • Retail User

On selecting an application role, system rules maintained if any are shown in editable form.

Party Mapping Required

Party mapping check is required for a particular enterprise role or not.

Party Preferences Check

Party preferences check is required or not.

Account Transaction Mapping

Account transaction mapping check is required or not.

Approvals Check

Approvals check is required or not.

First Time Login Steps

First time login steps to be followed or not.

Administrator can also configure the steps along with the order of the steps that need to be displayed to user.

Below field are displayed if the First Time Login Steps option is enabled.

Select

Option to decide whether that transaction is to be displayed as part of the first time login steps.

Name of Screen

Name of the transaction which is to be included as part of First Time Login Steps process.

Mandatory

Option which will decide whether the transaction is mandatory to execute as part of First Time Login Steps process.

Reorder

Order in which the transactions will get displayed when the user logs in for the first time. Administrator can click on the reorder icon and configure the order of steps in which these steps need to be displayed to user.

Account Relationship Check

Account RelationshipClosedRelationship signifies the relationship between parties and accounts whenever the relationship is mapped to account. check is required or not.

Limits Check

Limits check is required or not.

Limits - Entity Level Configuration

If limit check is required, assign a limit package.

In case of multi entity set up, limit packages needs to be mapped at each entity level.

Name of the entity

Name of entity under which limit packages are to be mapped is shown in the header.

Touch Points/ Group

Name of touch points/ groups under a specific entity to whom the limit packages are to be mapped.

Also an option is provided to map the limit package at Global level (a group created with all internal and external touch points).

Package

List of the packages which are to be mapped to a touch points/ groups. Only limit packages maintained for the selected touch point will get listed here.

To set the system rules:

  1. From the Enterprise Role list, select the appropriate option.
  2. In the Party Mapping Required field, select the appropriate option.
  3. In the Party Preferences Check field, select the appropriate option.
  4. In the Account Transaction Mapping Check field, select the appropriate option.
  5. In the Approvals Check field, select the appropriate option.
  6. In the First Time Login Steps field, select the appropriate option.
  7. To include in the First Time Login Steps process, select the checkbox(s) against the transaction and configure the steps.
  8. Slide Mandatory option to enabled /disabled the execution of transaction in the First Time Login Steps process.
  9. Slide reorder icon to set order in which transaction are executed in the First Time Login Steps process.
  10. In the Account Relationship Check field, select the appropriate option.
  11. In the Limits Check field, select the appropriate option.
  12. Click dropdownof desired entity to whom limit package to be mapped.
    Displays the list of touch points/ groups to map limit package.
  13. From the Package list, select the appropriate option.

  14. Note: Click Refresh to refresh the option.

  15. Repeat steps a to b of step 8 for all touch points/ groups.
  16. Click info to view the details of touch points group. The View Details -Touch Point Group popup window appears.

  17. Field Name

    Description

    Group Code

    Group code defined for a touch point group.

    Group Description

    Group description defined for a touch point groups.

    Touch Point Group Type

    Type of touch point i.e. whether touch point is of type internal or external.

    Touch Points

    List of the internal or external touch points.
  18. Click Submit to save system rules.
    OR
    Click Cancel to cancel the transaction.
    The success message appears.
  19. The System Rules - Review screen appears. Verify the details, and click Confirm.
    OR
    Click Back to make the changes if any.
    OR
    Click Cancel to cancel the transaction and navigate back to ‘Dashboard’.
  20. The success message of System Rules maintenance appears along with the transaction reference number. Click OK to complete the transaction.

FAQs

Closed Who can create-edit this maintenance?

System Administrator can create and edit this maintenance.

ClosedHow can I find out what checks are granted to a particular role and can I change it?

You can select a role and view the checks mapped to the role, you can also edit the type of checks.

Closed How can I group the touch points?

A separate menu option ‘Touch Point Group Maintenance’ is available to the system administrator user to maintain the groups. Groups maintained under specific entity are shown on the System Rules screen against which a consolidated limit package can be assigned.

ClosedIs it mandatory to map packages for all the touch points and groups available under each entity?

Mapping the limit packages for each touch point and for all groups available under each entity is not mandatory. But it is mandatory to map a limit package at Global level for each entity.

Home