|
Introduction
|
This section outlines specific user functionality in Retail e-Banking. Menu Id, description and User acceptance required flag identifies a menu option. If required, descriptions are maintained in multiple languages.
The administrator can identify the retail or the retail menu based on the prefix (R-Retail, C-Corporate)
For Example:
|
Menu Id
|
Description
|
|
RACCT
|
Accounts functionality of retail users.
|
|
RCUST
|
Customize functionality of retail users.
|
Note:
-
For privileged dealing with user menu options, the administrator menu profile must contain one or more of these menu options: VMOT, VMOTM and VMOTV.
-
The Bank administrator can sub-classify user menu options and define them for the granular functionality. Accordingly, he can also control its availability at granular level.
-
For the application to recognize a new menu options, certain front end changes should be carried out. Also, properties in the Retail e-Banking navigation must be done.
-
The user’s access to a particular menu option can be validated during login through a third party application. This application must be capable of accepting list of menus and user information from e-banking and flagging access to users menu wise. The customVaritionHookClassName in Custom.xml and MenuOptionListFetchUtility java class must be used as part of implementation to customize this to bank’s requirement.
-
If the promotional flag for the menu option is ‘No’ and the user is not having to a specific account type, user will not be able to see the menu though it may be part of the profile. For example If credit card accounts are not linked to the user, the related menus will not be shown till user is linked to valid credit card account. If the menu is flagged as promotional, then it’ll be shown to the user irrespective of accounts available for the specific account type.
|
