Populate DOB on record summary from Petitioner Info #522
+93
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update to records_summary.py resolves #494
Additionally this update has a side-effect of preferring the user input DOB from petitioner info when generating record summary, even if a batch DOB exists (in case of pdf uploads). This was discussed at 11/26 meeting as desired way discrepancies between client dob and batch dob should be handled.
We also discussed updating so that petitioner info DOB populates from the batch DOB in cases where user leaves DOB blank in petitioner info user input (see update to api/viewsets.py).