Simultaneous forms editing

asked on February 20, 2018

Is there a way to have multiple users editing a single form at one time? This use case would be if User-A is completing a submission of a form. User-A saves a form as a draft. User-B needs to fill out some data on the form that was saved as a draft from User-A. If there is no way to share saved drafts is there a recommendation on how to accomplish this.

Would the following be a possible solution?

User-A submits form as a "draft"
1. This is done by submitting the form with incomplete data and having User-A assigned the same form with the missing data
A concurrent task is assigned to User-B
User-B submits data in form

Given if the same variables are in both forms would User-A's form task be updated with the data that was placed by User-B?

0 0

replied on February 21, 2018

I think your solution sounds like it would work. Have user A submit the first part of the form, then have either parallel or sequential user tasks where user B fills out their part of the form, then user A can complete their user task with all of the previous information.

I assume user A needs the information from user B to finish filling out the form? If so, you may want to have these tasks sequential so that user A's second task won't appear until user B has filled out their part. If they are in parallel, user A would immediately see the second user task but would have no indication as to when user B completed their part.

0 0

replied on February 21, 2018 • Show version history

I don't have the gateways on this chart yet. The main item is User-B's simultaneous task can be skipped. Originally the process was sequential though they would like to have User-B be able to update the form at the same time as User-A if necessary. Given this case would it be possible to terminate User-B initial simultaneous task using gateways?

0 0

replied on February 21, 2018

You could do something like this. User A and B both get a task. If user A completes the task first and set some field to User B doesn't need to review, it would throw a signal event and interrupt User B's initial task. User A could also submit their initial task saying User B DOES need to review and it would follow the top path to User B second task, leaving User B's initial task unaffected.

If it fits your use case, you could also just have one outflow from User A's task with the signal throw event. If they submit before User B's initial task, it will remove the User B task. If user B submits their task first, user A's form will be updated and the signal event won't trigger anything afterwards.

Make sure to use the appropriate gateways, definitely need one here before User B second task to make sure they wait for each other.

0 0

Question

Question

Replies

Sign in to reply to this post.