This task involves adapting the existing asynchronous submission process to accommodate the synchronous submission needs of staff users. The goal is to create a new endpoint in the processor service that exposes the method to start the process of persisting data. This allows the backend service to trigger the process manually, monitor submission completion flags, and notify the end user accordingly. The system should handle long response times by allowing users to disconnect while processing continues in the background.
Type of change
[x] New feature (non-breaking change which adds functionality)
Description
This task involves adapting the existing asynchronous submission process to accommodate the synchronous submission needs of staff users. The goal is to create a new endpoint in the processor service that exposes the method to start the process of persisting data. This allows the backend service to trigger the process manually, monitor submission completion flags, and notify the end user accordingly. The system should handle long response times by allowing users to disconnect while processing continues in the background.
Type of change
How Has This Been Tested?
Checklist
Further comments
Thanks for the PR!
Deployments, as required, will be available below: Any successful deployments (not always required) will be available here
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: