...
Under "Administration" in the workflow section the user can automate his Testify environment. Certain Specific events can be defined which that trigger actions when they take place. Workflows can be activated and deactivated, deactivated, overwritten, but not deleted.
...
Add a new Workflow
When adding a new workflow, the user must define a title. The title should be meaningful, so that one can already recognize in the menu, which task the workflow fulfills. After defining a meaningful title, the triggering event and subsequent action must be defined. If necessary, multiple triggering events and actions can be added.
| Info |
|---|
Each event, each action and the entire workflow must be saved separately. |
Events
In the “Events” section steps must be defined that must be fulfilled in order to trigger the action. When creating events the following informations have to be specified:
...
| Info |
|---|
The filter before change is only applied if the property has actually changed. If the property is the same before and after the event, the workflow is not executed because the filter does not apply. Example of a workflow not working:
Workflow for modified changed checklists that restrict to with the one checklist template when filter before change on a checklist template. Since . → Since the checklist template will not change, the workflow will never be triggered. Users might think that they are triggering every checklist change as an event. However, since the checklist template will not change, the workflow will never not be triggered. Corrected example:
|
Actions
When creating actions the following informations have to be specified:
...
Based on events within Testify, webhooks can also be added independently as actions in workflow management. This is possible by selecting the scope "Webhook" with the type "trigger". An URL is has to be specified as parameter, optionally an identifier can be entered:
...
The generation of PDF protocols can now be automated as an action via a workflow. This process automation is to start the generation of PDFs for the filtered checklists. Filters can be set based on the events to define exactly for which check test objects or checklists , for example, the automated PDF generation should take place.
...
Workflows have a history where all previous steps are displayed. This feature allows to check the successful and failed executions of all workflows. For each execution attempt, a separate entry is created with all relevant information. To Filters can be set to ensure transparent troubleshooting, it is also possible to set filters and search for them.
It also shows when a workflow was activated/deactivated and whether this was done automatically or manually by a person.
The workflow history can be viewed by clicking on the context menu (the three dots ) in the upper right corner).
...
By selecting the desired entry, the history is displayed:
...
Event:
When a new test object gets added by “Testify Admin“ to “Airport Frankfurt” then the action will be carried outis added from "Testify Admin" to "Frankfurt Airport", the action is executed.
Action:
A “New Item - Airport Frankfurt“ checklist gets is created by "Testify Admin" for the added test object by “Testify Admin”, assigned to “Engineering”, “Due date (+days since event): 7; Time of day: 12:00pm”which is assigned to the user "Testify Admin" and due in 7 days at 12:30.
2) Initiation of a checklist when an issue was created
...
Event:
When a new issue with the category “Logistic error“ gets added to “Airport Frankfurt” then the action will be carried out"Logistical Error" is added to "Frankfurt Airport", the action is executed.
Action:
A “Logistic "Logistic Issue - Checklist“ Checklist" checklist gets is created by "Testify Admin" for the test object where the error occured by “Testify Admin”issue occurred, assigned to “Engineering”, “Due date (+days since event): 3; Time of day: 12:00pm”.the "Engineering" area and due in 3 days at 12:01
3) Initiation of a sequence of related checklists
...