Create your entire teams audit workload for the year, in just minutes with Recurring Assignments. Just like you would for a calendar event, you can now create assignments that will automatically re-create themselves based on your set frequency. |
Creating an Assignment
Creating a recurring assignment is the same process as creating a normal one with one difference. As in the image above, you select the Frequency option to 'Recurring'. Recurrence options:
1. Repeats Every - Here you choose the number of the times an assignment recurs within a defined period. You choose a recurrence number and the period.
eg:
Repeats every 1 Month = one assignment per month.
Repeats every 2 Quarter = one assignment per 6 months
Repeats every 3 Weeks = one assignment per 3 weeks
Repeats every 10 Days = one assignment per 10 days
Note - To create an assignment that would repeat "twice a week", you have to use the days option:
Repeats every 4 Days = two assignments every 8 days.
2. Recurrence Day - Here you choose which day the assignment will be created and recur on. This setting is mainly for when you're looking to create a weekly assignment.
For Daily assignments, there is no need for this and just the recurrence number and Start Date are enough.
For Monthly & Yearly assignments, the recurrence Start Date is enough as all future assignments will be made on the same date of the following month or year, respectively.
eg:
Repeats every 3 Weeks on a Monday = one assignment every weeks, to be created on a Monday.
Note - There is no option to select the exact time, as of now all assignments will be created at 00:00hrs as per the set timezone.
3. Range - Here you choose the Start Date and End Date for the assignment.
Start Date - The date which the recurring assignment starts.
End Date - The date which the recurring assignment stops - there will be no more assignments automatically created after this date.
After this is done, please complete the same steps as a normal assignment to finish creating your assignment.
Recurrence Settings
Settings that dictate how your assignment looks and works in the app.
1. Nomenclature - The master/parent assignment, when created will immediately be shown in the UI under the "All Assignments" table. The master assignment will be the only assignment with the exact same name as what you choose when creating the assignment. All recurrences will have a suffix for the date.
eg:
Master - Test Assignment Q1
Child 1 - Test Assignment Q1 - MMDDYYYY
Child 2 - Test Assignment Q1 - MMDDYYYY
Here, MMDDYYYY is the date which this recurrence is created.
Note - This logic applies to both recurring assignments and scheduled assignments.
2. Due Date - The due date for an assignment will move with each recurrence, based on the difference set initially.
eg:
1) Yearly Assignment that is created on Jan 1st.
Master Creation = Jan 1st 2024
1st Recurrence = Jan 1st;
Due Date = Jan 10th
Difference (or Assignment Period) = 9 days.
This 9 days is what will be used to set the future Due Dates.
2nd Creation = Jan 1, 2025
2nd Due Date = Jan 1 + 9 Days = Jan 10th, 2025.
3. Date Range (Ticket Selection) - Similar to the Due Date, the Date Range for ticket selection will also move with each creation based on the initially set range.
eg: Assignment has a date range of "Last 30 Days".
Range for Recurrence #1 = The 30 days before it is created.
Range for Recurrence #2 = The 30 days before it is created
Note - For Recurring Assignments, we do not currently allow the "Custom" date range option. Therefore, you cannot create recurring assignments to pick tickets from the exact same date range.
4. Ticket Selection (Less Tickets) - If there are less tickets for any Agent(s) in any of the recurrences, then the assignment will still be created, but only with available tickets from the other selected Agents.
If there are no tickets at all for any recurrence, no assignment will be made. Effectively, this recurrence will be skipped you will directly see the next one.
4. Stop, Delete & Cloning - To make changes (stop or delete) to all the recurrences to an assignment, you have to do so to the Master assignment. So to stop all future recurrences to an assignment, you must stop the master assignment. Stopping or Deleting a child (any recurrence i.e.), will only result in that single assignment being stopped (and deleted).
a) To stop all future recurrences from being created, you have to stop the master assignment. Then deleting it would remove it from the app (like deleting normal assignments)
b) To stop/delete a recurrence that has already been made, you have to stop that particular assignment.
Note - This logic is the same for scheduled assignments as well.
Cloning works like normal, there will be the same assignment created with a "Duplicate" tag in its name.
For information about Assignments as a whole, please click here.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article