Master checkpoints/checklists

Master Checkpoints/Checklist

Please see the Checkpoints article to understand how Master Checkpoints and Master Checklists are used in Workflows. This article will describe how to actually manage those Master Checkpoints/Checklists and what is the meaning of each of their settings.

Although it is possible to create master checkpoints and checklists completely from the settings page described hereafter, note that it's not the only way to create master checkpoints and checklists: when using a default Winddle workflow or when using the workflow editor, it is possible to create master checkpoints and checklists. However, for updating or deleting those objects, the settings page is the only place.

Accessing the settings page

To access the settings for your company's master checkpoints and checklists, open the user menu, select Company settings, then open the Workflow group and select Checklists.

Managing master checklists

Creating a new master checklist

Click on the  in the top left corner, enter a name and validate. The checklist will be added and selected.

Names for master checklists should be between 2 and 100 characters.

Changing the icon

To change the icon of the master checklist, click on the icon in the header. A modal will appear, select a different icon and click on apply icon.

Renaming the master checklist

To rename a master checklist, click on the name in the selected checklist header, update and validate.

Deleting the master checklist

When a master checklist can be deleted, the delete button will appear in the top right corner, next to the button to add a checkpoint.

However, if there currently are any Master Checkpoints of this checklist in use in a Workflow template or in use in a Project Line, the Delete button will be replaced by an In Use label. Those dependencies needs to be cleared first.

Managing master checkpoints

Creating a new master checkpoint

To add a master checkpoint to a master checklist, first select the master checklist, then click on  in the top right corner. Enter the checkpoint name and validate.

Master checkpoint names have to be unique within a master checklist and must be between 2 and 100 characters long.

Average duration

It is not possible to set the average duration of a master checkpoint: this value is computed automatically by Winddle from its actual usage within your company. 

Whenever a checkpoint using this master checkpoint is validated, this value will be updated. It is used as a default duration when using the master checkpoint in a workflow template or in a project line.

The value is computed as an average of the actual duration of the last ten validated checkpoints using this master checkpoint, creating a moving average with a window of 10 checkpoints.

Renaming the master checkpoint

To rename a master checkpoint, just click on its name, update it and validate.

Changing its description

Changing the description is similar to changing the name, click on the description, update it and validate. The description will then be visible in the checkpoints using this master checkpoint, giving some context to the task at hand.

Changing its group

Changing the group of a master checkpoint is done in the same way as editing its name, just click on the group, update it and validate. Winddle will provide a list of the currently existing groups to help entering the same values correctly, if none of the existing groups are correct, you can just type in a new value and use it.

Master checkpoint groups are used in statistics to group together multiple checkpoints in order to compute certain metrics, such as lead time. They have no other use, at the moment.

Enabling the Pass/Fail behavior

The Pass/Fail behavior, when enabled, will add a secondary status to Checkpoints - see the checkpoint details article -, representing an inspection status or any type of activity leading to a result (different from the status of the checkpoint, which indicates if the checkpoint is done or not), which can either passed, be failed, or be with reserve. 

To enable this behavior, just click the checkbox. The change is automatically saved.

When a Checkpoint with Pass/Fail behavior is marked as Failed or With reserve it is possible to Retry it (see checkpoint details article). By default the Retry concerns the checkpoint itself, but it is possible to enlarge the Retry Scope to direct parents or Parents and Grandparents checkpoint. This means that launching a Retry will relaunch a new attempt of a given set of checkpoints. 

To update the Retry scope, use the drop down above the Pass/Fail option. 

Enabling the Booking Behavior

The Booking behavior, when enabled, will allow to enter a date of a booked event when validating the given checkpoint. Both dates of validation, and date of booking will be saved. The selected date of booking will automatically update the starting date of the direct child checkpoint. 

The Booking behavior is useful for all your Bookings checkpoints for which you need to track if the booking is done or not, but also to know at which date the event has been booked. Make sure to directly link the Booking Checkpoint to the related Event Checkpoint in your workflows to ensure correct date updates.

To enable this behavior, just click the checkbox. The change is automatically saved.

Deleting a master checkpoint

When the master checkpoint isn't used anywhere (neither in a workflow template nor in a project line workflow), you can delete it by clicking on the Delete button.

If the master checkpoint is in use and the Delete button isn't available, try to first delete those dependencies, then try again.There are multiple ways to find where a master checkpoint is used: from the dashboard, in the statistics, on the project list (filtering on either validated or non validated checkpoint), etc.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk