Skip to main content
Step Dependence

A Guide to Step Dependency and and/or logic.

Updated over a week ago

Step Dependency is used to require the specified step(s) to be completed prior to unlocking or entering information on the current step.

ADDING STEP DEPENDENCIES INTO A PROCEDURE


Navigate to a procedure's homepage using either:

  • CMD+K / CTRL+K to search for it

  • Master Procedures page

Click EDIT, EDIT DRAFT, or NEW DRAFT to step into an edit mode on a specific procedure (depending on what state your procedure is in).

Scroll to the step you would like add a dependency to.

Click the ADD DEPENDENCY drop down and select the desired step predecessor.

Dependencies can be added using AND/OR logic.

Adding two or more dependencies into the same block sets OR logic so the dependency is met if ANY 1 requirement per block is satisfied.

Each individual dependency block must be satisfied to unlock the step - multiple blocks use AND logic.

Ex: This step can not be unlocked until C1 AND either B1 OR D1 is completed.

ALERT! Be careful when setting up too many dependencies as you can over constrain your procedure.

Once added, click the eye icon to enter Preview mode.

You will see "Requirements Unmet" which is preventing signoff and field input.

You can also see which requirement(s) need to be met in order to begin the step.

Once the necessary requirements are met, the step will be unlocked.

Step Dependence is similar to Conditionals without affecting the flow of the run. Check out our article on Conditionals for more info.

Did this answer your question?