Offline Case Functionality - Case Desyncing?
This is a pretty specific question, but I figured I'd ask.
We have a situation with our client where we have offline cases that go through multiple stages and flows before resyncing back online. As a result of this, we're trying to figure out how behavior for these cases works in edge case scenarios. For example, consider a theoeretical offline app for plumbers.
Lets say that they have to go to a job, do the work, and then report back online about what changed. Lets say that one of them takes too long, and the case gets reassigned to another worker. What would happen when the first plumber tries to resync his case online?
Would data be persisted?
Would the new data overwrite the old data?
Would the state of the case change?
Please note that for this situation, we CANNOT change the design pattern we are using and as a result, advice about other ways to implement this, or to design this app are not relevent, and will NOT be helpful.
We're only looking to answers to questions like the ones above.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Is there a way to prevent the user from submiting their updates?
In our situation, the only reason they would be updating in that manner would be if another user had gone and performed the work they were supposed to do, and it had been reassigned to someone else.
Keep up to date on this post and subscribe to comments
- Reset Button Functionality- Urgent
- Pega CMIS functionality- Version mgmt & Meta data
- Auto save functionality- looking for autosave without interfering with idle time logout feature
- PEGA 7.1.7 || Edit in Excel Functionality- Not Working
- Pega MObile Offline- Online Case and Offline Enabled Case Support in 7.2.2