Workflow processes exist in CMS as a special kind of entity, which can have properties and task sequences configured for them.
Some tasks can be performed manually, while others are fully automated. Tasks may determine conditions, necessary to fill in some of the process fields or perform automated / triggered actions, such as sending emails to customers on certain conditions. Task sequences of the process can be organized in many ways, in order to follow a certain workflow and fulfill needed business logic.
Many business processes (like user registration or sales order processing) can be executed in CMS as tasks and will not require additional coding.
For example, if you set up a Sales Order process, the process instance will be invoked each time, there is a new order from a website customer. Each process instance will automatically inherit Customer data and order data, to process each purchase.
Process start can be triggered in 3 ways:
- By front / back end logic
- With an entity trigger (currently on creation / change / or deletion of any item of a specified entity)
At this moment the first task of a process will start. It is necessary to complete the first task in order to start the second one. The second task is triggered immediately after the end of the first task and so on, until the end of the process.