In SimpleOne, workflows provide an interface for automating multi-step processes across the solution. Each workflow consists of activities, such as generating records, notifying users of pending approvals, or running scripts. The graphical Workflow Editor represents workflows visually as a type of flowchart. It shows activities as boxes labeled with information about that activity and transitions from one activity to the next as lines connecting the boxes.

Generally, workflow consists of:

• Properties: such as workflow name, the table whose records the workflow acts on, and the conditions under which to run it.
• Activities: the sequence of the operations the workflow performs, for example, generating records or running scripts.
• Transitions: specify the conditions under which to run the activity.
• Exit Conditions: specify the conditions under which to run a transition.
• Contexts: specific workflow runtime information stored in a Workflow Context record.
• Versions: specific workflow version information stored in a Workflow Context record.

Workflow life cycle

A workflow starts when a triggering event occurs, Common triggers are, for example, a record insertion into a specific table, or setting a particular field in a table to a specified value. For example, you might create a workflow, that runs whenever a user raises a major or an infrastructure Incident. You can also schedule workflows to run periodically or call them from scripts such as business rules.

After activity completion, the workflow transitions to the next activity, or the exit. An activity might have more than one different possible transitions to various activities, depending on the activity outcome.

The graphical Workflow Editor displays workflows as a flowchart. It shows activities as boxes labeled with information about that activity and transitions from one activity to another as lines connecting the boxes.

At each step in a workflow:

1. An activity is processed, and an action defined by that activity occurs.
2. At the completion of an action by an activity, the workflow checks the activity's conditions.
3. For each matching condition, the workflow follows the transition to the next activity.