Bug 969557 - Unable to save a process which uses the connector object - Association (undirected)
Summary: Unable to save a process which uses the connector object - Association (undir...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-31 19:19 UTC by Amana
Modified: 2025-02-10 03:27 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot.jpg (162.53 KB, image/jpeg)
2013-05-31 19:19 UTC, Amana
no flags Details

Description Amana 2013-05-31 19:19:17 UTC
Created attachment 755351 [details]
screenshot.jpg

It is not possible to save a process which contains the 'Association (undirected)' connector object at the second time. 

Basically, you have to connect an annotation to a subprocess using the 'Association (undirected)'. The first time, you will be able to save it successfully. After saving it, the connector is still there but it is not connecting subprocess to annotation anymore, it gets displaced as you can see in screenshot.jpg attached. 

When trying to save it again, you will get the following error message on UI:

'Unable to perform user action due to error(s).
Validate your process before saving, and view server logs to see error details.'

When trying to 'validate process' a NPE is thrown in server.log and 'Invalid answer from server' in UI (see screenshot.jpg attached).

Comment 1 Amana 2013-06-03 17:08:48 UTC
What version will include this fix ?

Comment 2 Tihomir Surdilovic 2013-06-05 11:53:42 UTC
I am currently working on this. Will set status appropriately after fix asap

Comment 7 Red Hat Bugzilla 2025-02-10 03:27:51 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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