Direct links to fixes
APAR status
Closed as program error.
Error description
You can programmatically start an activity instance by using the ActivityInstance.start() JavaScript API. However, when you invoke that API in a task implementation and try to start an activity instance that is part of the same process instance as the task instance, the API fails and you find an exception like the following exception in the SystemOut.log file: Ä4/27/16 13:33:36:993 CESTÜ 000001c0 wle E CWLLG2229E: An exception occurred in an EJB call. Error: Execution context not set. com.lombardisoftware.core.TeamWorksException: Execution context not set. at com.lombardisoftware.bpd.runtime.engine. BPDAdhocActivityService.getModifiedBPDExecutionContext (BPDAdhocActivityService.java:2006) at com.lombardisoftware.bpd.runtime.engine. BPDAdhocActivityService.startManualAdhocActivity (BPDAdhocActivityService.java:231) at com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore. startActivityInstance(BPDEngineServicesCore.java:2354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.springframework.aop.support.AopUtils. invokeJoinpointUsingReflection(AopUtils.java:310)
Local fix
To successfully start an activity instance for the current process instance, you can invoke it directly in a Script activity in the process instead of invoking the JavaScript API from a task implementation.
Problem summary
The implementation of the JavaScript API must update the execution context of the process instance that an activity instance is to be started for. Depending on where the JavaScript API runs, the API either uses the execution context of the currently navigating process instance or must load it. In the above described case the logic did not take the correct code path and ended up without an execution context.
Problem conclusion
A fix will be included in an upcoming IBM Business Process Manager (BPM) V8.5 cumulative maintenance vehicle. To determine whether the cumulative fix is available and download it if it is, complete the following steps on Fix Central: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select Text, enter ?cumulative fix?, and click Continue.
Temporary fix
Comments
APAR Information
APAR number
JR55815
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-04-27
Closed date
2016-05-19
Last modified date
2016-05-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 August 2023