-
Notifications
You must be signed in to change notification settings - Fork 5
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
Enable edit to Verification Date on SMDB Data Corrections Tool #1218
Comments
Pending UI discussion with Ops. |
Sandra to schedule touch point early this week |
@robertsamm from Ops to coordinate UI testing in dev, @hullingsag to find someone from analytics to coordinate data testing. Stage testing will be coordinated between NORC UI testing and analytics data testing. |
The requirement discussion occurred on Wednesday, 3/5. Amelia and Michelle walked through the UI request for "Enable edit to Verification Date on SMDB Data Corrections Tool" (as indicated above) and #1210 , "Add new duplicate type for 'change in eligibility status' to SMDB Data Corrections Tool." Takeaway Actions: |
3/5 UI Requirements notes @sonyekere @bransteitterbr , reviewed by Ops: Ability to edit verification datetime stamp when NORC is making a change to verification status ![]() -Wording: " Set date of verification" |
@JoeArmani @rohanjay10 and @mnataraj92 - Michelle and I discussed for which circumstances should the verification date picker appear on the data corrections tool. See decision below. If we change from any verification status to 'cannot be verified' or 'verified': the verification date picker should appear. For any other verification status change, the date picker should not appear. |
Sorry I meant to tag @bransteitterbr, not Joe in comment above! |
Add to Data Corrections tool on SMDB the ability for NORC to edit the Verification Date when they make a correction to Verification Status.
If they are changing someone from 'Cannot be Verified' to 'Verified', they should also update the verification date so the communications go out correctly in time and they do not get all old messages as once.
The text was updated successfully, but these errors were encountered: