Test task has 'complete' button disabled

Flowable Application
1

Hi

I’m trying to evaluate flowable, but have not managed to create a single process that works when published. I’ve now reduced to a process with a single task and no logic at all and got the publish to work (all other attempts the publish failed, even when the validation was OK), but when I start the process in flowable-task the ‘complete’ and ‘save’ buttons on my task are disabled. Below is my bpmn. I’m using the v6.3 apps with completely standard out-of-the-box installation.

So I have 2 real questions

  1. Can anyone help with the definition below
  2. Is there any end-user (i.e. not a Java developer, a business user) style documentation for the flowable apps? Specifically, what the attributes in each of the items in the process designer are, how to use them, how they hook together in the flow. At the moment I’m going on guesswork and searches in this forum and as you can see, that isn’t working out too well.

Thanks,
Mark

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:flowable="http://flowable.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:omgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns:omgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.flowable.org/processdef">
  <message id="ReportName" name="Report Name"></message>
  <process id="test" name="test" isExecutable="true">
    <documentation>test</documentation>
    <startEvent id="start"></startEvent>
    <userTask id="task1" name="Task to do" flowable:assignee="admin" flowable:formKey="Approval">
      <extensionElements>
        <modeler:activiti-idm-assignee xmlns:modeler="http://flowable.org/modeler"><![CDATA[true]]></modeler:activiti-idm-assignee>
        <modeler:assignee-info-email xmlns:modeler="http://flowable.org/modeler"><![CDATA[admin@flowable.org]]></modeler:assignee-info-email>
        <modeler:assignee-info-firstname xmlns:modeler="http://flowable.org/modeler"><![CDATA[Test]]></modeler:assignee-info-firstname>
        <modeler:assignee-info-lastname xmlns:modeler="http://flowable.org/modeler"><![CDATA[Administrator]]></modeler:assignee-info-lastname>
        <modeler:initiator-can-complete xmlns:modeler="http://flowable.org/modeler"><![CDATA[false]]></modeler:initiator-can-complete>
      </extensionElements>
    </userTask>
    <endEvent id="end"></endEvent>
    <sequenceFlow id="flow1" sourceRef="start" targetRef="task1"></sequenceFlow>
    <sequenceFlow id="flow2" sourceRef="task1" targetRef="end"></sequenceFlow>
  </process>
  <bpmndi:BPMNDiagram id="BPMNDiagram_test">
    <bpmndi:BPMNPlane bpmnElement="test" id="BPMNPlane_test">
      <bpmndi:BPMNShape bpmnElement="start" id="BPMNShape_start">
        <omgdc:Bounds height="30.0" width="30.0" x="100.0" y="163.0"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement="task1" id="BPMNShape_task1">
        <omgdc:Bounds height="80.0" width="100.0" x="165.0" y="135.0"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement="end" id="BPMNShape_end">
        <omgdc:Bounds height="28.0" width="28.0" x="345.0" y="161.0"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement="flow1" id="BPMNEdge_flow1">
        <omgdi:waypoint x="129.94340692927761" y="177.55019845363262"></omgdi:waypoint>
        <omgdi:waypoint x="164.99999999999906" y="176.4985"></omgdi:waypoint>
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge bpmnElement="flow2" id="BPMNEdge_flow2">
        <omgdi:waypoint x="264.95000000000005" y="175.0"></omgdi:waypoint>
        <omgdi:waypoint x="345.0" y="175.0"></omgdi:waypoint>
      </bpmndi:BPMNEdge>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</definitions>
2

Hi,

I think it’s because the task has no assignee. Have you tried following the example here?

Cheers
Paul.

3

Not sure what else I’d need to create an assignee?

<userTask id="task1" name="Task to do" **flowable:assignee="admin"** flowable:formKey="Approval">