Validations for Masters

The validations for masters are identified here.

Common instructions across all masters :

Page Heading

All page headings are in title case.

Example : "Customer Type List". Here the first letter of each word is "Capital".

When list box or combo box or drop down list box is used for adding new data(create), by default has to be blank and no item has to be selected. This helps to avoid wrong data entry.

Radio button validation

When radio button is used for adding new data(create), by default all buttons should deselected(no option is selected). This helps to avoid wrong data entry.

Edit Approve Screen

The following has to be implemented across all edit or modify pages during approval process:

1) all the changes done for every editable fields through edit option has to be shown as "old" and "new" data for each edit page. One sample has been shown in the respective wireframes.

2) The authoriser should be able to make changes to all editable fields irrespective of modifications done by user which are shown as "old" and "new". The same has been shown in the respective wireframes.

Create Approve Screen

The following has to be implemented across all create pages during approval process:

1)When create process has more than 1 step (more than 1 screen / page), the save button should be provided only at the last step (last screen / page).

2)The authoriser should be able to make changes to all fields irrespective of data entry done by user which are shown. The same has been shown in the respective wireframes.

Approval Workflow

The person with authosier role will view a list of pending tasks. The authoriser clicks on a specific task and approves or rejects.

If approve button is clicked, the new created record or updation is saved and an information message "......approved successfully." is displayed in diffrent colour for quick attention.

If reject button is clicked, the new record is not created or updation is not saved and an information message "......change or create is rejected." is displayed in different colour for quick attention.

These information messages has to be changed based on the task associated with the respective master either for create or edit.

For example : "User created successfully" or "User detail change rejected" for user master. "Identification detail change approved successfully" or "Identification creation rejected." for identification master.

Date Validations

All date data should be in DD/MM/YYYY format only.

Calendar to be provided for date entries. Year to be provided as a dropdown list for quick access.

Password Creation

Password created should be a combination of the following :

  • atleast one capital letter
  • numbers
  • special characters
  • any other characters
  • length should be minimum of 8 characters
Folio Master validation

Whenever, BRANCHID field, in FOLIOMST table is changed, the same change should be reflected in all related tables like FOLIOADDRESSMST, CONTACTMST, IDENTIFICATIONMST, FOLIOBANKMST, STATUSMST, NOMINATIONMST, NOMINEEMST.

H O User

HO User, is a bank user who can view data of all branches.

Data Duplicacy validations

  1. Validation on uniqueness of PK.

  2. Validation on uniqueness of other unique fields.

All the validations should happen on client side. As soon as data is entered and user leaves the specific field, at that point itself validation has to be done. Needs to be done for both edit and create actions. This is to avoid data duplicacy.

Image validations

Across all screens, when photo or images of documents are displayed, the photo or images should be displayed in full size on double click.

File formats

All formats of files to be allowed during uploading of documents and images.

Login Validations

Banker Login
  • Username , password and captcha have to be validated.
Agent / Superuser Login
  • Username and password has to be validated.
  • OTP has to be validated.
  • OTP has to be sent to registered mobile number and email. This has to be validated.