User: admin@spiffworkflow.org clicked save for examples/1-basic-concepts/1-6-roles/my_vacation.bpmn
This commit is contained in:
parent
e30a5fae0f
commit
1621cb0fb6
|
@ -7,11 +7,12 @@
|
|||
<bpmn:laneSet id="LaneSet_1tmn5gq">
|
||||
<bpmn:lane id="Lane_0wgzewb">
|
||||
<bpmn:flowNodeRef>Activity_121gfc7</bpmn:flowNodeRef>
|
||||
<bpmn:flowNodeRef>Event_1pi0b2e</bpmn:flowNodeRef>
|
||||
<bpmn:flowNodeRef>StartEvent_1</bpmn:flowNodeRef>
|
||||
<bpmn:flowNodeRef>Activity_0cya923</bpmn:flowNodeRef>
|
||||
<bpmn:flowNodeRef>Event_1pi0b2e</bpmn:flowNodeRef>
|
||||
<bpmn:flowNodeRef>Activity_0tr6u2s</bpmn:flowNodeRef>
|
||||
</bpmn:lane>
|
||||
<bpmn:lane id="Lane_15s7af6" name="admin">
|
||||
<bpmn:lane id="Lane_15s7af6" name="Vacation Approver">
|
||||
<bpmn:flowNodeRef>Activity_041y60h</bpmn:flowNodeRef>
|
||||
</bpmn:lane>
|
||||
</bpmn:laneSet>
|
||||
|
@ -24,37 +25,10 @@
|
|||
<spiffworkflow:postScript />
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_08b39kn</bpmn:incoming>
|
||||
<bpmn:outgoing>Flow_0moponf</bpmn:outgoing>
|
||||
<bpmn:outgoing>Flow_12s1u1h</bpmn:outgoing>
|
||||
</bpmn:userTask>
|
||||
<bpmn:sequenceFlow id="Flow_08w5ra5" sourceRef="StartEvent_1" targetRef="Activity_0cya923" />
|
||||
<bpmn:endEvent id="Event_1pi0b2e">
|
||||
<bpmn:extensionElements>
|
||||
<spiffworkflow:instructionsForEndUser>Thanks so much for checking out Lanes - this is very simple example. You could have dozens of lanes in a single diagram, or modify the list of people allowed to complete a process in a loop. Imagine you need sign-off from 3 of 12 potential people. You could loop back to the same process 3 times, each time removing people from the list of possible candidates.
|
||||
|
||||
Like many aspects of BPMN, it is a very simple visual representation that is also very robust and easy to shape to many different circumstances.
|
||||
|
||||
### What's Next?
|
||||
|
||||
Please check back frequently, we will be adding new documentation and examples on a regular basis.
|
||||
|
||||
### Get Involved!
|
||||
Please get in touch with us! We would love to help you as you orchestrate the flow of tasks between many people and groups. There is no end to what we can accomplish if we work together. Please reach out to Dan at [dan@sartography.com](mailto:dan@sartography.com) to get started.</spiffworkflow:instructionsForEndUser>
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_0dsxo60</bpmn:incoming>
|
||||
</bpmn:endEvent>
|
||||
<bpmn:sequenceFlow id="Flow_0moponf" sourceRef="Activity_121gfc7" targetRef="Activity_041y60h" />
|
||||
<bpmn:sequenceFlow id="Flow_0dsxo60" sourceRef="Activity_041y60h" targetRef="Event_1pi0b2e" />
|
||||
<bpmn:userTask id="Activity_041y60h" name="Approve Vacation">
|
||||
<bpmn:extensionElements>
|
||||
<spiffworkflow:properties>
|
||||
<spiffworkflow:property name="formJsonSchemaFilename" value="approve-vacation-request-schema.json" />
|
||||
<spiffworkflow:property name="formUiSchemaFilename" value="approve-vacation-request-uischema.json" />
|
||||
</spiffworkflow:properties>
|
||||
<spiffworkflow:instructionsForEndUser>Please complete the form below to submit an approval request for the Vacation.</spiffworkflow:instructionsForEndUser>
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_0moponf</bpmn:incoming>
|
||||
<bpmn:outgoing>Flow_0dsxo60</bpmn:outgoing>
|
||||
</bpmn:userTask>
|
||||
<bpmn:sequenceFlow id="Flow_08b39kn" sourceRef="Activity_0cya923" targetRef="Activity_121gfc7" />
|
||||
<bpmn:startEvent id="StartEvent_1">
|
||||
<bpmn:outgoing>Flow_08w5ra5</bpmn:outgoing>
|
||||
|
@ -91,28 +65,57 @@ The example here uses this approach, it figures out who the current user is (tha
|
|||
<bpmn:incoming>Flow_08w5ra5</bpmn:incoming>
|
||||
<bpmn:outgoing>Flow_08b39kn</bpmn:outgoing>
|
||||
</bpmn:manualTask>
|
||||
<bpmn:endEvent id="Event_1pi0b2e">
|
||||
<bpmn:extensionElements>
|
||||
<spiffworkflow:instructionsForEndUser>Thanks so much for checking out Lanes - this is very simple example. You could have dozens of lanes in a single diagram, or modify the list of people allowed to complete a process in a loop. Imagine you need sign-off from 3 of 12 potential people. You could loop back to the same process 3 times, each time removing people from the list of possible candidates.
|
||||
|
||||
Like many aspects of BPMN, it is a very simple visual representation that is also very robust and easy to shape to many different circumstances.
|
||||
|
||||
### What's Next?
|
||||
|
||||
Please check back frequently, we will be adding new documentation and examples on a regular basis.
|
||||
|
||||
### Get Involved!
|
||||
Please get in touch with us! We would love to help you as you orchestrate the flow of tasks between many people and groups. There is no end to what we can accomplish if we work together. Please reach out to Dan at [dan@sartography.com](mailto:dan@sartography.com) to get started.</spiffworkflow:instructionsForEndUser>
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_0dsxo60</bpmn:incoming>
|
||||
</bpmn:endEvent>
|
||||
<bpmn:userTask id="Activity_041y60h" name="Approve Vacation">
|
||||
<bpmn:extensionElements>
|
||||
<spiffworkflow:properties>
|
||||
<spiffworkflow:property name="formJsonSchemaFilename" value="approve-vacation-request-schema.json" />
|
||||
<spiffworkflow:property name="formUiSchemaFilename" value="approve-vacation-request-uischema.json" />
|
||||
</spiffworkflow:properties>
|
||||
<spiffworkflow:instructionsForEndUser>Please complete the form below to submit an approval request for the Vacation.</spiffworkflow:instructionsForEndUser>
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_1c2wuo0</bpmn:incoming>
|
||||
<bpmn:outgoing>Flow_0dsxo60</bpmn:outgoing>
|
||||
</bpmn:userTask>
|
||||
<bpmn:sequenceFlow id="Flow_12s1u1h" sourceRef="Activity_121gfc7" targetRef="Activity_0tr6u2s" />
|
||||
<bpmn:sequenceFlow id="Flow_1c2wuo0" sourceRef="Activity_0tr6u2s" targetRef="Activity_041y60h" />
|
||||
<bpmn:scriptTask id="Activity_0tr6u2s" name="Assign current user to lane">
|
||||
<bpmn:incoming>Flow_12s1u1h</bpmn:incoming>
|
||||
<bpmn:outgoing>Flow_1c2wuo0</bpmn:outgoing>
|
||||
<bpmn:script>lane_owners =
|
||||
{ "Vacation Approver": [get_current_user().email] }
|
||||
}</bpmn:script>
|
||||
</bpmn:scriptTask>
|
||||
</bpmn:process>
|
||||
<bpmndi:BPMNDiagram id="BPMNDiagram_1">
|
||||
<bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Collaboration_0y7oun0">
|
||||
<bpmndi:BPMNShape id="Participant_0sjjdhc_di" bpmnElement="Participant_0sjjdhc" isHorizontal="true">
|
||||
<dc:Bounds x="340" y="70" width="710" height="300" />
|
||||
<dc:Bounds x="340" y="70" width="1070" height="300" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Lane_15s7af6_di" bpmnElement="Lane_15s7af6" isHorizontal="true">
|
||||
<dc:Bounds x="370" y="220" width="680" height="150" />
|
||||
<dc:Bounds x="370" y="220" width="1040" height="150" />
|
||||
<bpmndi:BPMNLabel />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Lane_0wgzewb_di" bpmnElement="Lane_0wgzewb" isHorizontal="true">
|
||||
<dc:Bounds x="370" y="70" width="680" height="150" />
|
||||
<dc:Bounds x="370" y="70" width="1040" height="150" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Activity_0axyuw7_di" bpmnElement="Activity_121gfc7">
|
||||
<dc:Bounds x="600" y="127" width="100" height="80" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Event_1pi0b2e_di" bpmnElement="Event_1pi0b2e">
|
||||
<dc:Bounds x="962" y="149" width="36" height="36" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Activity_0lxj3pw_di" bpmnElement="Activity_041y60h">
|
||||
<dc:Bounds x="760" y="270" width="100" height="80" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="_BPMNShape_StartEvent_2" bpmnElement="StartEvent_1">
|
||||
<dc:Bounds x="392" y="149" width="36" height="36" />
|
||||
</bpmndi:BPMNShape>
|
||||
|
@ -120,26 +123,40 @@ The example here uses this approach, it figures out who the current user is (tha
|
|||
<dc:Bounds x="470" y="127" width="100" height="80" />
|
||||
<bpmndi:BPMNLabel />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Event_1pi0b2e_di" bpmnElement="Event_1pi0b2e">
|
||||
<dc:Bounds x="1152" y="149" width="36" height="36" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Activity_0lxj3pw_di" bpmnElement="Activity_041y60h">
|
||||
<dc:Bounds x="950" y="270" width="100" height="80" />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNShape id="Activity_03xh6yh_di" bpmnElement="Activity_0tr6u2s">
|
||||
<dc:Bounds x="740" y="127" width="100" height="80" />
|
||||
<bpmndi:BPMNLabel />
|
||||
</bpmndi:BPMNShape>
|
||||
<bpmndi:BPMNEdge id="Flow_08w5ra5_di" bpmnElement="Flow_08w5ra5">
|
||||
<di:waypoint x="428" y="167" />
|
||||
<di:waypoint x="470" y="167" />
|
||||
</bpmndi:BPMNEdge>
|
||||
<bpmndi:BPMNEdge id="Flow_0moponf_di" bpmnElement="Flow_0moponf">
|
||||
<di:waypoint x="700" y="167" />
|
||||
<di:waypoint x="725" y="167" />
|
||||
<di:waypoint x="725" y="310" />
|
||||
<di:waypoint x="760" y="310" />
|
||||
</bpmndi:BPMNEdge>
|
||||
<bpmndi:BPMNEdge id="Flow_0dsxo60_di" bpmnElement="Flow_0dsxo60">
|
||||
<di:waypoint x="860" y="310" />
|
||||
<di:waypoint x="891" y="310" />
|
||||
<di:waypoint x="891" y="167" />
|
||||
<di:waypoint x="962" y="167" />
|
||||
<di:waypoint x="1050" y="310" />
|
||||
<di:waypoint x="1081" y="310" />
|
||||
<di:waypoint x="1081" y="167" />
|
||||
<di:waypoint x="1152" y="167" />
|
||||
</bpmndi:BPMNEdge>
|
||||
<bpmndi:BPMNEdge id="Flow_08b39kn_di" bpmnElement="Flow_08b39kn">
|
||||
<di:waypoint x="570" y="167" />
|
||||
<di:waypoint x="600" y="167" />
|
||||
</bpmndi:BPMNEdge>
|
||||
<bpmndi:BPMNEdge id="Flow_12s1u1h_di" bpmnElement="Flow_12s1u1h">
|
||||
<di:waypoint x="700" y="167" />
|
||||
<di:waypoint x="740" y="167" />
|
||||
</bpmndi:BPMNEdge>
|
||||
<bpmndi:BPMNEdge id="Flow_1c2wuo0_di" bpmnElement="Flow_1c2wuo0">
|
||||
<di:waypoint x="840" y="167" />
|
||||
<di:waypoint x="895" y="167" />
|
||||
<di:waypoint x="895" y="310" />
|
||||
<di:waypoint x="950" y="310" />
|
||||
</bpmndi:BPMNEdge>
|
||||
</bpmndi:BPMNPlane>
|
||||
</bpmndi:BPMNDiagram>
|
||||
</bpmn:definitions>
|
||||
|
|
Loading…
Reference in New Issue