Dynamic check validation

Overview

Dynamic check validation lets you reuse one checklist template while applying different numeric and warning limits per test object or per checklist instance. This is particularly useful when checklist structures are consistent, but the numeric limits and warning limits differ per test object. Instead of creating and maintaining a separate checklist template for each case, limits are provided dynamically via numeric custom fields.

Use Case

You have consistent checklists for your test objects, but the numeric and warning limits are different for each individual test object. To avoid creating new checklist templates for every test object, the numeric check validation should be dynamic per test object.

How limits are provided

Limits are stored at the checklist template as numeric custom fields. The custom field can be mapped on:

• the test object, or

• the checklist instance.

This works for numeric and calculation checks:

• In addition to manually entering fixed limits, you can select numeric custom fields.

• At instantiation, the system tries to read the limit values from the checklist instance or test object custom field values.

Open

Resolution order for limits

When instantiating which limits to apply, the system uses the following order:

1. Checklist instance custom field

2. Test object custom field

3. Checklist template validation (default limits configured on the template)

If a value is found at a higher level, that value is used. If not, the system falls back to the next level.

Technical behavior

• You cannot change the validation afterwards for already executed checklists by modifying the template or changing the custom field values. Executed checklists always keep the limits that were effective at instantiation.