How to Avoid "Conflict in Form Submit"
Hi,
I understand that the "Conflict in Form Submit" error happens when two submissions were done in the same process instance (i.e. both users open an eForm at the same time, when a first eForm is submitted, the second one gets rejected since the data in the model was changed by what was submitted in the first eForm).
This default behavior can be problematic when two types of information need to be gathered from two different business units in parallel.
Is there a reference or an AgilePoint "design pattern" that would allow multiple eForms to be active at the same time which would allow different users to submit their info back to a common data model/schema?
-
Hi Nicholas,
Yes, the behavior you are seeing is by design. It sounds like what has happened is one of the parallel tasks is now 'out of date' as the other user has entered data into the form which is not reflected in the previous user's task. If you run into this scenario, please have the user refresh the page and retrieve the new data from the schema.
As an alternative, you can also use sequential tasks, though I understand your business case may not allow for this.
Hope this helps.
Lucas
-
We have this use case quite a bit in our multi departmental quote application. Users may have a long form which needs to stay open for a while. We also use the native 'save for later' but this did not solve the problem directly.
The design pattern we are using is a subprocess where the schema is 'copied', not 'shared'. at the end of the subprocess is a custom web service which copies the changed data to the parent process based on parent process ID.
The web service, or 'wcf' was custom built by agilepoint professional services.
Nik
サインインしてコメントを残してください。
コメント
2件のコメント