anchor.diff:  
   Also:
   
  -* Any BPMN 2.0 process definitions in the _processes_ folder will be automatically deployed. Create a folder _processes_ and add a dummy process definition (named _one-task-process.bpmn20.xml_) to this folder.
  +* Any BPMN 2.0 process definitions in the _processes_ folder will be automatically deployed. Create a folder _processes_ and add a dummy process definition (named _one-task-process.bpmn20.xml_) to this folder. The content of this file is shown below.
   * Any CMMN 1.1 case definitions in the _cases_ folder will be automatically deployed.
   * Any DMN 1.1 dmn definitions in the _dmn_ folder will be automatically deployed.
   * Any Form definitions in the _forms_ folder will be automatically deployed.
  +
  +The XML content of the process definition is shown below. Notice that, for the moment, we are hard-coding an assignee called "kermit" to the user task. We'll come back to this later.
   
   [source,xml,linenums]
   ----
  
positive.code:     <process id="oneTaskProcess" name="The One Task Process">
          <startEvent id="theStart" />
          <sequenceFlow id="flow1" sourceRef="theStart" targetRef="theTask" />
          <userTask id="theTask" name="my task" />
          <sequenceFlow id="flow2" sourceRef="theTask" targetRef="theEnd" />
          <endEvent id="theEnd" />
      </process>
  
negative.code: ----
  <userTask id="theTask" name="my task" flowable:assignee="${person.id}"/>
  ----
  
  This replaces the hard-coded recipient, "kermit", which we had initially set.
  
  We can now start a new process instance, providing the user name in the POST body:
  
  