Role transaction Mapping

OBDX application has many roles for different type of users defined under different user types i.e. Retail, Corporate, and Admin. These roles are defined for internal as well as for external touch points.

Application roles mapped to Internal Touch Points (Internet, Mobile Application, SIRI, Chatbot.etc.) are used by OBDX itself, whereas Application roles mapped to External Touch Points are defined for being used by third party system. Each External role is mapped to a scope (defined in Identity Management System) and the same scopes are mapped to External Touch Points in Touch Point Maintenance screen.

For Internal Touch Points, a user can perform only those transactions which are mapped to the application role assigned to that user. Whereas for External Touch Points, third party system can only perform only those transactions (on behalf of the user), which are mapped to the application role, mapped to the scope assigned to that external touch point (third party system).

Using this option a customer can define an Application role. Application Roles are mapped to Entitlements for various Touch Points, so that System AdministratorAdministrator is a set of individuals that administer the applicant/Affiliate entity. For example, Accountants, Authorized Signatories for organizations, Power of Attorney for individuals. can decide which all transactions should be available for which touch points.

Apart from the transactions, OBDX, widgets are also available as entitlement, and can be mapped to the application roles.

System displays only those menu options widgets and dashboard which are mapped to the application role assigned to the logged in user. For e.g. If a user with application role ‘Retail’ does not have access to transactions widgets & dashboard related to Wealth Management module, then those transactions, widgets and dashboard will not be shown on the UIUser Interface to user.

Note: The users can have access only to those transactions, dashboards and widget which are mapped to the role associated to the him/her.

Pre-Requisites

• Transaction access is provided to System Administrator.
• Approval rule set up for System Administrator to perform the actions.

Workflow

Features supported in application

Using this option System Administrator can perform the following actions:

• Create Application Roles
• View Application Roles
• Edit Application Roles
• Delete Application Roles

How to reach here:

System Administration Dashboard > Authorization and Access Controls > Role Transaction Mapping
OR
System/ Bank Administration Dashboard >Toggle Menu > Authorization and Access Controls > Role Transaction Mapping

Search Application Role

Using this option, System Administrator can search application roles based on the search criteria. By default all the application roles will be displayed on this screen, Administrator can filter the list by entering the values in search criteria.

To search application role/ application roles:

• In the User Type field, select the user type.
• In the Application Role Name field, enter the name of the application role.
• Click Search.
  The search result based on search criteria displayed in Application Role Details section.
  OR
  Click Clear to reset the search parameters.
  OR
  Click Cancel to cancel the search process and to go back to dashboard.

Search Application Roles - Search Results

4. Click on the Application Role Name to view the details. Role Transaction Mapping - View screen appears.

Role Transaction Mapping - View

5. Click against the particular category to view the transaction mapping details.
6. Click to modify the transaction role mapping. The Role Transaction Mapping screen appears in editable form.
   OR
   Click Delete To delete the application role along with the transaction mapping.
   (Deletion of any role is only allowed if there are no users attached to that role)
   OR
   Click Back to navigate back to previous screen.
   OR
   Click Cancel to cancel the search process and to go back to dashboard.

Edit Application Role

Using this option System Administrator can edit or update the details of an existing role transaction mapping.

To modify role transaction mapping:

1. Repeat step 1 to 4 of Search Application Role section.
2. Click against the Map Transactions.
   Screen in editable mode appears.

Note: Application Role Name, User Type, and Touch Point Type fields cannot be edited.

3. Update the role description if required .
4. Add/ remove the user segment as per requirement.
5. Select/ deselect module names for which the transaction mapping is to be done
6. Check/uncheck the touch points for which the transaction mapping is to be done
7. Click Next to link/ delink transactions.
   OR
   Click Back to go back to previous screen.

8. Note: If the administrator deselects a module from Module name field, transaction mapping done for all the transactions under that module will get removed for that module. Similarly if the administrator unchecks and existing touch point, transaction mapping done for all modules for that touch point will get removed for that Touch Point.

8. Modify the transactions mapping for different touch points. Click against the particular category to view and update the transaction mapping.
9. Click on the next touch point tab, a pop up window appears for asking Copy data from touch point.

1. Click Yes to select the touch point from which the data has to be copied.
2. Copy transaction mapping details of touch point to another popup window .

1. From the Select list, select the touch point from the list.
2. Click Apply.
   OR
   Click No. to do the mapping operationally.
10. Modify the transactions mapping for current touch points if required.
11. Click Save to save the updates.
    OR
    Click Cancel to cancel the transaction.
    OR
    Click Back to navigate back to previous screen.
12. The screen with success message appears. Click OK to close the message screen.

Delete Application Role

Using this option System Administrator can delete an existing role transaction mapping. Deletion of any role is only allowed if there are no users attached to that role.

To delete role transaction mapping:

1. Repeat step 1 to 4 of Search Application Role section.
2. Click Delete to delete the application role along with the transaction mapping.
   The Delete Warning message appears.

3. Click Yes.
   The Role Transaction Mapping screen with the successful role deletion message appears.
   OR
   Click No to cancel the transaction.

Create Application Role

Using this option System Administrator can define an application role and map transactions to it for selected touch points.

To create an application role transaction mapping:

1. In the Role Transaction Mapping screen, click Create. The Role Transaction Mapping - Create screen appears.

2. In the Application Role Name field, enter the name of the application role.
3. In the Description field, enter the description of the application role.
4. From the User Type list, select appropriate type for which role is to be created.
5. From the Touch Point Type list, select appropriate option.
1. If you select External;
1. From the Scope Name list, select the appropriate scope to map to application role.
2. If you select Internal and User Type as Retail;
1. From the User Segment list, select the appropriate segments for which maintenance is to be done.
6. Click Map Transaction to map transaction to the role.
   The Application Role Creation screen to add transaction modules and touch points appears.
   OR
   Click Back to navigate back to previous screen.
   OR
   Click Cancel to cancel the transaction and to go back to dashboard.

7. Select appropriate modules for transactions mapping.
8. Select the check box (against the list of Touch Points to map the transactions to selected touch points.
9. Click Next. The entitlement mapping section Map Transaction appears.
   OR
   Click Clear to reset the entered details.
   OR
   Click Cancel to cancel the transaction and to go back to dashboard.
   OR
   Click Back to navigate back to previous screen.

10. Click on the desired Touch Point tab for e.g. Internet.
11. To map the transactions to the role, click against the particular module, then select the transaction type, and then transactions to be mapped.
12. Select the respective check boxes preceding to transaction to be mapped.
    OR
    Select the checkbox at header level if you want to map all the transactions below that at one instance.
13. Click on the next touch point tab, a pop up window appears for asking Copy data from touch point.
1. Click Yes to select the touch point from which the data has to be copied.
2. Copy transaction mapping details of touch point to another popup window .
3. From the Select list, select the touch point from the list.
4. Click Apply.
   
   OR
   
   Click No. to do the mapping operationally.
14. Click Save to save the changes.
    
    OR
    
    Click Cancel to cancel the transaction.
    
    OR
    
    Click Back to navigate back to the previous screen.
15. The Role Transaction Mapping - Review screen appears. Verify the details, and click Confirm.
    OR
    Click Cancel to cancel the transaction.
    OR
    Click Back to navigate back to the previous screen.
16. The screen with success message of Application Role Policy Map appears. Click OK to complete the transaction.

FAQs

Is it mandatory to map transactions to the created application role?

Yes. You will need to associate transactions for at least one module for a touch point, once an application role is created.

Do I need to mandatorily map transactions for each touch point for the new application role created?

No, it is not mandatory to map transactions for each touch point for the new role created but if the same are not defined then on initiation of transaction from that touch point, system will give an access denied message.

Why am I unable to select an action against a specific entitlement for a transaction?

This could be because that the specific action is not applicable or relevant for an entitlement i.e. approve as an action is not applicable to inquiry entitlement for a transaction.

Can I copy the same transaction mapping for an application role from one touch point to another?

Yes, you can copy the details along with an option to decide from which touch point the details need to be copied. On selection of a touch point, system will prompt to select the touch point from which the entitlements need to be copied. If you had selected ‘No’ and later wish to copy the details, then you will need to click on the touch point tab again for the system to provide that option.

Once I select the module and touch points for transaction mapping to an application, can I include additional modules and touch points?

Yes, you can click on ‘Edit’ and include additional modules and touch points for mapping.

Can I associate multiple scopes to an application role of type external and how are they associated to external touch points?

No. Only one scope can be mapped to an application role to map transactions. Once a scope is mapped to an application role, that scope cannot be mapped to another application role. Multiple scopes can be associated to an external touch point as part of touch point definition and the same scope can be mapped to different external touch points.

Home