32.5 FAQ

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.