If a process contains two or more parallel execution paths where one path modifies the business data object within a system task, the other execution paths are not updated with this value change.
At system task level, all variable modifications are localized to the task. The changes do not get propagated to the business process definition level. Hence, the parallel paths of the process accessing the same business object are not reflected with this change. This issue is in reference to the data mapping method.
Resolving the problem
This function is working as designed in IBM Business Process Manager V7.5 so an interim fix is not available. The shared objects feature is introduced in IBM Business Process Manager V8.0. However, there are some ways that you can overcome this limitation in IBM Business Process Manager Version 7.5.x.
When you modify the data within a system task, the data must be then propagated to the business process definition level where the global object can be updated. This approach enables other activities to pick up the changes as well. The system task can output the data to a Java™script component at the business process definition level and the data can be set there. Alternatively, the data can be passed to another business process definition where you can expose the updated data. You can use either method. However, to avoid this issue entirely, do not implement parallel activities that depend on the same data object.
You can upgrade to IBM Business Process Manager V8.0 where the new feature is introduced to allow the sharing of objects within subprocesses.
|Business Integration||IBM Business Process Manager Standard||Business Process Definition (BPD)||AIX, Linux, Linux zSeries, Solaris, Windows||7.5.1, 7.5|
|Business Integration||IBM Business Process Manager Express||Business Process Definition (BPD)||Linux, Linux zSeries, Windows||7.5.1, 7.5|