2023/24

Owned by Testify
Last updated: Feb 14, 2024
5 min read

Highlights implemented features

Fiscal year 2023/24 (04/23-03/24)

Preview

New features

Action block: Assign

The "Assign" action block makes checklist execution even more dynamic and interdisciplinary. This new feature allows assigning a checklist to a previously defined user and due date. This button can be at the end of a page, section or check. This way, multiple users or members of a group can work on a checklist together in a predefined flow. Before doing so, it is necessary to define in the checklist template design, to whom the checklist should be assigned (user or group) and if this will change the due date.
Use Case/Example:

  • A checklist is to be processed consecutively by various departments. As soon as department A is finished, the button for assigning to the next group appears. Department B also completes the relevant tasks and assigns the checklist to department C. Finally, the checklist comes back to department A for checking.

A detailed feature description can be found in the release notes at Release v4.84.0 as well as at Checklist structure, Checklist and check settings and Execute checklist.

Automatic translation of checklist templates

The automatic translation makes it possible to translate checklist templates into all Testify standard languages at the touch of a button. The automatic translation can be started with a simple button. This method is particularly time-efficient and useful for multilingual companies.

image-20240131-135504.png

This function is not included in the standard version. Key users can obtain further information on activating this function from the Solution Team.

A detailed feature description can be found in the release notes at Release v4.94.0 and at Translating a checklist template.

Bulk actions: Bulk assignment

The new "Bulk assignment" function makes it possible to assign several checklists at the same time. In contrast to "Bundle and execute", several test objects and checklists can be selected and it can be precisely defined to whom the individual checklists are to be assigned. Different test objects, checklists, users/groups and different due dates can be selected. This allows a comprehensive process chain to be mapped and different checklists to be assigned within a very short time. Use case/example:

  • A production order (test object type) contains several items (test object). Different checklists are required for all items, which are carried out by different people.

The "Bulk assignment" function can be called up via the "Bulk actions" tab and is not included in the standard . Key users can obtain further information on activating this feature from the Solution Team.

A detailed feature description can be found in the release notes at Release v4.92.0 and at https://testify.atlassian.net/wiki/spaces/TWN/pages/2654928897

Dependencies (dynamic checklists)

Complex workflows with many dependencies and nestings can be mapped using the "Dependencies" feature in Testify. Based on sections, one check or several checks can be defined, which is/are decisive for whether the section is opened or not. The following dependencies are currently possible:

  • Check is positive

  • Check is negative

  • Check was executed

  • Check was not executed

Use Case/Example:

  • Check "Sensory evaluation successful? (Yes = Positive, No = Negative)"

    • Check in case of positive result: "Laboratory analysis".

    • Check for negative result: "Packaging integrity".

  • Check: "Perform temperature measurement with thermometer 1." (Positive: 70-72 degrees)

    • Result positive: "Perform temperature measurement with thermometer 2 for cross check." (Positive: 70-72 degrees)

    • Result negative: "Perform temperature measurement with thermometer 1 again." (Positive: 70-72 degrees)

      • If positive: "Perform temperature measurement with thermometer 2 for cross-check." (Positive: 70-72 degrees)

      • If negative: "Contact shift supervisor."

Subsequently, the feature will be further extended so that multiple dependencies can be mapped.

A detailed description of the feature can be found in the release notes at Release v4.79.0 and at Checklist and check settings and Dependencies (Dynamic Checklists).

New check type: Geoposition

The new "Geoposition" check type provides more insight into your location. This allows the exact location to be retrieved in real time and specified in coordinates. Alternatively, this can also be selected or entered in the map. Use Case/Example:

  • Search and find all assets in the area

  • Detailed recording of locations

A detailed description of the featurecan be found in the release notes at Release v4.77.0 and at Check types.

New check type: Signature

The new check type "Signature" allows adding signatures within the checklist. This allows to add any number of signatures exactly where it is needed. Use Case/Example:

  • Signature after a specific check or at the end of a page or section.

A detailed feature description can be found in the release notes at Release v4.81.0 and at Check types

Push notifications

Thanks to push notifications in the Testify app, messages can be received with minimal delay. In addition to the familiar notifications within the app as well as via email, this is a valuable extension for seamless information sharing and task distribution.

The advantage is that the app does not have to be open to receive the push notifications. It is sufficient if the user is logged into the Testify app. When using the multi-tenant capability, users will receive notifications from that tenant they currently have open in the app. Use Case/Example:

  • Notification that a new checklist has been assigned to the user

  • Notification that an issue has been verified on a test object subscribed to by the user

  • Notification that the user has to approve a checklist template

A detailed feature description can be found in the release notes at Release v4.77.0 and at Notifications.

Feature highlights

Custom fields for checklists

Custom fields can now be stored in checklist templates. This makes it possible to display additional information on the checklist when instantiating checklists. Use case/example:

  • Adding milestones to checklists as part of a production process (e.g. manufacture of a machine). Initially, 20 checklists are assigned simultaneously; each checklist is assigned a different milestone.

  • Add essential additional information such as batch number or production order number.

A detailed feature description can be found in the release notes at Release v4.94.0 and at Execute checklist, https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752602 and https://testify.atlassian.net/wiki/spaces/TWN/pages/1577287695.

Save GPS position in custom field

The new data type "GPS Position" allows to store even more detailed information about test objects and issues. With the help of these custom fields exact coordinates can be added. Use Case/Example:

  • Detailed recording of locations

A detailed feature description can be found in the Release Notes at Release v4.77.0 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1507229975.

Workflow action: Test result as custom fields of the test object

The new workflow action can be used to save test results in a custom fields of a test object. It is possible to define exactly which check type should be used for which custom fields. It is important that the type of the custom fields and the Check match (e.g. numeric and numeric). Use case/examples:

  • Accept measured values such as pH value or temperature checks.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2693627938 and at https://testify.atlassian.net/wiki/spaces/TWN/pages/1606615347 and https://testify.atlassian.net/wiki/spaces/TWN/pages/2376990727 .