Bug 1146372 - AttachedNodeID should be displayed on the web and the eclipse BPMS designer
Summary: AttachedNodeID should be displayed on the web and the eclipse BPMS designer
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-25 06:23 UTC by ksuzumur
Modified: 2019-02-15 13:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 06:44:08 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)

Description ksuzumur 2014-09-25 06:23:16 UTC
Description of problem:
AttachedNodeID should be displayed on the web and the eclipse BPMS designer

The user can send an error event using API[1]. In the boundary catch error event case, Error type will be "Error-"+$AttachedNodeID+"-"+$ERROR_CODE.[2]. We already filed the documentation request in the Bug 1138530. Because AttachedNodeID does not appear anywhere, it's not user friendly UI. The user wants to get the Error type from the boundary event properties panel.

[1] Official Document: Please check section "⁠5.1.5.1.2. Exception handling classes"
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/User_Guide/index.html#Exception_handling_classes

[2]
https://github.com/droolsjbpm/jbpm/blob/master/jbpm-bpmn2/src/main/java/org/jbpm/bpmn2/xml/BoundaryEventHandler.java#L182


Version-Release number of selected component (if applicable):
JBPM 6.0.2
JBDS 7.1.1


Actual results:
AttachedNodeID does not appear anywhere.

Expected results:
AttachedNodeID or Error code ("Error-"+$AttachedNodeID+"-"+$ERROR_CODE) appears in the boundary event properties panel.

Additional info:
Document does not cover the situation that sending Error event to the boundary catch error event using API
https://bugzilla.redhat.com/show_bug.cgi?id=1138530

Comment 1 Kris Verlaenen 2014-09-26 12:50:08 UTC
I wouldn't recommend triggering an error event by sending a signal with the correct (internal) signal name, as this will only trigger the event, it will not trigger the exception handling itself (possibly cancelling the original node the boundary event is attached to, finding the right event in case of hierarchical structure, etc.).

Recommended way to trigger an error in code would be to use the exception scopes, finding the right handler and raising an error there, for example:

https://github.com/droolsjbpm/jbpm/blob/6.1.0.Final/jbpm-services/jbpm-executor/src/main/java/org/jbpm/executor/impl/wih/AsyncWorkItemHandlerCmdCallback.java#L91

Comment 6 Robert (Bob) Brodt 2014-10-09 18:45:34 UTC
The eclipse editor can be configured to display object IDs from the User Preferences -> BPMN2 -> Editor -> Behavior -> Show ID Attribute for BPMN2 Elements. This should allow you to see the Activity ID to which a Boundary Event is attached by selecting the Activity and looking at the "General" property tab.

This works in both the kepler (1.0.3) and luna (1.1.1) versions of the editor.

Comment 7 Toshiya Kobayashi 2014-10-17 06:42:17 UTC
Thank you, Bob! I'm sorry about not being aware of the configuration. I confirmed that ID is displayed in JBDS 7.1.1, too. So I'm closing this BZ as not a bug.

Note: I need to check the check-box "id" of target elements in "Preferences -> BPMN2 -> Editor -> Tool Profiles" in addition to "Behavior -> Show ID Attribute for BPMN2 Elements".


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