Table of Contents

Dependencies

Dynamic checklists can be created thanks to the "Dependencies" feature. This allows you to define which checks should appear depending on the check result. This enables complex workflows with various nestings to be mapped within a checklist.

Create dependencies

To use the feature, a checklist template in draft mode is required. A dependency can be set based on a section. Sections are therefore essential for this feature.

After creating the desired sections and checks, the dependencies can be added. This is possible in the section settings on the right side and the third tab "Dependencies".

Dependencies are to be added to the section that is to appear when the specified conditions are met. Under "Add dependency", the check that will be used as a trigger can be defined. Several checks can also be stored, whose conditions must all be fulfilled. If several checks are stored, the following selection options appear:

One of the dependencies have to apply to activate the section
All dependencies have to apply to activate the section

All checks from the checklist are listed in a drop-down menu with the title of the check. A selection as well as a search via text input is possible. It is also possible to set which condition must be fulfilled and whether the check is positive, negative, executed or not executed.

One check can trigger several sections. The dependency is automatically saved as soon as another field is clicked. If the check that is stored as a dependency in a section is deleted, this dependency is automatically removed. Dependent sections can additionally be marked as optional or mandatory in the section settings.

The feature is available for all check types except for photo and file checks.

This feature is only available within the Testify interface and not in combination with the creation of checklists via Excel.

Dependent checks in practice

The behavior when filling in dependent sections works in principle the same as the general checklist execution. Dependent sections are displayed only after the relevant check has been filled in. The section opens automatically after saving this check at the place where it was added.

Note: If a check is repeated so that the dependency no longer applies to a dependent section that has already been filled in, this section will be closed again and no longer displayed. The result will not be saved in this case.

Note: It is not possible to populate dependent checks via the API.

Examples

Example 1

Check 1 decides whether Check 2 or Check 3 is opened.

Check 1: Sensory evaluation

If Check 1 is positive, Check 2 follows; otherwise, Check 3 is performed.

Check 2: Laboratory analysis

Depending on the results, the product is either approved for sale or rejected.

Check 3: Package integrity test

If Check 1 is negative, Check 3 follows. If the product passes Check 3, it is released for sale. Otherwise, it is considered unfit for sale and further steps must be taken to rectify the problems.