Bug 1049361 - Conflict pop-up upon saving reappearing after conflict was resolved
Summary: Conflict pop-up upon saving reappearing after conflict was resolved
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: CR1
: 6.0.0
Assignee: Toni Rikkola
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks: 999950
TreeView+ depends on / blocked
 
Reported: 2014-01-07 13:19 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:19:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Zuzana Krejčová 2014-01-07 13:19:46 UTC
Description of problem:
In most asset editors, if there is a conflict upon trying to save, no matter which option you choose, trying to save again will bring up this conflict pop-up again. 
You have to close the asset editor and reopen it to really get rid of the pop-up.

Data modeler behaves well in this case and in Designer, it is simply too difficult to say with all the other problems and inconsistencies.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER7


Steps to Reproduce:
1. Users u1 and u2 both open the same asset, let's say a guided rule.
2. User u1 makes a change, saves.
3. User u2 makes a change, tries to save.
4. In the conflict error pop-up, user u2 chooses either Force save or Reopen, doesn't matter which.
5. User u2 makes another change and tries to save again.


Actual results:
Error pop-up appears again, even though no other user has made any changes.


Expected results:
Asset is saved without needing to resolve a non-existing conflict.

Comment 2 Toni Rikkola 2014-01-11 20:26:03 UTC
Even this did not have the blocker+. I was informed that it was needed for jboss‑brms‑6.0.0

Comment 4 Zuzana Krejčová 2014-01-24 12:43:04 UTC
Verified with CR1.


Note You need to log in before you can comment on or make changes to this bug.