Description

It is understood that a Member board may wish to change one or more attributes of an existing approval for a Candidate. ASWB wishes to have the system intelligently prevent a user from entering a “new” approval in these situations.

Assumptions

• The user has the authority to edit approvals.

Requirements

1. During the submission of an approval, as outlined in the As a system I must be able to display the appropriate fields for a new approval entry user story, the system must compare the entered information against existing records for the same jurisdiction

2. Comparisons are to be made against approvals for the SAME jurisdiction.

3. Comparisons are to occur against “imported” and “non-imported” approval records

4. Comparisons to “Imported” records are for approvals which have not expired.

5. The following field comparisons will occur

   1. SSN

   2. First Name, Last Name, DOB

   3. Last Name, DOB, Approval Date

6. If one of the comparisons above return a match to an existing approval record, the system must prompt the user that an existing approval has been found and show the details. The user must indicate if they wish to modify the existing approval OR create a new approval.

   1. If the user indicates they wish to create a new approval, the system will execute the requirements outlined in As a system, I must save a new approval record

   2. If the user indicates they wish to edit the approval, the user will be taken to the edit approval screen and the information entered will be prepopulated to assist the user in completing the edit as outlined in As a user, I must be able to edit an existing approval

Design Considerations

Test Cases

Questions

Related Items

IT Notes

In order to prevent duplicate items, the system should utilize the view vw_CheckforExisitingApproval on ASWBSQL2\ASWBSQL2 database