-
Notifications
You must be signed in to change notification settings - Fork 283
(feat)O3-4783: improve error handling for post-visit creation actions #2490
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
base: main
Are you sure you want to change the base?
Conversation
Size Change: +219 B (0%) Total Size: 17.3 MB ℹ️ View Unchanged
|
@donaldkibet you can remove the word failed since its just that some input was not made. Maybe something like: 'You did not input some fields like appointment, queues or billing' |
@chibongho @ibacher would some kind of roll-back mechanism if one of the linked requests fail be desirable/feasible here? |
@denniskigen That would require wrapping the start visit endpoint and all related callbacks within a single transaction, we do not support that at the moment. |
Which is why we should probably be moving things towards the EMRAPI model which allows for more "transactional" data submissions. |
Requirements
Summary
See https://openmrs.atlassian.net/browse/O3-4783
Screenshots
Kapture.2025-06-05.at.13.45.14.webm
Related Issue
Other