What you need to know
Dependencies lists what each task of the version waits for. A can be another task, a document, an outside party, an approval or a date. You change one in its row, and each change saves as you make it; you add one under Add a dependency. Publish checks that no tasks wait for each other in a circle.
Good to know
A task that waits for a task of another template, such as an engagement’s work and a property’s, is not listed here: the ProperTax loader writes those links. The task's card shows them.How to get here
Open the template from Workflow Templates, then select Edit on a draft (or View on a published or retired version). In the template editor's left menu, select Dependencies.
What is on this screen
Under the heading What each task is waiting on, one row per dependency: the task that waits, the kind of waiting, the fields that kind needs, and Enforcement, then a trash icon. With none yet, the list says “No dependencies recorded yet.”
On a draft, Add a dependency sits under the list. Here, one task waits for another:
What you can do here
- Make a task wait for something.
- Change a dependency in its row. A choice saves as you make it; a typed value, such as Offset (days), saves when you leave the field. If a change leaves a field the kind needs empty, such as a new kind of waiting, that field says “Required” and nothing saves until you fill it. Choose the saved kind again to go back to the saved row.
- Delete one with its trash icon. It asks Delete this dependency? and says “This edits the draft only. A running project that already recorded this relationship is unaffected.”
Who can do what here
Anyone with a role in the department can open this section and read it. Adding, changing and deleting are for a department manager or a company administrator. If your role does not allow it, a message at the bottom right says so and nothing changes. See Who can see and do what.
Things to know
- Like the other sections, this one saves as you go: the line under the title says “changes save as you make them”. On a published or retired version it says “this version is read-only”, as the other sections do.
- Tick more than one document under Add a dependency and the form says “Checking more than one records a separate dependency for each.” Each one then has its own row, so each can arrive on its own. A row holds one document: to wait for another one too, add it.
- A task that can repeat (Can repeat on Tasks) cannot wait for another task, and no task can wait for it: Blocked by another task and Invalidated by another task refuse it, with a message at the bottom right. See Tasks.
- Publish refuses a version where tasks wait for each other in a circle, through Blocked by another task or Invalidated by another task. See Publish checks.
- On a published or retired version you can read this section but not change it.
What a running project does with these
The heading's line says “A task cannot move while a task that blocks it is not done. A manager can still move it and give the reason.” On a running project:- A task blocked by another task with Blocks the task cannot move while that task is not done. A manager, or a person whose access says May override, can move it anyway and give the reason. One override is enough: the task then shows Started without its prerequisites, and its later moves do not wait for that task. With Allowed, marks the output provisional, the task can move, and it shows that it is still waiting. This check is on unless your company has switched it off.
- A task that waits on an approval cannot be finished until the approval is given, unless its enforcement is Shown only, does not block. This check is on unless your company has switched it off.
- A document, an outside party or an approval is requested from the task on the record's Work panel. A date wait starts by itself. With the anchor Pre-reassessment call, the date is three months before the state's notice date for the property's reassessment year, and a property with no such date has no wait.