Highlights implemented features

Fiscal year 2022/23 (04/22-03/23)

Preview

New features

Calculation with previous test results

Calculation checks offer especially much flexibility and freedom when creating checks. In addition to multiple input values, predefined as well as custom formulas can be used, which are observed based on the mathematical rules. By referencing previously entered check results, calculations can be represented in an even more fine-grained way. Use Case / Example:

• Deviations of different measurement results (e.g. two thermometers)

• Percentage deviation from the average of the samples

A detailed feature description can be found in the release notes at Release v4.54.0 as well as at Calculations (Advanced)

Check categories and check collections

Check categories enable the thematic grouping of checks. Within the checklist template, these can be stored for relevant checks. This allows check results from several checklists to be displayed in one protocol. This is possible as follows:

Check collections can be created for each test object. These can each consist of one or more check category(ies). The restriction to individual checklist templates is also possible. In this way, meaningful PDF protocols can be created. These protocols show an overview of all recent check results per check collection.

The feature is particularly useful as current processes and checklist structures can be rethought and combined protocols can be created. Use case/example:

• Rethinking processes: for example, audits can be executed area-based instead of the classic standard-based checklists. There is one check category per standard (e.g. IFS7). The audit is executed per audit area, and one or more check category(ies) can be stored per check. This allows a complete focus on one area during the audit. It is particularly efficient and useful as several checks of different standards within one area are carried out one after the other and recurring questions are avoided.

• In the case of long processes, it may be useful to map them within one checklist, even though multiple PDF protocols are required. By adding check categories, it is possible to create different PDF protocols based on the check collections after checklist completion. Example: electrical protocol, assembly protocol, etc.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2404810802 and Release v4.71.0 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/2412871731 and https://testify.atlassian.net/wiki/spaces/TWN/pages/1507229902.

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 https://testify.atlassian.net/wiki/spaces/TWN/pages/2450096129 and at https://testify.atlassian.net/wiki/spaces/TWN/pages/1522434125.

Key users can enable this feature through the Testify Customer Success Team.

Scan JSON DataMatrix in text check

A simplification when running text checks is provided by scanning JSON codes. This extracts the relevant values and displays them as the check result. Use Case / Example:

• Batch number scanning

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2362376193 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752592.

Feature highlights

Assign multiple checklists at the same time

A checklist can be assigned to multiple persons and test objects at the same time. The Bundle and Execute feature has been further optimized for this purpose. Thanks to the flexible setting options, multiple assignment of checklists is easily possible. The following variants are currently offered:

Starting checklists with different test objects

• Always start new checklists: When executing checklists by "Bundle and execute", a new checklist is always started automatically.

• Continue existing checklists, if possible: When executing checklists by "Bundle and execute", existing checklists will be continued, if available. Both open and closed checklists can be used within this option.

Instantiation of checklists with different test objects (types) and different users

• Assign checklists: This allows a checklist to be assigned to multiple test objects to multiple people. Additionally, test object types can be selected to instantiate a checklist for all underlying test objects. Likewise, a due date and time can be selected.

Use Case/Example:

• Five checklists from the same checklist template are assigned to five different people and test objects.

Key users can activate this feature through the Testify Customer Success Team.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2387738625 and Release v4.71.0 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/2051670141.

Assignment of custom fields to the user

Custom fields can be used to store additional information. This offers more flexibility for test objects as well as issues and from now on also for users. Use Case / Example:

• Department number

• Personnel number

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2354905198 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1507164378.

Excel import of entities

To simplify the creation of data in Testify, there is the option to import/export it via Excel. This is especially useful when a large amount of data is new or needs to be updated. The following extensions offer an even broader range of possibilities:

• Updating groups provides an easy way to keep group information always up to date.

• User management is simplified by adding test object and test object type restrictions to users.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TB/pages/2354905184 and https://testify.atlassian.net/wiki/spaces/TWN/pages/2362376193 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1507229936.

Extensions for Excel import of checklists

Checklists can also be created and edited via Excel. Users can thus decide at will whether they want to create and edit checklists in the system or via Excel. In order to respond even more flexibly to requirements and needs, the Excel template has been further optimized as follows:

• Detailed description as a note in the columns

• Optimization of the design

• Link to the detailed feature description

Use Case / Example:

• Particularly long checklists

• Checklist already existing in Excel format

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2394259478 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/2386624530.

External sensor data as check results in checklists

Testify enables the automatic transfer of external sensor data into checks. For this purpose, the necessary equipment can be stored for a check and the measured values can be automatically stored as check results when checklists are executed. This provides correct and clean data even more efficiently. Use Case / Example:

• Measured values of a thermometer for temperature checks

• Weight checks by scales

• Torque checks of all screws

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2423160833 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1564114969.

Multi-Language in analyses

For German-speaking users, reporting is displayed in German by default, while all other users see it in English. This bilingualism provides an even better and individualized user experience.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2365620238 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197278.

Share filters in the analyses

In order to let other users even better participate in the analyses, there is now the possibility to create shareable links within the analyses. All previously set filters are taken into account for the links. This makes it possible to define exactly which information should be displayed in the dashboard based on the previously set filters. This enables an even better exchange within the company.

In addition to this, external tools can link to an embedded reporting in Testify and set filters for this report. For this purpose, we support setting filters directly from the URL.

Use Case / Example:

• Internal sharing of specific information

• Filtered dashboards for management

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2391441425 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197278.

Mandatory issues for negative checks

For each checklist template, you can define whether an issue must be created for negative checks. This enables an even more precise mapping of your company processes and internal specifications.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2496987137 as well as at https://testify.atlassian.net/wiki/spaces/TWN/pages/1538752602.

Workflows

Workflows enable the automation of work processes within Testify by allowing predefined actions to trigger specific events. The application possibilities have become even more diverse thanks to the following enhancements:

• Delay: By delaying workflows, actions can be triggered later.

• Area Notification: Define notifications for checklists, issues, test objects, users and timers to better customize requirements. This is possible thanks to the flexible setting option of language, message, recipient as well as notification type.

• Event Timer: With the workflow time trigger, tasks can be scheduled periodically based on minutes, hours, days, weeks or months. The event timer can be used on all current actions (checklists, issue, webhook, PDF, notification).

• “Reopen checklist" action: The Open checklists action can be used to automatically assign checklists to predefined persons or groups after completion. This enables an automated collective processing of a checklist.

• Action “Calendar Entry”: Calendar invitations can be created for checklists and issues. This allows tasks that arise in Testify to be integrated into calendars.

A detailed feature description can be found in the release notes at https://testify.atlassian.net/wiki/spaces/TWN/pages/2369028097, https://testify.atlassian.net/wiki/spaces/TWN/pages/2379907073, https://testify.atlassian.net/wiki/spaces/TWN/pages/2411167759 and https://testify.atlassian.net/wiki/spaces/TWN/pages/2496987137 as well as at Workflows and https://testify.atlassian.net/wiki/spaces/TWN/pages/2376990727.