| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Description
Upon the successful validation of the data entered, the system must save the information to both the ASWBSQL2 legacy database and to the ASWBCentral database.
Assumptions
The actions of this user story are completed following As a system I must be able to display the appropriate fields for a new approval entry.
Requirements
As the information entered is temporary until imported, there is little need to store the data entered in ASWBCentral in a complex format. A flat table is preferred
When saving to the legacy database, in cases where the data can not be saved for any reason, a message should be displayed to the user asking them to try again.
When saving to the legacy database, the information will be inserted into the tblCRCNewApprovalHoldLocal table with the following data column associations
tblCRCNewHoldApprovalLocal Column | Data value to store | Notes |
|---|---|---|
HoldApprovalWebID | 0 | |
DateEntered | Current date and time | |
Authorizing State | Jurisdiction | Two letter state abbreviation |
FirstName | First Name | |
MiddleInitial | Middle Initial | |
LastName | Last Name | |
IDNo | SSN | Stored as debby encoded value |
BirthDate | Date of birth | |
Exam Level | Exam Level | Saved as index value |
ApprovalDate | Approval Date | |
ApprovalExpirationDate | Approval Expiration Date | |
Correction | 0 | |
DateDownloaded | NULL | |
DateImported | NULL | |
OnHold | 0 | |
PersonalNo | Internal ID No | NULL if no value was provided |
CorrectionList | NULL |
Design Considerations
Test Cases
Link to test case documentation | Result | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
| |||||||||||||||||
| 2 |
Related Items
Questions
Question | By | Answer | |
|---|---|---|---|
| 1 | |||
| 2 |