Introduction |
A new user or a disabled corporate user can be enabled by the bank administrator for accessing the application. |
Bank Administrator functions |
The bank administrators can perform the following functions:
Note:
|
Navigation |
The following is the navigation for this option:
|
What you can do |
The table below provides a brief description of the data that must be specified on the screen and the functions you can perform: |
Field |
Description |
Retail User Id |
The ID of the user who should be enabled or disabled to access the application. |
First Name |
The first name of the retail user. |
Last Name |
The last name of the retail user. |
Remarks |
Specify the remarks on the activity performed. Note: This is a mandatory alphanumeric field of maximum350 characters and is validated against banned characters list. If remarks are not provided or invalid value is provided, then the following error message will be shown – < Remarks not entered.> If the validation against the banned character list fails, then the standard error message available in Finacle is displayed. |
Apply Changes for |
|
Loggin Allowed |
Indicates if the user should be enabled or disabled for signon to the application. |
Transaction Allowed |
Indicates if the user should be enabled or disabled from conducting transactions through the application. |
Mode for authentication and authorization |
|
Login Passowrd |
If user selects the mode of authentication as login password, then the Enabled option button should be selected else the Disabled option button should be selected. |
Transaction Password |
If user selects the mode of authorization as transaction password, then the Enabled option button should be selected else the Disabled option button should be selected. |
Secure Token |
If user selects the mode of authentication and authorization as Secure Token, then the Enabled option button should be selected else the Disabled option button should be selected. |
SMS-based Mobi token |
If user selects the mode of authentication and authorization as SMS-based mobi token, then the Enabled option button should be selected else the Disabled option button should be selected. |
Device-based Mobi token |
If user selects the mode of authentication and authorization as Device-based mobi token, then the Enabled option button should be selected else the Disabled option button should be selected. |
Digital Certificate |
If user selects the mode of authentication and authorization as Digital certificate, then the Enabled option button should be selected else the Disabled option button should be selected. |
Enable/Disable History Note : The data displayed is sorted in descending order of Action Date or Time hence no pagination is required. |
|
Action Date/Time |
The date and time when the status for the Corporate was last changed. |
Action By |
The bank user ID who performed the listed action. |
Action Taken |
The action that was Performed. For example: Login Enabled Login Disabled Transaction enabled Transaction disabled Secure Token disabled Login Password Disabled and so on |
Remarks |
The remarks that were added at the time of change of status mainly the reason for changing the status. |
Click |
To |
Page Go |
View the list of records in that page. Note: If there are multiple number of pages for displaying the list of records, then the desired page number can be provided and click Go. The list of records in that page is displayed. |
|
View the list of records in the previous page. |
|
View the list of records in the next page. |
Submit |
Update the database. |
Back |
Return to the previous screen without saving the changes. |