-
Type:
New Feature
-
Status: Done
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: DMS Monthly Release - May 2020
-
Labels:
-
Company:All Clients/Multiple Clients
-
Epic Link:
Objective: As a HR Manager, I want to be able to control and validate the data format on forms so that users have specific formats to use so that I can standardize the data collected for use in an API.
Pre-requisite: I have a DMS activated. I am a CBAT customer.
Entry: I create a form
Exit: I can control the data format entered
Acceptance criteria:
- can control data entry types:
-
- Date
-
- soc sec #
-
- phone number
-
- text
- receive feedback when the data format is invalid
- hr manager can configure at set up
- user sees the required format (dd/mm/yyyy), XXX-XX-XXXX; X-XXX-XXX-XXXX
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length.
Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into DMS-1962.
CC – Samir
- relates to
-
DMS-2122 Add helpers on every form to sign
-
- Done
-
Field | Original Value | New Value |
---|---|---|
Epic Link | DMS-2 [ 69268 ] |
Description |
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length. |
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length. Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into |
Description |
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length. Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into |
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length. Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into CC -- [~samir] |
Assignee | Samir [ samir ] | Mohd Belal [ mohd.belal ] |
Sprint | Winter-2020 Sprint 3 [ 185 ] |
Remaining Estimate | 24h [ 86400 ] | |
Original Estimate | 24h [ 86400 ] |
Status | To Do [ 10000 ] | In Progress [ 3 ] |
Remaining Estimate | 24h [ 86400 ] | 16h [ 57600 ] |
Time Spent | 8h [ 28800 ] | |
Worklog Id | 211847 [ 211847 ] |
Description |
Add validations to DMS system fields.
For an example SSN must be numeric and fixed length. Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into CC -- [~samir] |
Objective: As a HR Manager, I want to be able to control and validate the data format on forms so that users have specific formats to use so that I can standardize the data collected for use in an API.
Pre-requisite: I have a DMS activated. I am a CBAT customer. Entry: I create a form Exit: I can control the data format entered Acceptance criteria: * can control data entry types: ** Date ** soc sec # ** phone number ** text * receive feedback when the data format is invalid * hr manager can configure at set up * user sees the required format (dd/mm/yyyy), XXX-XX-XXXX; X-XXX-XXX-XXXX Add validations to DMS system fields. For an example SSN must be numeric and fixed length. Currently DMS not having any validations for system fields. But some API implemented some validations details are updated into CC – [~samir] |
Remaining Estimate | 16h [ 57600 ] | 14h [ 50400 ] |
Time Spent | 8h [ 28800 ] | 10h [ 36000 ] |
Worklog Id | 212029 [ 212029 ] |
Remaining Estimate | 14h [ 50400 ] | 6h [ 21600 ] |
Time Spent | 10h [ 36000 ] | 18h [ 64800 ] |
Worklog Id | 212560 [ 212560 ] |
Attachment | DMS_System_Fields_Validation.docx [ 126759 ] |
Status | In Progress [ 3 ] | To Do [ 10000 ] |
Sprint | Winter-2020 Sprint 3 [ 185 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4 [ 185, 187 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4 [ 185, 187 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5 [ 185, 187, 189 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5 [ 185, 187, 189 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6 [ 185, 187, 189, 190 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6 [ 185, 187, 189, 190 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7 [ 185, 187, 189, 190, 193 ] |
Fix Version/s | Winter 2020 CBAT Integration [ 11316 ] | |
Fix Version/s | Winter 2020 Enhancements [ 11314 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7 [ 185, 187, 189, 190, 193 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8 [ 185, 187, 189, 190, 193, 197 ] |
Assignee | Mohd Belal [ mohd.belal ] | Shamooka Mohapatra [ shamooka.mohapatra ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8 [ 185, 187, 189, 190, 193, 197 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Winter-2020 Sprint 9 [ 185, 187, 189, 190, 193, 197, 198 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2 [ 185, 187, 189, 190, 193, 197, 198 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3 [ 185, 187, 189, 190, 193, 197, 198, 199 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3 [ 185, 187, 189, 190, 193, 197, 198, 199 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3, Spring-2020 - Sprint 4 [ 185, 187, 189, 190, 193, 197, 198, 199, 200 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3, Spring-2020 - Sprint 4 [ 185, 187, 189, 190, 193, 197, 198, 199, 200 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3, Spring-2020 - Sprint 4, Spring-2020 - Sprint 5 [ 185, 187, 189, 190, 193, 197, 198, 199, 200, 202 ] |
Sprint | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3, Spring-2020 - Sprint 4, Spring-2020 - Sprint 5 [ 185, 187, 189, 190, 193, 197, 198, 199, 200, 202 ] | Winter-2020 Sprint 3, Winter-2020 Sprint 4, Winter-2020 Sprint 5, Winter-2020 Sprint 6, Winter-2020 Sprint 7, Winter-2020 Sprint 8, Spring-2020 - Sprint 2, Spring-2020 - Sprint 3, Spring-2020 - Sprint 4, Spring-2020 - Sprint 5, Spring-2020 - Sprint 6 [ 185, 187, 189, 190, 193, 197, 198, 199, 200, 202, 203 ] |
Labels | DMS-CBAT |
Fix Version/s | DMS Monthly Release - May 2020 [ 11705 ] | |
Fix Version/s | Winter 2020 CBAT Integration [ 11316 ] |
Resolution | Done [ 10000 ] | |
Status | To Do [ 10000 ] | Done [ 10001 ] |
Transition | Time In Source Status | Execution Times |
---|
|
27d 16h 19m | 1 |
|
7d 7h 14m | 1 |
|
193d 16h 12m | 1 |
Hi All,
I have done the analysis on implementing the validation for system fields in DMS for PDF.
We will be adding the validation on the basis of system fields name, but in our current scenario we don't have any fixed standard defined for creating the system fields.
For example: We need to validate the date fields in the format of MM/DD/YYYY.
So we planned to check for fields with name "date" and add validation to all the fields which include date as a part of its name.
But for some dates we are using names as dob, doj instead of dateofjoin or dateofbirth.
This will cause a fail in checking the dates field and our validation won't work in that fields.
Awaiting for further discussion in this implementation.
cc - Samir
Thanks