Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1084022

Summary: Broken process definition cannot be deleted
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.1CC: kverlaen, mbaluch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:41:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error thrown when opening broken file none

Description Jiri Svitak 2014-04-03 12:41:47 UTC 
Created attachment 882251 [details]
error thrown when opening broken file

Broken process definition cannot be deleted.

For example check BZ1083248. The user can use designer to define a broken business process, which should not be possible. However this broken process means that:

1.) The user lost his so far defined process definition (at least in GUI).
2.) User cannot open that business process definition again. It offers new blank process of the same name, but even that does not happen. Designer hangs while loading.
3.) The process cannot be deleted, because delete button is available only in the designer.

Expected behavior:
Designer is robust enough to open broken business process definition. At least partly. Or at least blank process of the same name, which could be deleted. Designer does not hang after throwing the error describing its parse problem.

Actual behavior:
Currently it says that it will open new blank one instead, but even that does not happen. So the process definition cannot be deleted.

My env:
BPMS 6.0.1.CR2
EAP 6.1.1
Comment 1 Kris Verlaenen 2014-04-03 12:55:00 UTC 
When a process cannot be loaded, it should show an error message why, but after closing this error message, designer should load an empty process (if no process can be loaded at all), so it can at least be overridden or deleted.
Comment 2 Jeremy Lindop 2014-11-25 12:59:06 UTC 
I cannot reproduce this bug with bpms-6.1.0-DR4. I tried using the processes attached to both BZ's referenced below, and tried importing a range of invalid .bpmn2 files. In all cases the BP editor opened after some errors were displayed, so the BP could be deleted.

Some related bugs have been fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1083248
https://bugzilla.redhat.com/show_bug.cgi?id=1074694

Please re-test and see whether this bug can be reproduced - if so, please include the reproduction steps.
Comment 3 Jiri Svitak 2014-11-25 13:37:32 UTC 
According to Tihomir
https://bugzilla.redhat.com/show_bug.cgi?id=1083248#c6

the related issues with assignments editor were fixed, see also:
BZ1078088
BZ1074694

So now it should not be possible to easy create a disallowed assignment in data assignment editor of the designer, which would broke the process definition. The designer is now better able to cope with broken process definitions and now such bad definitions can be deleted or redefined.

I have tested the problematic HelloJob process from BZ1083248 and the problem had been fixed in meantime and this bugzilla was probably forgotten. Closing it as verified in BPMS 6.1.0.ER2.