Hey @rezza72 ,
What do you mean by sequential User Tasks? Your current diagram has just running tasks in parallel under certain circumstance, which are not clear because your gateways are not labeled.
I created from your description an example: forum-registration-example.bpmn (14.2 KB)
that are two different patterns. The first pattern is used in the lane of user 2 and the second pattern in the lane of user 3. The first example has two gateways to route the process instance. Therefore the labeling and decision points are clearer to a reader.
The second example uses just one gateway. It is more complex at this point to read. Therefore, I would probably go with the first option.
From your description it remains unclear what happens if data is rejected. I just used an end event in my example but this might not be true for your usecase.
Also I am not sure if you really need two forms (user tasks) . It might be an even better user experience if the user can edit, reject and accept in the same form (task). If the user edits something they will accepted it probably. Otherwise editing does not make that much sense.
I hope that helps