09-28-2016 11:52 PM
12-12-2016 09:07 AM
What BPMN Modeler are you using to create this process definition?
It is certainly BPMN 2.0 compatible and produces valid BPMN, but the task "type" definition is not defined and as such is not an "executable" process.
Take the first task:
<bpmn:task id="Task_1jcrv8e" name="JIRA">
<bpmn:incoming>SequenceFlow_1fbnbrj</bpmn:incoming>
<bpmnutgoing>SequenceFlow_1go50qm</bpmnutgoing>
</bpmn:task>
While this is certainly valid, it lacks certain details required to actually create a "task" within the process engine.
See below a typical user task:
<userTask id="sid-C62D0DEB-58C9-438D-9E8F-446ADBA42E2B" name="Evaluate Other Options" activiti:assignee="$INITIATOR" activiti:formKey="8014">
<extensionElements>
<activiti:taskListener event="complete" expression="${execution.setVariable("taskAssignee", task.assignee)}"/>
</extensionElements>
</userTask>
Key missing elements are the "type" subclass (in the above example this is userTask). Also, a task must have an assignee as highlighted above.
I suggest you import your model into the Activiti editor/modeler and add the necessary attributes and then redeploy.
Hope this helps,
Greg
12-12-2016 09:07 AM
What BPMN Modeler are you using to create this process definition?
It is certainly BPMN 2.0 compatible and produces valid BPMN, but the task "type" definition is not defined and as such is not an "executable" process.
Take the first task:
<bpmn:task id="Task_1jcrv8e" name="JIRA">
<bpmn:incoming>SequenceFlow_1fbnbrj</bpmn:incoming>
<bpmnutgoing>SequenceFlow_1go50qm</bpmnutgoing>
</bpmn:task>
While this is certainly valid, it lacks certain details required to actually create a "task" within the process engine.
See below a typical user task:
<userTask id="sid-C62D0DEB-58C9-438D-9E8F-446ADBA42E2B" name="Evaluate Other Options" activiti:assignee="$INITIATOR" activiti:formKey="8014">
<extensionElements>
<activiti:taskListener event="complete" expression="${execution.setVariable("taskAssignee", task.assignee)}"/>
</extensionElements>
</userTask>
Key missing elements are the "type" subclass (in the above example this is userTask). Also, a task must have an assignee as highlighted above.
I suggest you import your model into the Activiti editor/modeler and add the necessary attributes and then redeploy.
Hope this helps,
Greg
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.