...
Add a new Workflow
When adding a new Workflow workflow, the user has to must define a title. The title should be meaningful, so that you one can already see recognize in the menu, which task the workflow fulfilsfulfills. After defining a descriptive meaningful title, the triggering event and the subsequent action afterwards need to must be defined. If necessary there can be , multiple triggering events and actions can be added.
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:
Scope: The scope defines the entity where the event takes place. (
Checklist
Issue
Test object
PDF
User
Type: The type defines the change of the entity. (created / updated)
Created
Updated
Filters/Trigger: Filters can be applied to specifiy the required conditions. Here can be defined that the event is only valid for certain test objects, checklist templates, etc.
Filter: Filters for attributes of the object
Triggers: Defines the field, which has to be changed to a certain value, to trigger the workflow
Filter before change: Filters for attributes of the object before the update (If a property of the affected object has changed, you can filter on the value before the change, i.e. before the event was triggered).
Filter after change: Filters for attributes of the object after the update (This condition must apply at the time of workflow execution).
| 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:
Workflow for modified checklists that restrict to with the filter before change on a checklist template. Since the checklist template will not change, the workflow will never be triggered. |
Actions
When creating actions the following informations have to be specified:
Scope: The scope defines which action should be triggered. (
Checklist
Issue
Webhook
PDF
Type: The type defines the change of the entity.
create
change
trigger
generate
Parameters: Parameters for the triggered action have to must be defined here (such as test objects, checklist templates, etc.). In this section, the values which were already defined in "Filter" above in “Filters” can be easily reused easily by selecting the “Reuse "Reuse field value from event” toggleif available from event" button.
| Info |
|---|
Defining all parameters is mandatory in this section. |
...
Example: Action
...
Webhook
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 to be specified as parameter, optionally an identifier can be entered:
...
Example: Action
...
Generate PDF
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 objects or checklists, for example, the automated PDF generation should take place.
...