Workflow-step fails when setting the outcome. And assigning fails with No UserTaskView object found

0
Mx10.18.0, WorkflowCommons 3.12.1 (most recent). Currently I have two problems in my workflow, likely related to a configuration error, but so far I have not found to solution. This first error is: in a workflow, on a UserTask's Taskpage having two "outcomes", each having a button on the page with "On click'-event "Complete user task". When clicking either of those buttons, the error occurs for lognode 'Connector':  com.mendix.webui.WebUIException: Exception while executing runtime operation at com.mendix.webui.actions.client.RuntimeOperationAction.$anonfun$apply$1(RuntimeOperationAction.scala:59) Caused by: com.mendix.systemwideinterfaces.MendixRuntimeException: Unable to find objects for guids: [18577348462967520] at com.mendix.webui.actions.client.CommitExecutor.apply(CommitExecutor.scala:31)....and the stacktrace.... and a second one for lognode 'Client': An error occurred while executing an action of MyProject.Project_Validation_Extended_Workflow.actionButton1: Internal server error Error: An error occurred while executing an action of MyProject.Project_Validation_Extended_Workflow.actionButton1: Internal server error at http://localhost:8080/mxclientsystem/mxui/mxui.js?638761518864685774:7:171586 at ye (http://localhost:8080/mxclientsystem/mxui/mxui.js?638761518864685774:21:6830) at i (http://localhost:8080/mxclientsystem/mxui/mxui.js?638761518864685774:21:6731) at k (http://localhost:8080/mxclientsystem/mxui/mxui.js?638761518864685774:5:126124) The second is whenever I click on button "Assign" (or "Unassign"), it does correctly assign (or unassign), but also throws an error: No UserTaskView object available for `Validate or reject project Test11 `. Please check if the required state change event microflows have been configured in the App Settings. Refer to the module documentation for more information.   Possibly I have incorrectly set the "state change event microflows". The 'Audit trail' works fine, and the trail is being stored. but what about the events. The 'old' way is to add OCh_WorkflowUserTask_State and OCh_Workflow_State, but adding these results in an error-message by MxStudio: wrong parameters. Page Workflow Events | Mendix Documentation tells me to configure events, like I have done. So to me it looks ok.    Does anybody have an idea what can be wrong?
asked
3 answers
0

Comes down to:

What Events do I need to connect to what microflows to make sure that my UserTasks get created correctly.

answered
0

Got rid of all the events, and solved the cause: 

Made sure that every 'Outcome' belonged to the usertask or flow in which it was used.

answered
0

Hi Tim,

The WFC module still uses the Workflow State Change Events and OCh_WorkflowUserTask_State and OCh_Workflow_State. I suggest to set them at app-level.

FYI: Mx11 and WFC will have improvements in this area's so this type if issues is less likely to occur.

answered