Difference between revisions of "Workflow Course: Lesson 3"
| Line 20: | Line 20: | ||
All workflow starting with only one start box. This is mandatory. Can not be more than one start box defined into one workflow. When workflow start executing from start task and flows across output transitions conected with this to other inmediatly. | All workflow starting with only one start box. This is mandatory. Can not be more than one start box defined into one workflow. When workflow start executing from start task and flows across output transitions conected with this to other inmediatly. | ||
| − | [[File:box_start.png]] | + | [[File:box_start.png|center]] |
'''TASK''' | '''TASK''' | ||
| Line 26: | Line 26: | ||
When into workflow is needed human interaction, this is defined as a task. Workflow will be stopped here waiting for human intervention, after it flows across output transactions to others inmidiatly. | When into workflow is needed human interaction, this is defined as a task. Workflow will be stopped here waiting for human intervention, after it flows across output transactions to others inmidiatly. | ||
| − | [[File:box_task.png]] | + | [[File:box_task.png|center]] |
'''NODE''' | '''NODE''' | ||
| Line 32: | Line 32: | ||
Node are used usually for doing complex logic evaluations or actions. The idea of adding some node in workflow is doing some something ( for example adding some register in DBMS, etc... ). When workflow arrives to node execution, it's executed inmidiatly and flows across output transactionto to other inmediatly. Basically in node workflow will never be stopped waiting for anything, will executing their logic and will continue inmidiatly to other nodes. | Node are used usually for doing complex logic evaluations or actions. The idea of adding some node in workflow is doing some something ( for example adding some register in DBMS, etc... ). When workflow arrives to node execution, it's executed inmidiatly and flows across output transactionto to other inmediatly. Basically in node workflow will never be stopped waiting for anything, will executing their logic and will continue inmidiatly to other nodes. | ||
| − | [[File:box_node.png]] | + | [[File:box_node.png|center]] |
'''END''' | '''END''' | ||
| Line 38: | Line 38: | ||
At least must be one end node, but could be several is same workflow ( remember only one start node but several end nodes in a workflow ). When workflow arrives to some end node, workflow will be automatically finished. | At least must be one end node, but could be several is same workflow ( remember only one start node but several end nodes in a workflow ). When workflow arrives to some end node, workflow will be automatically finished. | ||
| − | [[File:box_end.png]] | + | [[File:box_end.png|center]] |
=== Transactions === | === Transactions === | ||
Transaction is a connection between two boxes and is represented as an arrow. During transaction execution can be executed some action. Workflow not stops during transaction execution. | Transaction is a connection between two boxes and is represented as an arrow. During transaction execution can be executed some action. Workflow not stops during transaction execution. | ||
| − | [[File:transition.png]] | + | [[File:transition.png|center]] |
=== Action === | === Action === | ||
Latest revision as of 08:15, 26 April 2013
Business logic
Understanding bussines logic as a serie of tasks to be executed if certain conditions are met, sequentially or in parallel, or keep waiting for some event to resume execution.
BPM - Business Process Management
The set of these tasks is called business logic. The business process modeling is responsible for business processes and defines the workflow that governs its operation.
A workflow model graphically the relationships between different tasks.
Basic Workflow elements
- Nodes ( represented as box )
- Transactions ( represented as rows )
- Actions ( in nodes / transactions can be executed actions ).
Basic nodes
START
All workflow starting with only one start box. This is mandatory. Can not be more than one start box defined into one workflow. When workflow start executing from start task and flows across output transitions conected with this to other inmediatly.
TASK
When into workflow is needed human interaction, this is defined as a task. Workflow will be stopped here waiting for human intervention, after it flows across output transactions to others inmidiatly.
NODE
Node are used usually for doing complex logic evaluations or actions. The idea of adding some node in workflow is doing some something ( for example adding some register in DBMS, etc... ). When workflow arrives to node execution, it's executed inmidiatly and flows across output transactionto to other inmediatly. Basically in node workflow will never be stopped waiting for anything, will executing their logic and will continue inmidiatly to other nodes.
END
At least must be one end node, but could be several is same workflow ( remember only one start node but several end nodes in a workflow ). When workflow arrives to some end node, workflow will be automatically finished.
Transactions
Transaction is a connection between two boxes and is represented as an arrow. During transaction execution can be executed some action. Workflow not stops during transaction execution.
Action
Actions are some parts of the logic implemented as a programs. These programs can do several actions like connecting with thirdparty applications to retrieve or store data, send mails, evaluate workflow variables and take some decisión etc... For doing it can be used java classes or scripting for doing it.
