Hi Mark,
No its the same code that is being executed in all environments. We are calling this from webMethods Portal using Task API. In the query, we just change the parameter ‘assignedToList’ at runtime based on what we have to search. See example below.
Do we have to enable something for doing wild card search? We have checked the role functional privileges and the assignment is proper.
This is how the query (non-working) looks like in the logs at runtime.
Task Search Query [max:-1]{currentUserAccepted = null; acceptedByList contains null; #{currentTask.taskInfo.acceptedByList} contains null; assignedToList like risk; createdDate <= null; createdDate >= null; customTaskID like 10; expireDate <= null; expireDate >= null; #{currentTask.taskData.lmiRequest.body.lmiRequest.policy.policy_LmiReferenceNumber} = null; lastModifiedDate <= null; lastModifiedDate >= null; priority = null; processInstanceID = null; status = null; #{currentTask.taskData.lmiRequest.body.taskCustomInfo.customStatus} <> ; taskID = null; #{currentTask.taskData.lmiRequest.body.taskCustomInfo.customStatus} like ; taskTypeID = null}
Working query:
Task Search Query [max:-1]{currentUserAccepted = null; acceptedByList contains null; #{currentTask.taskInfo.acceptedByList} contains null; assignedToList like account; createdDate <= null; createdDate >= null; customTaskID like 10; expireDate <= null; expireDate >= null; #{currentTask.taskData.lmiRequest.body.lmiRequest.policy.policy_LmiReferenceNumber} = null; lastModifiedDate <= null; lastModifiedDate >= null; priority = null; processInstanceID = null; status = null; #{currentTask.taskData.lmiRequest.body.taskCustomInfo.customStatus} <> ; taskID = null; #{currentTask.taskData.lmiRequest.body.taskCustomInfo.customStatus} like ; taskTypeID = null}
#webMethods#webMethods-BPMS#MWS-CAF-Task-Engine