Skip to main content
Use Conditional Logic

Learn how to add conditional logic tasks to your runbooks, meaning you can halt a runbook's progress based upon failure to meet a condition.

Cutover Documentation Team avatar
Written by Cutover Documentation Team
Updated over a week ago

You can add conditional logic tasks to your runbooks, giving you the ability to halt their progress should something such as a validation test fail, for example.

Conditional logic tasks will either pass or fail depending upon one of the following conditions being met in the custom field of a preceding task in the runbook:

  • Equal to a specified value

  • Less than a specified value

  • Greater than a specified value

Any proceeding task will be able to progress provided the conditional logic task has passed. In the event of failure, any linear progression will halt until there is further intervention (such as manually completing the failed conditional logic task).

Note: If conditional logic is available under Task Type (under the Integrations section) when adding a task, then it has been set up and you can add and edit conditional logic tasks.

If it is not visible, you will need to follow the guidance and steps in Prerequisites.

Prerequisites


Important: Conditional logic needs to have been enabled in your instance’s settings. If you are unsure whether this is the case, consult your Customer Success Manager. They will be able to confirm its status and will be able to enable it for you, if required.

You require these roles to be able to do the following:

  • The Integrations admin and Custom fields admin roles to add and configure a Conditional Logic connection in your instance

  • The Runbook Admin role to add a conditional logic task to a runbook and edit it

Follow these steps to add and configure a Conditional Logic connection in your instance:

  1. Go to Settings (cog icon at the bottom of the far left panel) > Integrations.

  2. Click the + icon in the bottom right corner of the Integration Connections page.

  3. Click Conditional Logic in the Available Integration Connections page.

  4. Click Create in the New Conditional Logic Connection pop-up modal.

  5. In the editing panel that appears, click + New in the Integration Actions section.

  6. Under Action in the New Conditional Logic Action pop-up modal, select Custom Field Task Progression.

  7. In the fields that appear, enter ‘Conditional Logic’ as the Name, ensure the Trigger is set as On Task Start, and set Visibility as appropriate if you want it restricted to a specific workspace and not globally visible.

  8. When done, click Create.

This creates the new conditional logic action, meaning Conditional Logic will be available for selection under Task Type (under Integrations) in the task editing panel.

Add and edit a conditional logic task


Follow these steps to add and edit a conditional logic task in a runbook:

  1. When creating your new task, select Conditional Logic from the Task Type dropdown in the task editing panel.

  2. Click on the Conditional Logic section and complete these four settings:

    1. Source task: Start entering the name of the runbook task whose custom field you want to reference in b, and then select the task from the list of suggestions that appears.

    2. Custom field: Start entering the name of the custom field you want to apply your conditional logic against, and then select the custom field from the list of suggestions that appear.

    3. Condition: Select Equals, Less than or Greater than from the dropdown.

    4. Pass value: Enter the value that your set condition either needs to be equal to, less than or greater than. Note: the pass value field is not case sensitive.

  3. Once your conditional logic task is all set up, click Save.

At this point, your conditional logic task is set up and ready to go in your runbook.

Conditional logic in action


When a conditional logic task passes


For simplicity, let’s take the example of a conditional logic task that has been set up with the condition that the pass value in the referenced task’s custom field must be equal to ‘yes’. During the runbook’s execution, given that the referenced custom field does contain the value ‘yes’, the conditional logic task will indicate in green that it has passed because the condition was met.

The proceeding task will be able to begin.

When a conditional logic task fails


Taking the same example as above, if the referenced custom field (‘Has regression testing passed?’) does not contain the value ‘yes’, the conditional logic task will indicate in red that it has failed because the condition was not met.

The conditional logic task will not complete and the proceeding task will not be able to begin. Intervention will be required at this point.

Note: In the case of using a less than/greater than condition, a conditional logic task will fail when finding a non-numeric value in either its given pass value or in the referenced custom field.

Further things to note about conditional logic


  • Conditional logic tasks work in rehearsal mode (provided that Execute in Rehearsal is enabled under ‘Additional Settings’ when creating or editing the conditional logic action).

  • Multiple conditional logic tasks can be used in a runbook.

  • Conditional logic tasks work with non-text custom field types too. For instance, you can configure a conditional logic task to be equal to a specific radio box selection.

  • Conditional logic tasks can be skipped.

Did this answer your question?