RealAdvice

WarpCore

WorkFlow PM

/

Help

/

Reference

/

Publish checks

Reference

Publish checks

Every check Publish makes, in its order, and how to fix each.

What you need to know

Publish makes twelve checks on a draft version, always in the order below. Publish in the template editor runs them all and lists every one that fails, in this order, so the first item is what publish would refuse with now. Each item has a Go to link to the section that fixes it.

Before the checks, the version must be a draft. A published or retired version cannot be published again.

The checks, in order

#
What the list says
How to fix it
1
“This template cannot be published: no stage is marked as the starting stage.”
On Stages, tick Start on the stage where work begins.
2
It names each stage that nothing moves work into, so no project could ever reach it.
On Transitions, add a transition into each named stage from another stage. Or delete the stage on Stages.
3
“This template cannot be published: no reachable stage is marked as an ending, so a project could never finish.”
On Stages, tick Ending on a stage where work finishes, and make sure a transition leads to it.
4
It counts transitions with “no saved choice of who may move work”, and asks you to choose who may make them.
On Transitions, choose who may make each move. The list on a row shows Anyone on the project even before a choice is saved, so pick another choice, then pick the one you want.
5
It names the empty squares of the Task grid, and says “Set every square, so each task has a place on a person’s board at every stage it can reach.”
On Task grid, set every hatched square. See Fill the task grid quickly.
6
Only when a task waits for another task with Blocks the task. It names the starting stage and its Where it sits in the work choice, and says “so work counts as started before a dependency can hold it”.
On Stages, set the starting stage's Where it sits in the work to Not planned yet or Ready to start.
7
It names the tasks, and says “These tasks are waiting on each other in a circle, so none of them could ever start”.
On Dependencies, change or delete one of the dependencies in the circle.
8
It names a task that can repeat and the dependency that links it to another task, and says “so it cannot wait for another task, and no task can wait for it”.
On Dependencies, delete that dependency. Or, on Tasks, untick Can repeat on the task.
9
It names each ending with no outcome, and asks you to add at least one outcome to each.
On Outcomes, add at least one outcome to each named ending.
10
It names a task that shows on a page of the wrong kind of record, such as a property page, when the kind of work applies to engagements.
On Tasks, change the task's Shows on. Or, if the kind of work is wrong, change its Applies to on Workflow Templates.
11
It names each choice field with no options. For one field it ends “Add its options, or change its type.”
On Fields, type the field's Options, or change its Type.
12
A condition no longer fits its field, for example because an option it tests was removed. For one condition it ends “Change the condition, or remove it.”
On Tasks or Transitions (the link says which), open the conditions with Edit, then change or remove that one.
No records

Things to know

  • Check 2 and the unreached tag on Transitions are the same thing: fix one and the other goes.
  • Check 5 counts squares only for stages work can reach, so fix check 2 first: a new transition can add a column to the grid.
  • A version published by mistake cannot be taken back. Revise it, fix the draft, and publish again: Change a published template.

Good to know

Required fields are not a publish check. A field marked required is shown as required on each project, and work is not stopped while it is empty.