Checklist and check settings

General

In this area the title and description can be edited. It is also possible to add PDF protocol profiles and display an unfilled print preview.

Attachments

Attachments (documents, photos and videos) can be attached here. This can be helpful to give instructions for the execution.

Data size see info field at the bottom of this page.

Attachments

These attachments are stored during the checklist execution for each check and can be called up via the context menu.

Start Score

Adding a start value for the score points of a checklist.

This can be negative as well as positive. Depending on the check results, the achieved score can be higher or lower (in case of minus points) than the start value.

General

In this area, the title and description can be edited.

Attachments

Attachments (documents, photos and videos) can be attached here. This can be helpful to give instructions for the execution.

Data size see info field at the bottom of this page.

General

In this area, the title and description can be edited.

It is also possible to add a check identifier. With this option, the person running the checklist can access the section only if the correct identification is entered. The identification can also be entered by scanning different types of codes. (e.g. QR code or via NFC).
A valid QR code is required to use QR codes in Testify. The check identifier and the stored text in the QR code must be identical. Instead of manual selection, a check can be selected using "Scan data code".

It is also possible to define whether individual sections are mandatory or optional. By clicking on the context menu within a section, the following elements can be selected via dropdown:

• Required = The section must be executed

• Optional (Default disabled) = The execution of the section is enabled by default
  (Opt Out)

• Optional (Default enabled) = The execution of the section is disabled by default
  (Opt In).

Attachments

Attachments (documents, photos and videos) can be attached here. This can be helpful to give instructions for the execution.

Data size see info field at the bottom of this page.

Dependencies

If dependencies are stored, the section only appears if the requirements have been met. Any number of dependencies can be stored. The section only appears if the selected dependent check(s) is/are positive, negative, executed or not executed.

The feature is available for all types of checks except photo and file checks.Further information under https://testify.atlassian.net/wiki/spaces/TWN/pages/2547580929

General

In this area, the title and description can be edited.

It is also possible to add an check identifier. With this option, the person running the checklist can access the check only after entering the correct identifier. The identifier can also be entered by scanning different types of codes. (e.g. QR code or via NFC). A valid QR code is required to use QR codes in Testify. The check identifier as well as the stored text in the QR code must be identical. Instead of manual selection, a check can be selected using "Scan data code".

Also, one or more check categories can be selected.

Attachments

Attachments (documents, photos, …) can be added to the check here. This might be helpful for providing instructions for carrying out complicated checks.

Data size see info field at the bottom of this page.

Equipment (Types)

In this section, a specific device can be defined with which the check is to be executed. Either one Equipment type, several pieces of equipment or a specific piece of equipment can be stored. It is recommended to store a specific piece of equipment. Examples

• Thermometers for temperature controls

• Scales for weight checks

• Torque check of all screws

If external sensor data are stored with the equipment, they can be filled in automatically during execution. Further information under https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197212/Execute+checklist#Importing-external-sensor-data

Execute checks with measuring equipment: https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197212/Execute+checklist#Equipment

Note

If enabled, the user can open the note or it gets displayed if a new entered test result is invalid. (e.g. “add issue in case of an invalid test result“)

Format

Here the format of the input can be edited. The lable of the input field can be changed. For checks involving numbers a unit and decimal places can be adjusted.

Validation

The validation section provides the option to validate the test results based on the input. A range can be defined in which the input has to be in order to give a valid result.

Display/Configuration

This section gives the opportunity to change the display of the check. Enabling the quick input will give the person who is carrying out the checks the option to put in the result without navigating into the check. For single and multiple choice checks the configuration of the answers can be done here.

Scoring

Scoring can be used to add weightings to a check within a checklist.

In addition to the possibility of giving check results a scoring that is positive, negative or equal to zero, the field can be left blank. An empty field means that this result is not relevant and will not be included. If this check result was selected during checklist execution, the check will not be included in the overall scoring. This can be useful for audits, for example.

• Example positive value: 10

• Example negative value: -10

By this evaluation it is possible to get a total from the checklist, how positive or negative the audit result is. If a start value was set in the checklist settings at the beginning, the points achieved are added/subtracted from this value.

In this way, 5S audits, for example, can be mapped optimally.

JSON

For text checks, a QR/DataMatrix code can be scanned that contains a JSON object. The relevant keys are extracted from this JSON and the result is displayed during the text check. In the menu item "JSON" the JSON structure can be configured, a sample JSON can be inserted and the important keys can be selected.

Validation: When validating whether the DataMatrix code is a JSON or not, only the first and last characters are checked. In case of "{", it is treated as a JSON.

Error handling: If the key could not be found, the error message "JSON key not found" appears with red line and text below the input field.

General

In this area the title, description and designation can be edited.

Attachments

Attachments (documents, photos and videos) can be attached here.

Data size see info field at the bottom of this page.

Due date

Here you can define whether the due date of the checklist should be adjusted. If yes, it can be defined at the beginning from when the calculation should take place (Created on or Scheduled for). Afterwards, the corresponding days or hours are to be specified.

z. e.g. - 1 day, + 1 day, - 4 hours, + 4 hours

Assign checklist

It can be set to whom the checklist should be assigned. This can be a user or a group.