Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.13.2.GA
Affects Version/s: 7.13.1.GA
Component/s: jBPM Core
Labels:
- bamoe-verified
- support

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fix Build:
CR1
QE Test Coverage:
+
Target Release:

7.13.2.GA
Test Coverage:

+
Workaround:

Workaround Exists
Workaround Description:

Hide

Use ProcessInstance scope in the signal

Show
Use ProcessInstance scope in the signal
Git Pull Request:
https://github.com/kiegroup/jbpm/pull/2235, https://github.com/kiegroup/jbpm/pull/2236, https://github.com/kiegroup/jbpm/pull/2237
[QE] How to address?:
---
[QE] Why QE missed?:
---
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Using case management, if the process contains a signal to activate the next stage, the signal is sent twice if it is defined with "Process" scope. Using "ProcessInstance" scope only one signal is sent as expected.

clones

JBPM-10139 Signal with Process scope sent twice in Case project

Resolved

Assignee:: Martin Weiler (Inactive)

Reporter:: Martin Weiler (Inactive)

QA Contact:: Gonzalo Muñoz Fernández

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2022/11/23 9:05 PM

Updated:: 2024/02/12 9:14 AM

Resolved:: 2022/11/25 10:40 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates