Red Hat Bugzilla – Bug 983634
Problem with collaboration of two and more users on the one process definition
Last modified: 2014-08-06 16:02:15 EDT
Description of problem:
There is no update mechanism in Designer if collaborate two users on one process definition in the same time. User always rewrite the process by the his local definition. So win the last save.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. both user open process definition
2. user1: create process Start("MyStart") -> User Task("My User") -> End
3. user2: create process Start -> Task -> End
4. user1: save a process
5. user2: save a process
6. user1: delete End and add Task ("AAA") -> End
7. user2: change property "Name" of Task to "BBB"
8. user2: save a process
9. user1: save a process and close Designer
10: user1: open designer
The user1 can see a different process:
Some notification about conflict:
- merging mechanism
- update designer if a process is saved
GIT repository log says that commit "Updated asset BPMN2-ConditionalStart.bpmn2" is always done by same user (admin <null>).
This issue was partially solved by the following ticket: https://bugzilla.redhat.com/show_bug.cgi?id=999950
In order to fix this at desginer it's necessary to follow email instructions sent to bsig group.
OK.. so, can we make sure all major tools follow the steps provided ?
Internal Whiteboard: Beta Blocker → Blocker
Not critical for Beta, but need to address for GA
Fixed by https://bugzilla.redhat.com/show_bug.cgi?id=999950
blocked by another issue.
Seems the depending issue is already verified, setting back ON_QA
I verified that the dialog which resolves conflicts is shown up and options "Force Save" and "Re-open" work fine.
But there is one problem that an user does not know who changes that process. There is still user name "admin" no matter which user has saved the process.
Same conflict dialog is shown even if the process is modified by one person.
So there is no difference between single user modification and modification by two and more person.
the associated issue with admin user save by designer has already been fixed (https://github.com/droolsjbpm/jbpm-designer/commit/157325157707f2fc724ea8f29343a6184c78df00) -- BZ 1049290
This no longer has a target release of 6.0.0.
I verify that a conflict dialog contains right user for 6.0.1 ER2 BPMS. (Not just admin user).
Now conflict dialog works as was expected:
- show correct user
- options 'Force Save' and 'Re-open' works properly
Unfortunately, one problem still persist but it will be described by another bugzilla issue.