JR44894: EXECUTION CONTEXT NOT CORRECTLY SET IN SUBPROCESS
A fix is available
Closed as program error.
BPD that used to work just fine in BPM 800 cannot be started anymore in BPM 801. You cannot even start a BPD instance with the following scenario in BPM 801: ->Top level BPD (no input/output defined) ->->Nested BPD (one private var defined, this var is passed to next nested process) ->->->One more nested process with one Input var Such a process starts just fine in 800 and WLE and in 801 it would fail with an error: [11/26/12 8:27:47:157 EST] 000000f5 wle E CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: Undeclared local variable, input or output parameter textMessage found in service "Test" item "UNKNOWN" location "UNKNOWN". You must declare it in order to use it..
Define the var in question at the top BPD
Problem Description: If a task narrative is using process variables that are defined on a non-top-level scope, e.g. within a subprocess or within a linked process, task narrative resolution might fail. In this case, the process instance will not proceed. Problem Summary: For resolution of the task narrative, only the process instance top level variables are used. This interim fix will ensure that the task narrative is resolved based on the variables visible from the respective task. Problem Conclusion: After applying the interim fix, the variables that are visible on the respective task are visible for resolution of the task narrative.
Problem fixed iFix available on top V801 GA
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Translate this page: