Periodic assignment
Table of Contents
Periodic assignments
Periodic assignments allow recurring checklists to be assigned automatically. This means that checks that are executed monthly, for example, are automatically assigned to a person.
Managing periodic assignments of a checklist template can be done by clicking on the context menu (the three dots) on the right hand side of a published checklist template and selecting “Periodic assignment“. The user will see all the perodic assignments that are already in place. These can be edited and deleted by a user with the right permissions.
Adding a new perodic assignment
Assigning a checklist periodically to a user or a group can be done by clicking on the orange button in the lower right corner. Creating a new periodic assignment is divided into 4 steps.
General information
In this section the user has to provide a title which gives a quick information on the periodical assignment.
Assignment
This section contains all important information about periodic assignment. Test object type, test object, assigned user or group can be selected. When a test object type is selected, the periodic assignments are also automatically created for the test objects below it. This should be noted if the assignments are only required for specific test objects.
Furthermore, it is possible to set the due date and time by which the checklist should be executed. In the last field the user can choose how many days and at what time before the due date the checklist should be assigned. Execution is thus possible several times a day (morning and evening shift), for example. This also allows assignments on an hourly basis and the checklist only appears at a specific, predefined time.
Repetitions
Here the user can set the frequency of the assignment. There are predefined options (e.g. weekly, monthly,…) but also the opportunity to create a custom frequency.
Expiration
Here an expiration for the periodic assignment can be set. The user can chose the option “never“, define a number of repetitions or can set a date on which it expires.
History
Periodic assignments have a history where all previous steps are displayed. This feature allows to review the successful and failed executions of all periodic assignments. For each execution attempt, a separate entry is created with all relevant information. To ensure transparent troubleshooting, it is also possible to set filters and search for them.
Also shown is when a periodic assignment was activated/deactivated and whether this was done automatically or manually by a person.
The 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:
All important information can be seen at a glance. By using the link icon on the right side, the individual items can be expanded and further details can be displayed.
Export
Periodic assignments can also be exported as an Excel file, in which adjustments can be made and then re-imported to quickly and collectively implement changes.
The export is located under “Manage checklist templates” in the upper right context menu.
The file contains 2 worksheets.
IDs: in this worksheet, changes can be made which will take effect upon re-upload. The IDs of the respective entities can be found in the context menus, see for example with the inspection objects:
Titles: This worksheet contains the fully formulated titles of the individual entities and serves as an overview of the periodic assignments.
No changes can be made here; it is purely a report of the current state of the periodic assignments of all checklist templates.
Breakdown of the columns
Worksheet 1: IDs
Column | Description |
|---|
Column | Description |
|---|---|
Id | ID of the periodic assignment itself |
ChecklistId | ID of the checklist template |
Title_de-AT | Title of the checklist template in the language set in the user settings |
TestObjectTypeIds | If the periodic assignment is executed on a test object type: ID of the respective test object type |
TestObjectIds | If the periodic assignment is executed on a test object: ID of the respective test object |
AssignedToId | ID of the group or person to whom the checklist should be periodically assigned |
FirstDueDate (UTC) | First due date time Format: e.g. 02.12.2024 22:00 |
AssignDaysBefore | Number of days counted back from the due date when the checklist should be assigned. Format: e.g. 7 |
AssignTime (UTC) | Time of assignment Format: e.g. 15:00:00 |
Repetition | Setting of the repetition form. Here you can choose from the same modes as can be set in the Testify frontend. Formats:
|
RepetitionSettings | The specific setting of the repetition format chosen in the previous column.
Examples for the different possibilities with “Custom”: “Every 3rd day”: 3;Day |
Expiration | When should the repetition end? You can choose from the following options:
|
ExpirationSettings | The specific setting of the expiration format chosen in the previous column.
|
IsEnabled | Is the periodic assignment active or inactive?
|
The explanations for the columns “Repetitions” and “End” in the 2nd worksheet “Titles” can also be taken from the table.
Exception Dates
Exception dates let you define specific calendar days when periodic checklist assignments should not be created for a test object. Typical use cases: holidays, maintenance windows, or any day you want to skip automated assignments.
When the periodic assignment background worker runs, it checks if today matches any exception date for a test object. If it does, the assignment is skipped and logged with state Skipped.
The feature is disabled by default. A tenant admin must enable it first:
Go to Administration → Company Settings → Tenant settings
Look for the setting "Enable specifying periodic assignment date exceptions at test objects"
Set it to active
How to Configure Exception Dates
Navigate to Admin > Test Objects
Open the desired test object
A section labeled "Periodic assignment exception days" appears (only visible when the setting is enabled)
Use the calendar picker to select dates:
Click a date to add it as an exception
Click a selected date again to remove it
Past dates cannot be selected (only future dates are allowed)
Selected dates appear as chips below the calendar
Save the test object — exception dates are saved together with the test object
How It Works at Runtime
The periodic assignment background worker runs on schedule
For each test object, it checks if today (in the tenant's timezone, converted to UTC midnight) matches any active exception date
If a match is found → no checklist instance is created, and a log entry with state Skipped is recorded
If no match → assignment proceeds as normal
Import/Export Support
Exception dates can also be managed via Excel/CSV import:
Column name:
PeriodicAssignmentExceptionDatesFormat: Semicolon-separated dates, e.g.
2026-01-15; 2026-02-20; 2026-03-10Supports standard import actions (Add, Replace)