STEPS, STATUS, And Actions Each specific process has at least one current Steps at any time, and the current Steps also has a Status, which represents the Status of the process instance. The value of Status can be Underway or Queued. After a STEP is over, it is no longer the current STEP, usually a new current STEP is now generated so that the process continues to operate. The last Status of the end STEP is set to the OLD-STATUS property, which must be set before the process is turned to the new transition to the new STEP, which is generally set to Finished. Transition itself is an action of Action, a STEP can have multiple Actions, which is determined by end users, external events, or automatic triggers. Transition is generated in accordance with the completion of the action. Each Action has at least one Unconditional Result and any Conditional Results.
Result, Joins, And Splitsunconditional Result is a series of instructions to determine the next task of the process. It causes the conversion of process state in the state machine. The Conditional Result contains a range of conditions for Condition, the first condition is TRUE to indicate the conversion of the flow state. Three kinds of Result may occur: step; split; join.
A warning: Current Split or Join can no longer result to a split or join For the case where STEP is reached:
External FunctionsSworkflow defines the Functions method to perform external business logic and application services, divided into two categories: Pre & Post Step functions. Pre function is called before the process transfer (Transition), is usually some simple and fast applications. POST functions and preunctions are in the same application range, but they are only called after the process state changes, usually time-consuming applications. Functions can be named different locations: Steps and Actions. For functions: pre-func -> action defined on Actions: Action -> POST-FUNC ==> Next Step For Functions: Action on STEP -> Pre-func -> Step State Change -> POST-FUNC -> Next StepValidatorsValidator is some code that can verify the input of the action. If you pass the verification, the Action is executed; otherwise INVALIDInputException
RegistersRegister is a function that returns a public object, usually this object can be used throughout the process, such as files, original data, tasks, and more.
Variable interpolation uses parameters in Condition, Function, Validator, and Register. STATUS, OLD-STATUS, OWNER and other process descriptors are dynamically resolved, and the general variable is defined as $ {foo}. Osworkflow sees such a variable, it will be found in the TransientVars Map. If you can't find it to the propertySet, if you still can't find it, set it to empty. It is worth noting that if a parameter is a mixture of characters and variables, it will be considered a character. For example, below
Auto Actions Automatically performs Action. As long as the specified Action's auto property is set to "True".
