Schedules are used to automate the creation of submissions and the sending of submission request emails.
Schedules are created and managed by Org Admins and can be applied to multiple feeds by the feed owner. When a schedule is applied to a feed, new submissions will be created according to the frequency set in the schedule. Data request emails will be sent to the users listed in the default submitters popup.
Schedules can contain a deadline, allowing a submission to be marked as overdue.
Aspects of schedules such as overdue status, period start date, etc can be written to a pipeline via the Append Metadata operation.
Schedules are created and edited by Org Admins in the Admin tab. Any edits made to a schedule will be applied to all feeds using that schedule.
To create a schedule, navigate to the Admin tab:
To use a schedule in a feed, first set the list of submitters:
Next select the schedule:
Schedules can be paused to temporarily stop the creation of submissions and their associated notifications. Only feed owners can pause a schedule.
When a document is duplicated or archived its schedule is paused.
Parameter |
Description |
Name |
Name the schedule to allow it to be identified in feeds |
Publish |
When toggled ON the schedule is made available to the whole organisation and can be used in feeds.
When toggled OFF the schedule is in draft form and can only be accessed via the Admin panel |
Frequency |
Set the frequency of requests, e.g. monthly every 1 month, weekly every 2 weeks. |
Submission naming |
Create a naming convention for submissions utilising date components, separators and custom text,
e.g. ‘yyyy-mm’ |
Requests |
Set the time of day the request is issued. The date of first request will be set in the feed. |
Deadline |
Set the deadline for submission to a time after the request. |
Reminders |
If a deadline has been set, define when reminder emails are sent, both before and after the deadline.
If the submission is complete, no reminders will be sent. |
Example |
An example of the submission naming |