Persistent Checklists

What is a Persistent Checklist?

A Persistent Checklist enables you to share Checklist steps between multiple, consecutive Workflow statuses. If persistency is applied to a Checklist, a Client can progress in the Workflow without the particular Checklist being completed. The Persistent Checklist must be completed in the status of its last consecutive occurence.

---

Example

An example use-case would be a Back-up Checklist for the old device which needs to be completed by the Client user (owner) of the device. It contains a handful of important but manual steps that need to be taken care of before the old device can be exchanged by the new one.

The following diagramm uses the "complete" arrows to visualize, when the Checklists need to be completed in order for the Client to move to the next status:

Since the blue Back-up Checklist is the Persistent one and it was added to both statuses Staging and In Delivery, it has the same state in both statuses in terms of the Checklist steps values.

The corresponding Workflow would look like this:

In the Workflow editor, the Persistent Checklists are highlighted if the persistency is applied.

Like this, the Back-up Checklist will

• not block the Rollout crew from moving the Client from Staging to In Delivery

• occur in both of the statuses to be worked on

Because the Client user has time until the Client should advance from In Delivery to Done to complete the Back-up Checklist.

---

Edge Case behaviour

If a Persistent Checklist is added to multiple Workflow statuses except for one in between, the persistency is not applied to the individual occurence:

---

Summary

A Persistent Checklist should be used when you have work steps that

• can or should be worked on throughout multiple statuses

• should not block these statuses from completion until the work steps definitely need to be finished