Docs/basics content (#315)
* Basics content add * Fixing the stylesheet so forms wrap correctly. * fixing basics symbols --------- Co-authored-by: danfunk <daniel.h.funk@gmail.com>
usama9500
GitHub
|
Before Width: | Height: | Size: 1.9 KiB |
|
Before Width: | Height: | Size: 1.8 KiB |
|
Before Width: | Height: | Size: 1.9 KiB |
|
Before Width: | Height: | Size: 1.8 KiB |
|
Before Width: | Height: | Size: 2.1 KiB |
|
Before Width: | Height: | Size: 2.0 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 1.4 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 1.4 KiB |
|
After Width: | Height: | Size: 2.5 KiB |
|
After Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 1.8 KiB |
|
After Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 1.0 KiB |
|
After Width: | Height: | Size: 1.3 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 1.3 KiB |
|
After Width: | Height: | Size: 2.1 KiB |
|
After Width: | Height: | Size: 1.3 KiB |
|
Before Width: | Height: | Size: 1.7 KiB After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
Before Width: | Height: | Size: 1.5 KiB |
|
|
@ -17,34 +17,33 @@ Tasks represent activities or work that needs to be performed as part of a proce
|
|||
|
||||
| **Task** | **Symbol** | **Description** |
|
||||
|---------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Service | <div style="width:100px"></div>  | Task that uses a Web service, an automated application, or other kinds of service in completing the task. |
|
||||
| Send | <div style="width:100px"></div> | Task that sends a Message to another pool. The Task is completed once the Message has been sent. |
|
||||
| Receive | <div style="width:100px"></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 |  | 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. | |
|
||||
| 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. |
|
||||
| Parallel event-based gateway |  | This gateway is similar to a parallel gateway. It allows for multiple processes to happen at the same time, but unlike the parallel gateway, the processes depend on specific events. |
|
||||
| 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. |
|
||||
| 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. |
|
||||
| |
|
||||
|
||||
### Flows
|
||||
|
|
|
|||