Page History

In SimpleOne, workflows provide an interface for automating multi-step Workflow is a tool that allows configuring complex 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 The Workflow Editor displays processes 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 boxesset of boxes and arrows representing transitions, conditions, and stages. Set the sequence of steps and stages your business needs by using various types of activities: utilities, conditions, approvals, subflow, and timer.

Workflow is a complex tool consisting of the following partsGenerally, workflow consists of:

• Properties: such as workflow name, the table whose records the workflow acts on, and the conditions under which to run it.
• Versions: specific workflow version information stored in a Workflow Context record.
• Activities: the sequence of the operations the workflow performs, for example, generating records or running scripts.
• Activity Exits: specify the conditions under which to run a transition.
•  general information and setting of the workflow such as name, table on the basis of which this workflow runs, conditions to start executing the process, description of the workflow.
• Versions: workflow versions stored in the Workflow Versions table.
• Activities: a set of operations arranged in a particular order and performed by the workflow (for example, changing the value of a certain field).
• Activity Exits: conditions to be met to proceed to a particular transition.
• Transitions: the Transitions: the connection between the activity exit and the next activity.
• Contexts: specific workflow runtime information stored in a Workflow Context record information about every time a workflow was executed stored in the Workflow Context table.

Workflow life cycle

A The 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 running when conditions specified in the parameters are met. Usually, starting conditions are record insertion, field update, field with a particular value. For example, you might create a workflow, that runs whenever a user submits 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:

the Incident table has a workflow executed every time when a new record is created.

After the starting event, the workflow executes activities one after another according to the defined transitions. As a rule, activities have more than one transition – the path taken depends on the activity outcome.

Within an activity, workflow performs the following steps:

1. Operation defined by the activity is executed.
2. Activity conditions are checked.
3. Depending on the previous step's outcome, the workflow transitions to the defined
4. An activity is processed, and an action defined by that activity occurs.
5. At the completion of an action by an activity, the workflow checks the activity's conditions.
6. For each matching condition, the workflow follows the transition to the next activity.

Workflow states

Generally, the workflow can be in one of two states - Checked Out or Published.The :

• Checked Out

•  – for editing new or existing workflows.
• Published – for the finalized workflows ready to be run; finalized but unpublished workflows are inactive and non-functional.

Checked Out

When you start working on your workflow (whether a new or existing one), it is in the Checked Out state. In this state, other Other users cannot edit this workflow along with you , since the workflow is already checked out. Also, the workflow is inactive when checked out; it needs to be published to enable it.

To check out your workflow, navigate to the hamburger menu (Image Removed) in the Control Panel, and click Publish.

The Published state is intended for the finalized workflows ready to be run; finalized but unpublished workflows are inactive and non-functional.

Image Removed

enable editing a published workflow, perform the following steps:

1. Open the workflow you need in the Workflow Editor.
2. Navigate to the hamburger menu Image Added.
3. Click Check Out.

Published

When the workflow configuration is completed, and the process is ready to run, you need to change the workflow state to Published. After that, users are not able to edit the workflow (until it is back to the Checked Out state).

To publish a workflow, perform the following steps:

1. Open the workflow you need in the Workflow Editor.
2. Navigate to the hamburger menu Image Added.
3. Click Publish.

How it works

1. You just created are creating a new workflow (version 1, for example). It has the Checked Out state equal to TRUE 'true' and the Published state equal to FALSE'false'.
2. You have edited it to the end, and then you finished configuring this workflow and decided to publish it. You click Publish, and your workflow now has the Checked Out state equal to FALSE 'false' and the Published state equal to TRUE'true'.
3. In a while, you need to modify it, and you make a checkout, what this has happened:
   1. There's a A copy of the existing workflow has been created.
   2. The existing workflow was not affected.
   3. The copy created has the Checked Out state equal to TRUE 'true' and the Published state equal to FALSE'false'.
4. You have finished editing this copy and published it (it is now version 2), what this has happened.:
   1. The previous workflow (that was version 1) moves to workflow archive (now it has the Checked Out and Published states – both equal to FALSE'false').
   2. The workflow you were working on (version 2) is now an the active one.