A scheduled request is a recurring request for data to be uploaded from a specific supplier to a specific data store, on a specific cadence.
A scheduled request must specify the following components:
The datastore that data should be submitted to
The supplier that the request should be assigned to
The schedule that the request should recur on
Each of the above components must already have been created within the gather360 interface before they can be combined to create a scheduled request.
Request schedules are created as a standalone component within gather360. These schedules can be assigned to one or many requests, so if you need data submissions in multiple different datasets at the end of each month it is easy to assign the same schedule to get all of these on the same date.
Schedules contain two key settings - the cadence for requests, and the desired notification schedule. For example, you may have a need for the following three schedules which all have different configurations:
Schedule 1 requests data every week on a Monday at 9am, and sends 2 advance reminders and 1 overdue reminder.
Schedule 2 requests data every week on a Monday at 9am, and sends 0 advance reminders and 2 overdue reminders.
Schedule 3 requests data the first week of every month on a Monday at 9am, and sends 2 advance reminders and 1 overdue reminder.
You can create any number of different schedules within the gather360 interface. To create a schedule, just visit the 'Requests' page and click the orange button 'Manage Request Schedules' in the top right corner to view existing schedules. You can click the orange button '+ New Schedule' on this screen to build your own schedule.
There are three options you can edit for a request notification: HOW OFTEN you want notifications to be sent, WHO receives the notification, and WHEN the notification is sent relative to the schedule due date.
Notifications can either be reminders - which are sent in advance of the due date, or escalations, which are sent after the due date if data has not been submitted.
Reminders are always sent to the 'supplier' of data (the person who you expect to upload the data). You can configure up to 4 advance reminders to the supplier.
Escalations can be sent either to the 'supplier' (the person responsible for uploading the data) or the 'requester' (the person who set up the request). You can configure up to 4 reminders in total.