update elements and content (#318)
usama9500
GitHub
|
|
@ -5,7 +5,6 @@
|
|||
:caption: Getting Started
|
||||
learn_basics/learn_basics.md
|
||||
quick_start/quick_start.md
|
||||
learn_basics/bpmn_terminology.md
|
||||
```
|
||||
|
||||
```{toctree}
|
||||
|
|
@ -48,6 +47,7 @@ how_to/complete_a_task_on_behalf_of_another_user.md
|
|||
:maxdepth: 3
|
||||
:caption: Glossary
|
||||
glossary/glossary.md
|
||||
learn_basics/bpmn_terminology.md
|
||||
|
||||
```
|
||||
|
||||
|
|
|
|||
|
After Width: | Height: | Size: 2.6 KiB |
|
Before Width: | Height: | Size: 449 B |
|
Before Width: | Height: | Size: 561 B |
|
Before Width: | Height: | Size: 400 B |
|
After Width: | Height: | Size: 1.4 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 1.7 KiB |
|
Before Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 676 B |
|
After Width: | Height: | Size: 2.9 KiB |
|
After Width: | Height: | Size: 1.7 KiB |
|
Before Width: | Height: | Size: 2.8 KiB |
|
Before Width: | Height: | Size: 1.4 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 1.8 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 2.1 KiB |
|
After Width: | Height: | Size: 2.0 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 2.5 KiB |
|
Before Width: | Height: | Size: 4.2 KiB |
|
After Width: | Height: | Size: 2.0 KiB |
|
After Width: | Height: | Size: 1.7 KiB |
|
After Width: | Height: | Size: 1.9 KiB |
|
After Width: | Height: | Size: 1.7 KiB |
|
After Width: | Height: | Size: 2.4 KiB |
|
After Width: | Height: | Size: 2.4 KiB |
|
After Width: | Height: | Size: 1.7 KiB |
|
Before Width: | Height: | Size: 2.8 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 2.0 KiB |
|
Before Width: | Height: | Size: 1.9 KiB |
|
Before Width: | Height: | Size: 2.6 KiB |
|
Before Width: | Height: | Size: 1.8 KiB |
|
Before Width: | Height: | Size: 1.9 KiB |
|
Before Width: | Height: | Size: 2.3 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
|
|
@ -12,44 +12,45 @@ When using SpiffWorkflow, a client can create the BPMN diagram and still have th
|
|||
## BPMN Elements
|
||||
BPMN (Business Process Model and Notation) elements are the building blocks used to model business processes visually. They represent different aspects of a process, such as tasks, events, gateways, and flows, and are used to describe the flow of activities, decisions, and data within a process.
|
||||
|
||||
### Tasks
|
||||
Tasks represent activities or work that needs to be performed as part of a process. They can be manual tasks that require human intervention or automated tasks that are executed by systems or applications.
|
||||
|
||||
| **Task** | **Symbol** | **Description** |
|
||||
|---------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Service |<div style="width:70px; height:10px"></div> | Task that uses a Web service, an automated application, or other kinds of service in completing the task. |
|
||||
| Send | | Task that sends a Message to another pool. The Task is completed once the Message has been sent. |
|
||||
| Receive |<div style="width:70px; height:10px"></div>  | A Receive Task indicates that the process has to wait for a message to arrive in order to continue. The Task is completed once the| message has received. |
|
||||
| User | <div style="width:70px; height:10px"></div>  | A User Task represents that a human performer performs the Task with the use of a software application. |
|
||||
| Manual |<div style="width:70px; height:10px"></div>  | A Manual Task is a Task that is performed without the aid of any business process execution engine or any application. |
|
||||
| Business Rule |<div style="width:70px; height:10px"></div>  | Business Rule Task provides a mechanism for a process to provide input to a Business Rules Engine and then obtain the output provided by the Business Rules Engine. |
|
||||
| Script | <div style="width:70px; height:10px"></div> | A Script Task defines a script that the engine can interpret. | |
|
||||
|
||||
### Events
|
||||
Events, represented with circles, describe something that happens during the course of a process. There are three main events within business process modeling: start events, intermediate events, and end events.
|
||||
|
||||
| **Event** | **Symbol**| **Description** |
|
||||
|---------------|-----------|-----------------|
|
||||
| Start Event | | Signals the first step of a process |
|
||||
| Intermediate Event |  | Represents any event that occurs between a start and end event. |
|
||||
| End event |  | Signals the final step in a process. |
|
||||
|-----------|-----------|-----------------|
|
||||
| Start Event | | Signals the first step of a process |
|
||||
| Intermediate Event |  | Represents any event that occurs between a start and end event. |
|
||||
| End event |  | Signals the final step in a process. |
|
||||
|
||||
### Gateways
|
||||
Gateways represent decision points in a process. They determine which path the process will take based on certain conditions or rules. There are different types of gateways:
|
||||
|
||||
| **Gateway** | **Symbol**| **Description** |
|
||||
|---------------|-----------|-----------------|
|
||||
| Exclusive gateway | | Evaluates the state of the business process and, based on the condition, breaks the flow into one or more mutually exclusive paths |
|
||||
| Event-based gateway |  | An event-based gateway is similar to an exclusive gateway both involve one path in the flow. In the case of an event-based gateway, however, you evaluate which event has occurred, not which condition has been met. |
|
||||
| Parallel gateway |  | Parallel gateways are used to represent two tasks in a business flow. A parallel gateway is used to visualize the concurrent execution of activities. |
|
||||
| Inclusive gateway |  | An inclusive gateway breaks the process flow into one or more flows. |
|
||||
| Complex gateway |  | complex gateways are only used for the most complex flows in the business process. They use words in place of symbols and, therefore, require more descriptive text. |
|
||||
| |
|
||||
| Exclusive gateway | | Evaluates the state of the business process and, based on the condition, breaks the flow into one or more mutually exclusive paths |
|
||||
| Event-based gateway |  | An event-based gateway is similar to an exclusive gateway both involve one path in the flow. In the case of an event-based gateway, however, you evaluate which event has occurred, not which condition has been met. |
|
||||
| Inclusive gateway |  | An inclusive gateway breaks the process flow into one or more flows. |
|
||||
| Complex gateway |  | Complex gateways are only used for the most complex flows in the business process. They use words in place of symbols and, therefore, require more descriptive text. |
|
||||
|
||||
### Flows
|
||||
Flows represent the sequence or direction of activities in a process. There are different types of flows in BPMN, including sequence flows, message flows, and association flows. Sequence flows indicate the order in which tasks are performed, message flows represent the exchange of messages between participants, and association flows connect data objects or artifacts to activities.
|
||||
### Tasks
|
||||
Tasks represent activities or work that needs to be performed as part of a process. They can be manual tasks that require human intervention or automated tasks that are executed by systems or applications.
|
||||
|
||||
| **Task** | **Symbol** | **Description** |
|
||||
|---------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Service | | Task that uses a Web service, an automated application, or other kinds of service in completing the task. |
|
||||
| Send | | Task that sends a Message to another pool. The Task is completed once the Message has been sent. |
|
||||
| Receive |  | A Receive Task indicates that the process has to wait for a message to arrive in order to continue. The Task is completed once the| message has received. |
|
||||
| User |  | A User Task represents that a human performer performs the Task with the use of a software application. |
|
||||
| Manual |  | A Manual Task is a Task that is performed without the aid of any business process execution engine or any application. |
|
||||
| Business Rule || Business Rule Task provides a mechanism for a process to provide input to a Business Rules Engine and then obtain the output provided by the Business Rules Engine. |
|
||||
| Script |  | A Script Task defines a script that the engine can interpret. |
|
||||
| Call Activity |  | A call activity allows you to call and invoke another process as part of this process.processes. |
|
||||
| Sub-Process |  | Sub-processes allow you to collapse and expand tasks to quickly convey information. |
|
||||
|
||||
### Artifacts
|
||||
Artifacts are used to provide additional information or documentation within a process. They include data objects (representing information or data needed for the process), annotations (providing explanatory or descriptive text), and groups (used to visually group related elements).
|
||||
|
||||
[def]: images/Untitled_2.png
|
||||
| **Artifact** | **Symbol** | **Description** |
|
||||
|---------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Data Object | | Data objects can represent data placed to the process, data resulting from the process, data that needs to be collected |
|
||||
| Data Storage | | Data storage provides the ability to store or access data that is associated with a business model. If your process outputs any data, it will become necessary to store that data. |
|
||||
| Group | <div style="height:50px;width:50px">  | Groups organize tasks or processes that have significance in the overall process. |
|
||||
| Annotation | <div style="height:50px;width:50px">  | Annotations allow you to describe the business process and flow objects in more detail. |
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Quick start guide
|
||||
# QuickStart Guide
|
||||
|
||||
```{admonition} Welcome to the SpiffWorkflow quick start guide!
|
||||
:class: info
|
||||
|
|
|
|||