Execute checklist

Table of contents

Checklists are used to check test objects and are filled out like a paper checklist.

Execute checklist

Select Test Object

The test object describes for which object the checklist is carried out. Later the checklist can be found in the checklists of the selected test object. 

Scan Data-Code

Instead of manual selection, the test object can be selected using "Scan data code". A test object that has a bar code/QR code/datamatrix code can be scanned and is automatically selected.

A valid QR code is required to use QR codes in Testify. The test object identifier and the text stored in the QR code must be identical. If this is not the case, a search field appears.

Open

NFC

The NFC functionality also makes it possible to read in NFC tags in order to select the test object. The prerequisite for this is an NFC reader.

Open

Select checklist template

Once you have selected a test object, you can choose the required checklist template. Various checklist templates can be created by quality managers and applied to test objects. For more information on creating checklist templates go to: https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197300

A valid QR code is required to use QR codes in Testify. The identifier required to create the QR code can be found in the URL of the periodic assignments.

Further Options

After selecting the checklist template the following options are displayed:

• Assigned to - The assigned user will find the checklist in his tasks and can execute, reassign and close them, if he has the permissions.

• Due Date - The date and time indicate by when the checklist should be completed. If the date is exceeded, the checklist status is changed and displayed as “Overdue”.

• Assign - If you don't want to execute the checklist immediately you can assign it to the selected user. A checklist instance is created, which can be executed later.

• Run Now - To directly jump in the checklist execution select the button 'RUN NOW'
  
  

Custom fields

If the checklist template has custom fields, further information can be entered when instantiating a checklist.

Permissions

• If the checklist is assigned to a person who does not have the appropriate rights, the error message "This user is restricted and won't have access to the checklist" appears. This is the case when the user is restricted to other than the selected check object or has no permissions to edit checklists.

• New feature: A new tenant setting allows users to see only checklists and issues for which they have authorization. This is especially relevant if users have a test object (type) restriction. This feature is automatically enabled for new tenants (as of July 2022). Other organizations can enable this feature through the Solution Team.

  • If a user's permissions are subsequently changed and the user then has restricted permissions, the error message "This user is restricted and won't have access to the checklist" appears. This is the case if the user is restricted to a test object other than the one selected or does not have permission to edit checklists.

Work through checklist

After starting the checklist, an overview of the checklist title, test object type, test object and checklist description is displayed. The search function is possible via the magnifying glass. This text search in checklists allows you to enter search terms within a checklist in order to get to a desired check, section or page. This is especially helpful for hierarchically structured checklists.

The info icon can be used to call up further information on the checklist as well as the test object.

• checklist information: Title, description, assigned to, due date, attachments

• Test object information: Title, Identifier, Test object type, Description, Custom fields

By filling in checks, a checklist can be processed. It is always immediately visible when a check was performed by which user. Likewise, this as well as past results can be seen via the respective history.

Depending on the https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752592 as well as the https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752602, there may be special features and restrictions. Here you will find an overview of possible settings:

Show previous check results

Previous check results can be displayed for numerical checks and calculations. This is possible across all revisions and can be clicked via the context menu of the respective checks.

Checkidentifier

If a check identifier has been stored for a section or check, the "checkidentifier" field appears in the checklist header. In this field, the checkidentifier can be entered or scanned via QR code or NFC to go directly to the check or section. If the function "Only allow execution via identifier" is selected, the check can only be executed after entering this identifier.

Add comment

Any number of comments can be added to each check to map additional information. In addition to a text, images can also be stored.

Add issue

Issues can be recorded for checks. This is possible by clicking on "Addfirst issue". An issue can be added for negative as well as for positive check results.

After a check has been executed, it can be seen whether an issue has been added to this check before. This issue can either be viewed or copied. This information is only available after execution, regardless of whether the result is positive or negative. The prerequisite is that it is the same check and the checklist has been executed on the same test object.

More information under https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197202

Equipment

For some checks, equipment (types) may be stored that must be used to perform the check. The equipment must be selected before the check is executed. This is possible by clicking in the field or (if available) by scanning a data code. The check can only be executed after the equipment has been selected.

If only one equipment has been stored in the template settings for a check, this will already be preselected during the check. This saves manual selection.

Importing external sensor data

If external sensor data is stored for the equipment, it can be automatically transferred to the check. This is the case when the "Get device data" button is displayed. By clicking on it, the last measurement result is loaded and the check is completed.

Action: Assign

checklists can be assigned to a predefined person or group using the "Assign" action. This button can be at the end of a page, section or check. Beforehand, it is necessary to define in the checklist designer to whom the checklist should be assigned (user or group) and whether this will change the due date.

The assignment via action block is possible regardless of the permissions assigned to the user via the roles. Thus, even users who normally cannot assign a checklist can assign a checklist via the button.

In the execution, the button is simply clicked to start the action.

Colour scheme

The colour scheme changes depending on the status of a check/section/page

• Pages/sections: Green indicates that all checks are positive. Red means that at least one check is negative. Orange means that at least one check is still open. Empty pages/sections are grey.

• Checks: Positive checks are green, negative checks are red and positive checks that have exceeded a limit are yellow.

• Checklists: Completed checklists are light green, verified checklists are dark green.

Close checklist

Close checklist

At the end of a checklist, the checklist can be closed, assigned to someone else, or exited:

• Leave: checklist remains in "in progress" status

• Assign: The checklist can be assigned to another user or group. A new due date can be selected.

• Close: The status of the checklist changes to "Done".

Restrictions to close the checklist

Depending on whether the checklist is restricted by https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752602, various closing limitations like warnings and error messages may appear. Depending on the setting, a warning (Show warning when exiting or closing) or an error message (Show warning when exiting / Show error when closing) or a combination of both will appear. The following warning or error messages are possible:

• checks: checklist must include 100% filled out checks or 100% positive checks.

• Issues: checklist must not contain any open issues

If not all requirements have been met, an overview of all checks that need to be adjusted before completion appears. Clicking on the respective check takes you directly there and allows you to adjust it accordingly so that the restrictions are met. The link is only activated when the device is online, in offline mode there is no link to the check. Example:

Signature

Likewise, a field for signing the checklist may appear:

• Signature: Sign the checklist after completion.

  • Depending on the requirements, the signature can be optional or mandatory.

  • As many signatures as needed can be added via the "Add signature" button.