Bug 1020875 - The unsaved changes in BPMN Designer are saved automatically even though I cancelled the transition to another view and the transition is performed as well despite of the cancellation
Summary: The unsaved changes in BPMN Designer are saved automatically even though I ca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER6
: 6.0.0
Assignee: Alexandre Porcelli
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-18 12:22 UTC by Ivo Bek
Modified: 2014-08-06 20:12 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ivo Bek 2013-10-18 12:22:17 UTC
Description of problem:

It's not possible to cancel the transition to other view when I have unsaved changes in my business process. A dialog asks me whether I want to continue because I have unsaved changes. I don't agree, so I cancel this operation The unexpected behavior is that the business process is automatically saved and I'm forced to continue to the view even though I disagreed.

How reproducible:


Steps to Reproduce:
1. Edit a business process but don't save it
2. Open Process Definitions view
3. In the dialog, saying you have unsaved changes, click on cancel button
4. See how you are transferred to the unwanted Process Definitions view
5. When you return to the process, edited before, you'll see the changes were saved and you have no option to return the changes in BPMN designer.

Comment 1 Tihomir Surdilovic 2013-11-25 19:03:22 UTC
I believe that this is not an issue with Designer but with the workbench. Similar behavior can be observed with other types of asset types such as rules. There even if you click on cancel, you are still transferred to the other view. 

Designer currently for view switching because of this issue (it never calls the @OnMayClose method of opened editors) simply saves changes so that user does not loose work. In the case of clicking on the "X" to close the actual editor, this is covered by BZ https://bugzilla.redhat.com/show_bug.cgi?id=1020353.

Comment 2 Ivo Bek 2014-01-03 11:53:55 UTC
Verified in BPMS 6.0.0.ER7


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