Direct links to fixes
APAR status
Closed as program error.
Error description
When you run a user task, for example in IBM Process Portal, you see an error. In the SystemOut.log file of the server, you find an exception like the following exception: [9/11/16 9:32:19:342 EDT] 0000012e wle E CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: com.lombardisoftware.core.TeamWorksException: Property <propertyName> in class <businessObjectTypeName> is not declared. It must be declared to be used.. com.lombardisoftware.core.TeamWorksRuntimeException: com.lombardisoftware.core.TeamWorksException: Property <propertyName> in class <businessObjectTypeName> is not declared. It must be declared to be used. at com.lombardisoftware.core.TeamWorksRuntimeException.asTeamWorksR untimeException(TeamWorksRuntimeException.java:69) at com.lombardisoftware.core.TWObject.getPropertyValue(TWObject.jav a:593) at com.lombardisoftware.core.script.js.TWObjectScriptable.get(TWObj ectScriptable.java:276) at org.mozilla.javascript.ScriptableObject.getProperty(ScriptableOb ject.java:1617) ... at com.lombardisoftware.core.script.js.JavaScriptRunner.evalScript( JavaScriptRunner.java:366) at com.lombardisoftware.component.common.workflow.ExecutionContext$ 1.call(ExecutionContext.java:593) at com.lombardisoftware.component.common.workflow.ExecutionContext$ 1.call(ExecutionContext.java:591) at com.lombardisoftware.component.common.workflow.ExecutionContext. doWithParams(ExecutionContext.java:727) at com.lombardisoftware.component.common.workflow.ExecutionContext. evalScript(ExecutionContext.java:591) at com.lombardisoftware.component.common.workflow.ExecutionContext. evalScript(ExecutionContext.java:585) at com.lombardisoftware.component.twscript.worker.ScriptWorker.doJo b(ScriptWorker.java:66) at com.lombardisoftware.component.common.workflow.ExecutionJob.doJo b(ExecutionJob.java:431) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1317) at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean. resumeTask(EJBWorkflowManagerBean.java:357) ... Caused by: com.lombardisoftware.core.TeamWorksException: Property <propertyName> in class <businessObjectTypeName> is not declared. It must be declared to be used. at com.lombardisoftware.core.TWObject.assertPropertyExists(TWObject .java:752) at com.lombardisoftware.core.TWObject.checkPropertyName(TWObject.ja va:740) at com.lombardisoftware.core.TWObject.getPropertyValue(TWObject.jav a:590) ... 96 more This error and exception occur for user tasks that belong to process instances that have been migrated to a new snapshot when the instance migration configuration deferEC property is set to true. PRODUCTS AFFECTED IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Local fix
To correct instances in your system without applying a fix, you can choose to do one of the following actions: - For each failed instance, use the move token REST API to move the token from the user task activity to itself. This action will cause a new task instance to start from the beginning. This task instance contains the correct snapshot in its runtime data. Then retry the instances by using the Process Admin Console or by using the REST API. - Create a new snapshot of your process application (this can be a snapshot without any changes). Change the instance migration configuration to specify deferEC=false. Retry the failed instances and migrate them to the new snapshot by using the Process Admin Console.
Problem summary
When a user runs a user task, its information is retrieved from the database. After its runtime data is loaded from the database, the variable data must be activated. During this operation, the server looks up the business object type definitions in the snapshot of the task. If the process instance had been migrated with the deferEC=true configuration, the runtime data is not yet set to run in this new snapshot and business object type definitions are looked up in the old snapshot. If the new snapshot contains new properties in business object type definitions, then the runtime environment doesn't know these new properties. As a result, scripts or other sources that access this new property fail.
Problem conclusion
A fix is available for IBM BPM V8.5.0.2 and will be included in IBM BPM V8.5.7 cumulative fix 2016.12 that corrects the logic when task runtime data is loaded from the database to set the runtime data to the new snapshot before activating the variable data.
Temporary fix
Comments
APAR Information
APAR number
JR57057
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-23
Closed date
2017-04-04
Last modified date
2017-04-04
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
R850 PSY
UP
R857 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021