Documentation › Create a Process

Create a Process: the blueprint of your work

A Process is the blueprint for work that repeats: which steps, in what order, assigned to whom, with what deadlines. You draw it like a diagram, then each time you start it, it becomes a concrete process instance.

In the process you draw steps; once a process instance is started, each step becomes a task given to a person.

⏱ 5 minutes📍 Processes tab🎯 Result: a published process

What is a Process for?

Start Create account✉ Email · IT support IT equipment⚙ Task · 2 days Approve equipment★ Milestone Approved? Training🗓 Meeting End YesNoEach rectangle is a step assigned to a person or a group.
An example process: onboarding a new employee. Steps read from left to right and top to bottom.

The step types available in the editor:

StepIt represents…
PhaseA group of steps, with a recommended duration and, if needed, a number of repetitions ("Group steps and repeat them").
EmailAn email to send: recipients (To, CC, BCC), subject and message body.
MeetingA meeting: required and optional attendees (Required attendees, Optional attendees), subject and invitation message.
DocumentOne or more documents to produce or provide (see the Use an Artifact in a Process page).
TaskA free-form task carried out by the assigned person.
Azure DevOpsCreates a work item (product backlog item, bug, task…) in Azure DevOps. How it works.
MilestoneA key point in the process.
ConditionA branch: the path depends on conditions.
WaitA wait: for a delay (months, days, hours, minutes) or until a given moment (next Monday, a day of next month, a date).
Join BarMerges several paths into one.
EndThe end of the process.

1. Create the Process

  1. Open the Processes tab

    Click Processes in the top bar.

  2. Click New process

    The Create New Process panel opens.

  3. Name it

    Enter the Process name (required) and, if needed, the Contributors who will be able to edit it.

  4. Click Save

    The process appears in the list. Use the pencil Edit to open the editor.

2. Draw the flow

  1. Declare the people and the variables (Start block)

    Double-click Start (Editor Configuration): you will find a Description (what the process does, visible to the people who start it), the list of Variables (the process's information) and Users and groups (the people and groups from which you will pick the owners). A group can also have participants (With participants): seats to be taken, filled with real people when the process instance starts.

  2. Add the steps

    Drag Email, Meeting, Document, Task, Milestone or Phase from the left column onto the grid.

  3. Link them

    Drag a link from a step's handle to the next one. Use Condition to create alternative paths and Join Bar to merge them.

  4. Finish with End

    Place an End step at the end of each path to mark the end of the process.

Create a Process, from creation to publication
My tasksActivityProcess instancesProcessesArtifacts

Processes

Design the processes your process instances are built from
Search processes+ New process
PRPurchase requestv2.0Published✎ 🗑
Create New Process
Process name *
New employee onboarding
Contributors
Sophie Martin
CancelSave
My tasksActivityProcess instancesProcessesArtifacts

Processes

Design the processes your process instances are built from
Search processes+ New process
NENew employee onboardingDraftDraft✎ 🗑
PRPurchase requestv2.0Published✎ 🗑
Process editorSave draftPublish
Phase
Email
Document
Meeting
Task
Milestone
Condition
Wait
Join Bar
End
Start
✉ Create account
⚙ IT equipment
◆ Approved?
🗓 Training
📄 HR welcome
Process editorSave draftPublish
✉ Create account
Email — Send an email when this step runs
PropertiesAttachmentsOutcomesReviewersAppearance
Title
Create account
Assigned to
IT support
Required
Yes
CancelSave
Process editorSave draftPublish
Start
✉ Create account
⚙ IT equipment
◆ Approved?
🗓 Training
📄 HR welcome
✓ Published

3. Configure a step

Double-click a step: its panel opens. Depending on the type, you will find tabs there:

TabWhat you set there
PropertiesThe name (Title), the Required option (mandatory step), the assigned people (Assigned to), the description, the estimated effort and the reminder before the due date.
AttachmentsThe step's files: to upload, to provide later, or generated from a template.
OutcomesThe information to fill in when the step is finished. It is mandatory if the step is Required.
ReviewersThe people who check the step's result before it is considered done.
Signers / ValidatorsThe people who sign the documents of a Document step (Signers), or who confirm that a milestone has been reached (Validators, Milestone step).
AppearanceThe step's colors in the diagram (purely for visual comfort).

A Required step has to be completed: it can only be set to "Done" once all its Outcomes are filled in.

Wait until Monday, next month or a date

In the panel of a Wait step, the Wait list chooses what the process waits for:

ChoiceThe process goes on…
For a delayafter the time entered (Minutes, Hours, Days, Months, Years).
Until next weekdayon the coming Monday, Tuesday… chosen in Weekday. If today is already that day, the process waits for the following week.
Until a day of next monthon the day chosen in Day of next month (1 for "the beginning of next month"). In a shorter month, it goes on on the last day of the month.
Until a dateon the Date chosen, or on the date held by a Date variable (Linked variable button). A date already past does not make the process wait.

For the last three choices, Time of the day sets the time the process goes on (09:00 by default). The steps after the wait start at that moment. Until a date needs a date: without one, the step cannot be saved.

4. Save and publish

  1. Save draft

    Saves a minor version (draft): handy for carrying on later. A dialog asks you to confirm first.

  2. Publish

    Publishes a major version. A dialog asks you to confirm first. This is the one you will be able to choose when you start a process instance.

Only published processes are offered when you start a process instance. If yours cannot be found, check that it has actually been published.

View the details

To see who created a Process, when, and how many versions exist, click the View details icon (the “i”) on its row in the Processes page. A panel opens on the right, without leaving the list:

The Open process button opens the editor; Close, the cross or the Esc key close the panel. The pen icon (Edit) opens the editor straight away, without showing the panel.

5. Delete a Process

A Process you no longer need is deleted from the Processes page: click the bin icon (Delete) on its row, or open it in the editor and choose More → Delete process. Confirm, and the Process leaves the list.

A deleted Process can no longer be chosen to start a process instance.

Good practices

Permissions

What you can do with a Process depends on your roles. You need Create processes to see the New process button. To edit a Process (Save draft, Publish) or to delete it, you need Edit processes or Delete processes and to be its owner or a contributor (unless you have Manage all processes and artifacts). Otherwise the pencil, the trash, Save draft and Publish are hidden. With the Viewer role you can only look.

Rights on processes are separate from those on Artifacts: being a contributor of an Artifact does not let you edit a process.

Everything about roles and permissions: Users and roles.