Introduction |
The details of the new relationship should be provided by the user. The details are similar to user creation screen but password set up related activities are not required while creating a relationship. |
Navigation |
|
What you can do |
The table below provides a brief description of the data that should be entered on the screen and the functions you can perform: |
Field |
Description |
Corporate ID |
Displays the corporate ID selected earlier. |
Corporate User |
Type the corporate user ID for the new relationship. |
CIF ID |
NA |
Location |
Select the primary CIF ID for the relationship from the drop-down. |
Primary Division ID |
Select the primary division from the drop-down. |
Location Access Indicator |
Indicates if the relationship has global [all] access to all the CIF IDs added to the corporate. If local, explicit linkage should be made to specific CIF IDs. |
Division Access Indicator |
Indicates if the relationship has global [all] access to all the divisions added to the corporate. If local, explicit linkage must be made to specific divisions. |
Administration ID |
Select the relationship manager ID. This group id will be used by the retail user for correspondence. |
Brand Id |
Displays the brand ID based on administrator set up. |
Menu Profile |
Select the menu profile for the retail user. The options display only retail user related menu profiles. |
Multi-Currency Transaction Allowed |
Indicates if the multi-currency transactions are allowed to the customer account. |
Workflow Rule Authority |
To enable the workflow rule authority, this flag should be checked.
|
Can Authorize Without Rules |
Indicates to initiate the transaction without any workflow rule. Note: If this check box is not selected (non-authorised user) these users will not be allowed to initiate the transaction, unless there is a valid workflow rule/role available. The function is to allow only some users to initiate the transaction if there is no workflow rule setup for a transaction, so as to limit the exposure to only trusted users (authorized users). Thus, if there is no workflow rule setup for a transaction type, only authorized users will be able to initiate such transactions. Non-authorised users will not be able to initiate the transaction without a valid workflow rule. |
Transaction Limit Scheme |
The transaction limit that is the applicable to the user can be selected from the drop-down. The periodic limit maintained in the selected transaction limit will be applicable to the user for those transactions and the channel through which the transactions are done. |
Entry/ Approval Limit Scheme |
The entry and approval limit scheme applicable to the user should be selected from the drop-down. |
Accessible Financial Transaction Types |
The financial transaction types to be accessible to the user can be selected from the list box. |
Register For Alerts |
|
Register For Alerts |
Select the value to register for alerts. |
Scheme ID |
The scheme ID for the alert to charge collection. |
Don’t Disturb Time |
The do not disturb period for alert delivery. |
Click |
To |
Submit |
Insert the new retail user ID created in the database. |
Reset |
Reset the contents of the screen. |
Back |
Return to the previous screen without saving the changes. |