Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update validateSSN validator to allow for all 0s,1s,...,9s as valid possible values except in cat3 scenarios. #2771

Closed
9 tasks
ADPennington opened this issue Dec 6, 2023 · 0 comments · Fixed by #2829
Assignees
Labels
dev Refined Ticket has been refined at the backlog refinement

Comments

@ADPennington
Copy link
Collaborator

ADPennington commented Dec 6, 2023

Description:

OFA's coding instructions indicate the following for STTs (this instruction is consistent for TANF, SSP, and Tribal TANF for adult and child records):

Social Security Number: Enter the nine-digit Social Security Number (SSN) for the adult. If the family affiliation code is 1 or 2, the state must provide the SSN, unless family affiliation is 2 with no SSN due to immigration status. If the family affiliation code is not 1 or 2, enter 999999999.

This is describing the conditions for a cat 3 error (inconsistency between related data elements in the same record) which has already been implemented, but based on review of error reports for recently submitted data files in prod, TDP is also flagging SSN values like this as cat 2 (out of range) errors.

all 0s,1s,...,9s are possible values for SSN. TDP should only raise cat 3 errors related to SSN.

Priority: Parity

Acceptance Criteria:
Create a list of functional outcomes that must be achieved to complete this issue

  • cat 2 error is not raised when SSN == all 0s, 1s, ..., 9s in TANF Sections 1 and 2
  • cat 2 error is not raised when SSN == all 0s, 1s, ..., 9s in SSP Sections 1 and 2
  • cat 2 error is not raised when SSN == all 0s, 1s, ..., 9s in Tribal TANF Sections 1 and 2
  • Testing Checklist has been run and all tests pass
  • README is updated, if necessary

Tasks:
Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

  • Task 1
  • Task 2
  • Task 3
  • Run Testing Checklist and confirm all tests pass

Notes:
Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this

  • Note 1
  • Note 2
  • Note 3

Supporting Documentation:
Please include any relevant log snippets/files/screen shots

  • Doc 1
  • Doc 2

Open Questions:
Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete

  • Open Question 1
  • Open Question 2
@jtimpe jtimpe added the Refined Ticket has been refined at the backlog refinement label Dec 12, 2023
@elipe17 elipe17 self-assigned this Feb 1, 2024
@elipe17 elipe17 mentioned this issue Feb 1, 2024
31 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Refined Ticket has been refined at the backlog refinement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants