You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Abstract
Allow optional auto-syncing behavior for web apps
Motivation
When teams are using case sharing and performing time sensitive changes to shared case models in web apps, it can be common for them to update shared data more frequently than users are manually or automatically performing.
The lowest hanging fruit for correcting this issue would be for the system to trigger a sync immediately after a form is processed and submitted. This is safer than other times because the user doesn't have a session which could have been invalidated by changes to data.
Specification
If a flag is set, after clicking the submit data button in a web apps form the request to submit to the Formplayer engine should provide a parameter to specify that after the form is processed, a sync action should occur.
Formplayer should ideally perform the sync before processing any end of form navigation actions (in case they are invalidated).
It is acceptable for the sync to be blocking for now (since this behavior would not be used by projects where syncs are not extremely fast.
Impact on users
The form entry operation will take more time, depending on the scope and scale of the case count, which is why this behavior is recommended to be flagged. This behavior would be especially ill advised when syncs take long amounts of time to compute due to UCR's.
The text was updated successfully, but these errors were encountered:
Abstract
Allow optional auto-syncing behavior for web apps
Motivation
When teams are using case sharing and performing time sensitive changes to shared case models in web apps, it can be common for them to update shared data more frequently than users are manually or automatically performing.
The lowest hanging fruit for correcting this issue would be for the system to trigger a sync immediately after a form is processed and submitted. This is safer than other times because the user doesn't have a session which could have been invalidated by changes to data.
Specification
If a flag is set, after clicking the submit data button in a web apps form the request to submit to the Formplayer engine should provide a parameter to specify that after the form is processed, a sync action should occur.
Formplayer should ideally perform the sync before processing any end of form navigation actions (in case they are invalidated).
It is acceptable for the sync to be blocking for now (since this behavior would not be used by projects where syncs are not extremely fast.
Impact on users
The form entry operation will take more time, depending on the scope and scale of the case count, which is why this behavior is recommended to be flagged. This behavior would be especially ill advised when syncs take long amounts of time to compute due to UCR's.
The text was updated successfully, but these errors were encountered: