What is a Workflow

The aim of this guide is to provide you with a general introduction to workflows, ranging from simple workflows through to more complex processes. There is also context specific help available within the editors within 12d Synergy.

1.1.  What is a Workflow?

Most businesses have processes, at a high level – when a project moves through many gates and phases – or at a day to day level, like a CAD design process. For example, a CAD design process might go through many steps.

1. The work is assigned
2. The CAD operator begins work
3. The CAD operator requests a review from the designated reviewer
4. The reviewer either signs it off, or rejects it with markups to explain problems

This is essentially a workflow, made up of several steps.

1. Pending Design
2. In Progress
3. Pending Review
4. Rejected
5. Signed Off

1.2.  Workflows in 12d Synergy

1.2.1.  Terminology

In 12d Synergy Workflows, the steps are referred to as States.

And there are also some rules that define which State you can get to next – these are called Transitions.

Each Transition can also define what should happen – like whether or not someone should receive an email, whether or not the Transition can take place, or if extra data is required.

The ability to perform some action is called an Activity.

The ability to set up additional rules is called a Condition.

You can use Data Capture to prompt users for more information.

An instance of a workflow refers to the current state of a workflow when it is applied against a specific entity – for example, a workflow may run over many files, with an instance of the workflow for each one.

1.2.2.  Workflows and Attributes

Workflows are setup as Attributes, which means you can run a workflow against almost anything in the 12d Synergy, including:

1. Jobs
2. Folders
3. Files
4. 12d Model Projects
5. Tasks
6. You must use a List type attribute, with one item for each State you want in your workflow.

1.2.3.  Workflows are General

It is really important to understand that workflows won’t, most likely, run against just one Job or just one File. They are going to be reused. It will be important to factor that in when designing your workflow. You can’t run out of attributes or workflows, you can always create another one if you need to.