Bug 808070 - Ad-hoc subprocess: the completion condition is limited only to: getActivityInstanceAttribute("numberOfActiveInstances") == 0
Summary: Ad-hoc subprocess: the completion condition is limited only to: getActivityIn...
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-29 13:32 UTC by Radovan Synek
Modified: 2020-04-27 01:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When using ad-hoc sub-processes the completion condition is limited only to: getActivityInstanceAttribute("numberOfActiveInstances") == 0, when the number of active instances differs, the ad-hoc subprocess does not end.
Clone Of:
Environment:
Last Closed:
Type: ---


Attachments (Terms of Use)

Description Radovan Synek 2012-03-29 13:32:48 UTC
Even when only the number of active instances is different (for example: getActivityInstanceAttribute("numberOfActiveInstances") == 1) and there is
one active task inside the subprocess, the ad-hoc subprocess does not end.

The completion condition works only when it is exactly as stated above in summary (so when there is no active task inside the subprocess, then the subprocess ends).

See the pull request: https://github.com/droolsjbpm/jbpm/pull/56,
commit: https://github.com/rsynek/jbpm/commit/7e1fe98179268865f70ef7c37aa299a7ca02d81c for more information.

Comment 1 lcarlon 2012-05-31 00:04:58 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When using Ad-hoc subprocesses the completion condition is limited only to: getActivityInstanceAttribute("numberOfActiveInstances") == 0, when the number of active instances differs, the ad-hoc subprocess does not end.


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