Bug 851298

Summary: JBPM-3626 Do not depend on hard coded variable name "processInstance"
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Maciej Swiderski <mswiders>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: VERIFIED --- QA Contact: Marek Baluch <mbaluch>
Severity: medium Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: kverlaen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, for intermediate conditional events to be able to a specific process instance's variables rules, the name of the variable had to be 'processInstance'. This prevented users from using any name for variables in conditional event rules. This issue has been resolved by checking the object type instead of relying on the hardcoded variable name. It is now possible to use any name for variables in conditional event rules.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maciej Swiderski 2012-08-23 17:44:00 UTC
Description of problem:
backport of https://issues.jboss.org/browse/JBPM-3626

  
Actual results:
to be able to use conditional event to reason over only variables of a selected process instance name of the variable must be exactly 'processInstance'

Expected results:
any variable name should work as long as it is of WorkflowProcessInstance type

Additional info:

Comment 1 Maciej Swiderski 2012-08-23 18:29:42 UTC
backported into 5.2.x branch

Comment 2 Jiri Svitak 2012-09-19 14:52:20 UTC
Verified in BRMS 5.3.1 ER1.

Comment 3 lcarlon 2012-10-22 05:40:46 UTC
doc text has been edited for inclusion in the release notes. Thanks for providing the text, Maciej.

- Lee