mirror of
https://github.com/sartography/demo-process-models.git
synced 2025-02-24 21:28:13 +00:00
413 lines
13 KiB
XML
413 lines
13 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
||
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:spiffworkflow="http://spiffworkflow.org/bpmn/schema/1.0/core" id="Definitions_96f6665" targetNamespace="http://bpmn.io/schema/bpmn" exporter="Camunda Modeler" exporterVersion="3.0.0-dev">
|
||
<bpmn:process id="Process_1smb9b5" isExecutable="true">
|
||
<bpmn:startEvent id="StartEvent_1">
|
||
<bpmn:outgoing>Flow_0bngcu2</bpmn:outgoing>
|
||
</bpmn:startEvent>
|
||
<bpmn:sequenceFlow id="Flow_0bngcu2" sourceRef="StartEvent_1" targetRef="Activity_10fbwgl" />
|
||
<bpmn:sequenceFlow id="Flow_0ggy7w4" sourceRef="Activity_10fbwgl" targetRef="Activity_0n8y9m7" />
|
||
<bpmn:manualTask id="Activity_0n8y9m7" name="About PEP8">
|
||
<bpmn:extensionElements>
|
||
<spiffworkflow:instructionsForEndUser># Readability
|
||
The creator of Python, Guido van Rossum, said
|
||
“Code is read much more often than it’s written.” It is worth taking the time to create code that is easy to understand.
|
||
|
||
For this reason we recommend following a popular standard called [PEP8](https://realpython.com/python-pep8/)
|
||
|
||
Here are some highlights from the standard...
|
||
|
||
## Variables
|
||
|
||
### Formatting:
|
||
being consistent in the naming of your variables makes them far easier to remember. If you always use lower case and separate words with underscores, you don't have to try and remember the formatting, you just have to remember what it is called. If everyone follows this standard, then you can remember their variables easier as well ...
|
||
|
||
* my_name (GOOD)
|
||
* MyName (NO)
|
||
* myname (NO)
|
||
|
||
### Use Thoughtful names.
|
||
Avoid names that don't have meaning, or are cryptic. Try to use names that are descriptive and concise.
|
||
* first_name = "Abraham" (GOOD)
|
||
* x = "Abraham Lincoln" (AVOID)
|
||
* fn = "Abraham" (AVOID)
|
||
|
||
## Whitespace
|
||
* Use blank lines, sparingly, to show clear steps
|
||
A little white space can make your code more readable.
|
||
So can comments.
|
||
* "Sparse is better than dense" -- Zen of Python. Place spaces around operators and boolean operations most of the time. Though it can be good to break this rule when there are multiple expressions of different priority. Take the following example, where the second line is harder to read than the first.
|
||
|
||
```python
|
||
if x < 5: # GOOD
|
||
|
||
if x>5 and x<10 : # GOOD
|
||
|
||
if x > 5 and x < 10: # NOT AS GOOD
|
||
|
||
```
|
||
|
||
## Use Comments Sparingly
|
||
A few carefully chosen words can help *IF it isn't apparent already.* Good variable names and well written code come first. Then add additional comments only if the information is not already apparent in the code.
|
||
|
||
## Closing Brackets and braces
|
||
We work with dictionaries a lot. So we recommend closing your braces and brackets with the first line to make it easy to tell when the dictionary definition is complete. For example:
|
||
|
||
|
||
```python
|
||
children = {
|
||
"Robert",
|
||
"Edward"
|
||
"Tad",
|
||
"Willie"
|
||
}
|
||
```
|
||
|
||
# “Simple is better than complex.”
|
||
* Don't compare booleans, it's not necessary
|
||
```python
|
||
is_bigger = 6 > 5
|
||
|
||
if is_bigger: # GOOD
|
||
if is_bigger == True: # AVOID
|
||
```
|
||
|
||
|
||
* "is not" is easier to read:
|
||
```python
|
||
if not x is None: # AVOID
|
||
if x is not None: # GOOD
|
||
```
|
||
|
||
|
||
</spiffworkflow:instructionsForEndUser>
|
||
</bpmn:extensionElements>
|
||
<bpmn:incoming>Flow_0ggy7w4</bpmn:incoming>
|
||
<bpmn:outgoing>Flow_1s0vaon</bpmn:outgoing>
|
||
</bpmn:manualTask>
|
||
<bpmn:endEvent id="Event_16l8zdp">
|
||
<bpmn:incoming>Flow_19uhs80</bpmn:incoming>
|
||
</bpmn:endEvent>
|
||
<bpmn:sequenceFlow id="Flow_1s0vaon" sourceRef="Activity_0n8y9m7" targetRef="Activity_14uu3ah" />
|
||
<bpmn:sequenceFlow id="Flow_0x52gsc" sourceRef="Activity_14uu3ah" targetRef="Activity_1v40j82" />
|
||
<bpmn:scriptTask id="Activity_10fbwgl" name="Simple Script Task">
|
||
<bpmn:extensionElements>
|
||
<spiffworkflow:unitTests>
|
||
<spiffworkflow:unitTest id="Example Test">
|
||
<spiffworkflow:inputJson>{}</spiffworkflow:inputJson>
|
||
<spiffworkflow:expectedOutputJson>{
|
||
"age": 54,
|
||
"height": 1.93,
|
||
"children": [
|
||
"Robert",
|
||
"Edward",
|
||
"Tad",
|
||
"Willie"
|
||
],
|
||
"is_married": true,
|
||
"my_age": 55,
|
||
"cabinet": {
|
||
"Secretary of State": {
|
||
"name": "William H. Seward",
|
||
"age": 60,
|
||
"children": [
|
||
"William Jr.",
|
||
"Frederick",
|
||
"Augustus",
|
||
"Anna"
|
||
]
|
||
}
|
||
}
|
||
}</spiffworkflow:expectedOutputJson>
|
||
</spiffworkflow:unitTest>
|
||
</spiffworkflow:unitTests>
|
||
</bpmn:extensionElements>
|
||
<bpmn:incoming>Flow_0bngcu2</bpmn:incoming>
|
||
<bpmn:outgoing>Flow_0ggy7w4</bpmn:outgoing>
|
||
<bpmn:script>
|
||
# Adding function
|
||
def add_one(input):
|
||
return input + 1
|
||
|
||
# Creating Variables
|
||
age = 51 # This is an integer
|
||
height = 1.93 # This is a float or "floating point number"
|
||
children = ['Robert', 'Edward', 'Tad', 'Willie'] # This is a list
|
||
is_married = True # This is a boolean
|
||
|
||
# Updating Variables
|
||
Age = 50 # Variables are case sensitive, this is a new variable.
|
||
age = 54 # This updates the age variable.
|
||
|
||
# Referencing variables
|
||
my_age = age # my_age is now set to 54
|
||
my_age = add_one(my_age)
|
||
|
||
# Deleting variables
|
||
del(Age) # The age variable no longer exists. You will get an error if you try to use it.
|
||
|
||
|
||
# This is a dictionary, and you will use a lot of them...
|
||
cabinet = {
|
||
"Secretary of State": "William H. Seward",
|
||
"Secretary of the Treasury": "Salmon P. Chase",
|
||
"Secretary of War": "Edwin M. Stanton",
|
||
"Attorney General": "Edward Bates"
|
||
}
|
||
|
||
# Dictionaries can be deeply nested and contain any type of variable
|
||
cabinet = {
|
||
"Secretary of State": {
|
||
"name": "William H. Seward",
|
||
"age": 60,
|
||
"children": ['William Jr.', 'Frederick', 'Augustus', 'Anna']
|
||
}
|
||
}
|
||
|
||
</bpmn:script>
|
||
</bpmn:scriptTask>
|
||
<bpmn:userTask id="Activity_14uu3ah" name="Simple User Task">
|
||
<bpmn:extensionElements>
|
||
<spiffworkflow:instructionsForEndUser />
|
||
<spiffworkflow:properties>
|
||
<spiffworkflow:property name="formJsonSchemaFilename" value="simple-user-task-schema.json" />
|
||
<spiffworkflow:property name="formUiSchemaFilename" value="simple-user-task-uischema.json" />
|
||
</spiffworkflow:properties>
|
||
</bpmn:extensionElements>
|
||
<bpmn:incoming>Flow_1s0vaon</bpmn:incoming>
|
||
<bpmn:outgoing>Flow_0x52gsc</bpmn:outgoing>
|
||
</bpmn:userTask>
|
||
<bpmn:sequenceFlow id="Flow_1hy1jl1" sourceRef="Activity_1v40j82" targetRef="Activity_1ct9c0w" />
|
||
<bpmn:serviceTask id="Activity_1v40j82" name="Simple Service Tasks">
|
||
<bpmn:extensionElements>
|
||
<spiffworkflow:serviceTaskOperator id="http/GetRequest" resultVariable="api_result">
|
||
<spiffworkflow:parameters>
|
||
<spiffworkflow:parameter id="url" type="str" value=""https://dog.ceo/api/breeds/image/random"" />
|
||
<spiffworkflow:parameter id="headers" type="any" />
|
||
<spiffworkflow:parameter id="params" type="any" />
|
||
<spiffworkflow:parameter id="basic_auth_username" type="str" />
|
||
<spiffworkflow:parameter id="basic_auth_password" type="str" />
|
||
</spiffworkflow:parameters>
|
||
</spiffworkflow:serviceTaskOperator>
|
||
</bpmn:extensionElements>
|
||
<bpmn:incoming>Flow_0x52gsc</bpmn:incoming>
|
||
<bpmn:outgoing>Flow_1hy1jl1</bpmn:outgoing>
|
||
</bpmn:serviceTask>
|
||
<bpmn:sequenceFlow id="Flow_19uhs80" sourceRef="Activity_1ct9c0w" targetRef="Event_16l8zdp" />
|
||
<bpmn:manualTask id="Activity_1ct9c0w" name="Simple Manual Task">
|
||
<bpmn:extensionElements>
|
||
<spiffworkflow:instructionsForEndUser>
|
||
|
||
![Dog]({{api_result["message"]}})
|
||
|
||
# h1 Heading 8-)
|
||
## h2 Heading
|
||
### h3 Heading
|
||
#### h4 Heading
|
||
##### h5 Heading
|
||
###### h6 Heading
|
||
|
||
|
||
## Horizontal Rules
|
||
|
||
___
|
||
|
||
---
|
||
|
||
***
|
||
|
||
|
||
|
||
## Emphasis
|
||
|
||
**This is bold text**
|
||
|
||
__This is bold text__
|
||
|
||
*This is italic text*
|
||
|
||
_This is italic text_
|
||
|
||
~~Strikethrough~~
|
||
|
||
|
||
## Blockquotes
|
||
|
||
|
||
> Blockquotes can also be nested...
|
||
>> ...by using additional greater-than signs right next to each other...
|
||
> > > ...or with spaces between arrows.
|
||
|
||
|
||
## Lists
|
||
|
||
Unordered
|
||
|
||
+ Create a list by starting a line with `+`, `-`, or `*`
|
||
+ Sub-lists are made by indenting 2 spaces:
|
||
- Marker character change forces new list start:
|
||
* Ac tristique libero volutpat at
|
||
+ Facilisis in pretium nisl aliquet
|
||
- Nulla volutpat aliquam velit
|
||
+ Very easy!
|
||
|
||
Ordered
|
||
|
||
1. Lorem ipsum dolor sit amet
|
||
2. Consectetur adipiscing elit
|
||
3. Integer molestie lorem at massa
|
||
|
||
|
||
1. You can use sequential numbers...
|
||
1. ...or keep all the numbers as `1.`
|
||
|
||
Start numbering with offset:
|
||
|
||
57. foo
|
||
1. bar
|
||
|
||
|
||
## Code
|
||
|
||
Inline `code`
|
||
|
||
Indented code
|
||
|
||
// Some comments
|
||
line 1 of code
|
||
line 2 of code
|
||
line 3 of code
|
||
|
||
|
||
Block code "fences"
|
||
|
||
```
|
||
Sample text here...
|
||
```
|
||
|
||
Syntax highlighting
|
||
|
||
``` js
|
||
var foo = function (bar) {
|
||
return bar++;
|
||
};
|
||
|
||
console.log(foo(5));
|
||
```
|
||
|
||
## Tables
|
||
|
||
| Option | Description |
|
||
| ------ | ----------- |
|
||
| data | path to data files to supply the data that will be passed into templates. |
|
||
| engine | engine to be used for processing templates. Handlebars is the default. |
|
||
| ext | extension to be used for dest files. |
|
||
|
||
Right aligned columns
|
||
|
||
| Option | Description |
|
||
| ------:| -----------:|
|
||
| data | path to data files to supply the data that will be passed into templates. |
|
||
| engine | engine to be used for processing templates. Handlebars is the default. |
|
||
| ext | extension to be used for dest files. |
|
||
|
||
|
||
## Links
|
||
|
||
[link text](http://dev.nodeca.com)
|
||
|
||
[link with title](http://nodeca.github.io/pica/demo/ "title text!")
|
||
|
||
Autoconverted link https://github.com/nodeca/pica (enable linkify to see)
|
||
|
||
|
||
## Images
|
||
|
||
|
||
|
||
|
||
Like links, Images also have a footnote style syntax
|
||
|
||
![Alt text][id]
|
||
|
||
With a reference later in the document defining the URL location:
|
||
|
||
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
|
||
|
||
|
||
### [Footnotes](https://github.com/markdown-it/markdown-it-footnote)
|
||
|
||
Footnote 1 link[^first].
|
||
|
||
Footnote 2 link[^second].
|
||
|
||
Inline footnote^[Text of inline footnote] definition.
|
||
|
||
Duplicated footnote reference[^second].
|
||
|
||
[^first]: Footnote **can have markup**
|
||
|
||
and multiple paragraphs.
|
||
|
||
[^second]: Footnote text.
|
||
|
||
|
||
### This is here
|
||
Because we wanted to show that footnotes end up at the very end of the page, not immediately below the footnote refernece.</spiffworkflow:instructionsForEndUser>
|
||
</bpmn:extensionElements>
|
||
<bpmn:incoming>Flow_1hy1jl1</bpmn:incoming>
|
||
<bpmn:outgoing>Flow_19uhs80</bpmn:outgoing>
|
||
</bpmn:manualTask>
|
||
</bpmn:process>
|
||
<bpmndi:BPMNDiagram id="BPMNDiagram_1">
|
||
<bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Process_1smb9b5">
|
||
<bpmndi:BPMNShape id="_BPMNShape_StartEvent_2" bpmnElement="StartEvent_1">
|
||
<dc:Bounds x="142" y="12" width="36" height="36" />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Activity_079whp1_di" bpmnElement="Activity_10fbwgl">
|
||
<dc:Bounds x="230" y="-10" width="100" height="80" />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Event_16l8zdp_di" bpmnElement="Event_16l8zdp">
|
||
<dc:Bounds x="982" y="12" width="36" height="36" />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Activity_0ip5gqo_di" bpmnElement="Activity_0n8y9m7">
|
||
<dc:Bounds x="370" y="-10" width="100" height="80" />
|
||
<bpmndi:BPMNLabel />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Activity_02lcq5d_di" bpmnElement="Activity_14uu3ah">
|
||
<dc:Bounds x="520" y="-10" width="100" height="80" />
|
||
<bpmndi:BPMNLabel />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Activity_0dju85j_di" bpmnElement="Activity_1v40j82">
|
||
<dc:Bounds x="680" y="-10" width="100" height="80" />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNShape id="Activity_071v8hv_di" bpmnElement="Activity_1ct9c0w">
|
||
<dc:Bounds x="830" y="-10" width="100" height="80" />
|
||
</bpmndi:BPMNShape>
|
||
<bpmndi:BPMNEdge id="Flow_0bngcu2_di" bpmnElement="Flow_0bngcu2">
|
||
<di:waypoint x="178" y="30" />
|
||
<di:waypoint x="230" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
<bpmndi:BPMNEdge id="Flow_0ggy7w4_di" bpmnElement="Flow_0ggy7w4">
|
||
<di:waypoint x="330" y="30" />
|
||
<di:waypoint x="370" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
<bpmndi:BPMNEdge id="Flow_1s0vaon_di" bpmnElement="Flow_1s0vaon">
|
||
<di:waypoint x="470" y="30" />
|
||
<di:waypoint x="520" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
<bpmndi:BPMNEdge id="Flow_0x52gsc_di" bpmnElement="Flow_0x52gsc">
|
||
<di:waypoint x="620" y="30" />
|
||
<di:waypoint x="680" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
<bpmndi:BPMNEdge id="Flow_1hy1jl1_di" bpmnElement="Flow_1hy1jl1">
|
||
<di:waypoint x="780" y="30" />
|
||
<di:waypoint x="830" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
<bpmndi:BPMNEdge id="Flow_19uhs80_di" bpmnElement="Flow_19uhs80">
|
||
<di:waypoint x="930" y="30" />
|
||
<di:waypoint x="982" y="30" />
|
||
</bpmndi:BPMNEdge>
|
||
</bpmndi:BPMNPlane>
|
||
</bpmndi:BPMNDiagram>
|
||
</bpmn:definitions>
|