Customer upgrades from v2.1.x to a later version: v2.2.x, v3.x or v4.x
Process Instance is halted with a ' Mandatory parameter [xxxxx] not set' error in the logs.

An example of the error in the BPM.log, would be as follows -

20 Mar 2018 15:07:11,304 [PVM:DB Process Worker-5] [ERROR] com.tibco.bx.core.BxSystemImpl - [ERROR] - {BX_TASK_REPORTED_ERROR} - BX-800009: Task reported an error �{nodeName=`BPM-01`, hostName=`myHostName`, messageCategory=`PROCESS_INSTANCE`, componentId=`BX`, creationTime=`2018-03-20T14:07:11.304Z`, extendedMessage=`BX-600056: Mandatory parameter [xxxxx] not set.`, componentClassName=`com.tibco.bx.core.BxSystemImpl`, moduleName=`blahblah.xpdl`, principalId=`277FFC60-13D7-4714-AC48-E397222511FC`, requestReceived=`null`, threadId=`2823`, parentContextId=`null`, environmentName=ENV`, correlationId=``, managedObjectName=`Main`, stackTrace=`com.tibco.bx.core.faults.BxException: BX-600056: Mandatory parameter [xxxxx] not set.

This error was a result of JIRA BX-2548 being implemented in the product. This introduced a stricter enforcement of mandatory parameters which were not there in v2.1.x
 

After an upgrade from 2.1 to 3.x or 4.x, an error can be seen in the BPM log with regards to 'Mandatory parameter [xxx] not set' . This error did not happen with the 2.1 environment.

All OS All environments

The customer has two options:

- Set the mandatory parameter with a value to avoid the error
- The 'com.tibco.bx.engine.checkParms' JVM property can be set to "no" to override this stricter enforcement of mandatory parameters.

More can be found out about it here -
https://docs.tibco.com/pub/amx-bpm/4.2.0/doc/html/bpmhelp/GUID-A2880508-D608-4A66-B31D-775A466EE5C6.html