Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Fixed
Priority: L3 - Default
Fix Version/s: 7.11.0, 7.11.0-alpha5
Affects Version/s: None
Component/s: engine
Labels:
- SUPPORT

A BpmnError thrown in a listener is currently treated as a runtime exception rather than treated as a process execution construct.

AT:

I can throw a BpmnError from a listener, which can be caught
start, end, take listeners
Should also trigger boundary events of the activity that is currently in execution
task and execution listener

This is the controller panel for Smart Panels app

is duplicated by

CAM-7072 I can throw BpmnError from the execution listener

Closed

is related to

CAM-10312 I cannot throw a BpmnError from listener on a joining parallel gateway

Closed

CAM-14408 BpmnError thrown from an execution listener doesn't cancel activity instance

Closed

CAM-13422 Inconsistent state in history for activities canceled through BPMN errors in end listeners

Open

CAM-10316 BpmnError is propagated from listener on modification

Closed

links to

https://github.com/camunda/camunda-bpm-platform/issues/2633

(1 links to)

Assignee:: Unassigned

Reporter:: Roman Smirnov

Votes:: 2 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 09/Feb/16 2:45 PM

Updated:: 12/Oct/22 11:15 AM

Resolved:: 14/May/19 10:22 AM