Bug 1149489 - Introduce "scope" attribute for Event
Summary: Introduce "scope" attribute for Event
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER4
: 6.2.0
Assignee: Alessandro Lazarotti
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-05 12:24 UTC by Toshiya Kobayashi
Modified: 2020-03-27 20:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:12:28 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PRODMGT-1171 0 Major Pending Product Management Triage Introduce "scope" attribute for Event 2016-12-09 06:22:49 UTC

Description Toshiya Kobayashi 2014-10-05 12:24:38 UTC
Description of problem:

Introduce a custom "scope" attribute for events where you could define if a signal is to be
considered internal (only for one process instance) or external (for all process instances which are waiting) --- or possibly more scopes in the future.

Comment 4 Jozef Marko 2015-10-27 13:42:11 UTC
Verified on BPM Suite 6.2.0.ER4 and 6.3.0.Final-redhat-2 engine binaries .


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