Linked task types in planning mode have default expected behaviors and available actions in parent runbooks and in their associated linked runbooks. In this article, we'll cover those scenarios and expected behaviors.
Linked task types — parent runbook
Below, we'll take a look at the expected behaviors and available actions for linked task types in parent runbooks
When a linked task is added to a runbook, you will need to select a template — this is what the linked child runbook will be created from. After the linked runbook has been created and the linked task type is successfully added, the runbook the linked task was added to becomes the parent runbook to the newly created linked runbook.
Note: If you are adding linked tasks to a template, the templates are only converted to a runbook after you create a runbook from the parent template.
Linked task types with associated runbooks will be illustrated by the linked runbooks icon.
To access linked runbooks at any time, click on the name of the associated linked tasks.
Each linked task has a task duration that is set by the linked runbook and cannot be set by the parent runbook.
When a linked task is copied and pasted, the new linked task will be created using the originally selected templates from when the linked task was first added.
Things to note
If a template associated with a linked task type is changed, or a linked task type is removed or changed to another task type, the associated linked runbook will be unlinked.
Linked task types or templates associated with linked task types cannot be edited in bulk.
Linked task types — linked runbook
Below, we'll take a look at the expected behaviors and available actions for linked task types in a linked runbook:
When a linked runbook is in planning mode, a small clock icon on the Play button can indicate one of two "set" states (indicated in the image above):
Not set: This state, illustrated by a gray clock, indicates that the parent runbook has not set a scheduled start time.
Set: This state, illustrated by a blue clock, indicates that the parent runbook has set a scheduled start time.
In a linked runbook, the date and start time displayed in the linked runbook is dictated by the linked task in the parent runbook. To note, a linked runbook's scheduled start time is set by the parent runbook only.
Because a linked runbook cannot begin a run without the parent runbook first initiating the run, two validation errors will display in the linked runbook:
A validation error will appear to illustrate that the associated linked task is not startable.
A validation error will appear to illustrate that the runbook associated with the linked task has not started.
Related articles
Read more about linked runbooks: