-
Notifications
You must be signed in to change notification settings - Fork 7
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
Cancel table not in sync with base table for UnCancel scenario #75
Comments
Fix was not deployed to staging. I have triggered deployment to staging now. Please retest. |
Pending or qwery: do we have scope of the web app as well completed : QA References : |
Fix is at ETL level and not dependent on source of data so testing from client should be sufficient. |
This was referenced Sep 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://avni.freshdesk.com/a/tickets/3163
There are scenarios where an encounter is cancelled by one user and filled in by another user. If the first user syncs, ETL creates a row in the _cancel table. When the second user syncs, the program_encounter row is overwritten, but the row in the _cancel table is not deleted.
Acceptance criteria
The text was updated successfully, but these errors were encountered: