Workflow
A workflow is a model of a process in your program. It could be the progression of “a blog topic from draft to review to publication.” Another example is when a user submits a series of different forms to complete a task. Such processes are best separated from your models and should be defined in configuration information.
The definition (definition) of a workflow includes places (locations) and actions (actions) to go from one location to another. Actions are called transistions (transitions). The workflow also needs to know where each object is in the workflow. That marking store writes a property of the object to remember the current location.
The above proper nouns are generally used to discuss workflow and Petri nets.
Workflow component supports state machines. A state machine is a subset of a workflow whose purpose is to hold a state of your model. You can read more about the different and specific functions of state machines in Workflow as State Machine.
Example ¶
The simplest workflow is the following. It includes two places and a transition.
When used to describe a real business, workflow can be more complex. The following workflow describes the process of filling in the job program.
When you fill out a job in this example, there are 4 to 7 steps depending on the job requested. Some jobs require personality tests, logic tests, and/or require users to fill out formal requirements. Others don't. GuardEvent Used to decide "what is the next allowed step" in a specific program.
By defining a workflow like this, you can get an overview of how the process is displayed. The logic of the process is not confused with the controller, model layer or view layer. The order of steps can only be changed by changing the "configuration information".
