Red Hat Bugzilla – Bug 1261084
Opening the business process viewer in Business Central without changing anything triggers a save (commit) dialog box
Last modified: 2015-09-29 06:47:19 EDT
When a business process is opened through Business Central (KIE-Workbench) and closed it without any changes then a pop up about "confirmation message" is showed ("Business Process may contain unsaved changes. Are you sure you would like to close the editor?"). Clicking on a single task or viewing some properties is enough to trigger this message although nothing has changed.
This confirmation message should only appear if some changes have been done in the process.
6.3.x commit: https://github.com/droolsjbpm/jbpm-designer/commit/e34ee9f72cffd3c1574aebf3305b0d0756b2fb7f
Hi, Tihomir. It looks much more better, but it is still trigger a pop up with ("Business Process may contain unsaved changes. Are you sure you would like to close the editor?") message in some cases.
After opening any editor (except new Data I/O editor. ie Text Type, Editor for imports, old Data I/O editor etc.)
Steps to reproduce:
1. Create simple Business Process (Start -> End)
2. Save it (reopen if you want)
3. Open Process Properties
4. Open Imports editor and close it with Cancel button or with X button
5. Try to close Business Process
When opening a property editor a value is always set - that being whatever user chose/typed in the editor or the old value in case of a "cancel" operation.
The editor has to make sure a value is set back from it and this triggers and update on the property value.
I believe that this is acceptable behavior and should not be changed.
Opening of existing Business Process is not enough for triggering "Business Process may contain unsaved changes" for now. Also activating different element on canvas, elements in Shape library and some properties in Properties Editor not enough to trigger this message. So I mark this issue as verified.
But on the other hand it is still possible to trigger this message even if you don't make a changes so new bug 1267199 filed.