The previous completed task was due on November 26, 2021.The current task has a due date of December 10, 2021.The following is the current state of the recurring task, and decision: Should the December 10 due date be changed?.This change invites different possible options for how the continuation of the series can be defined: The decision might even be that the 3-week cadence should be retroactive for the overdue reports. However, suppose a decision is made that going forward, this report should be done every 3 weeks, rather than every 2 weeks. The today's date isn't used to calculate due dates of recurring tasks, in order to avoid losing track of late work.įor this task, if the recurrence schedule isn't edited, and the December 10 task is marked complete, the next task for the series is instantiated with a due date of December 24. The next instance of a meeting is always in the future, based on today's date. Completing an overdue task can generate another task that is due in the past, but there is no concept of completing a meeting in the past. Meetings don't need to be marked complete in order for an automated system to schedule the next meeting on the calendar. Note: At this point, the contrast between recurring meetings and events becomes apparent. The report and its associated task are now 4 weeks overdue. The current recurring task (and corresponding report) is due on December 10. The person who did the reports took some time off in December, and nobody completed the reports. Fast forward to January 7, 2022, 34 weeks later. The first report is due on that date, Friday, May 14. The report and its associated task are due every 2 weeks on Friday the series started on May 14, 2021. The following example involves a report that must be completed regularly and utilizes a recurring task to track completion of the report. This section describes a real-life scenario for recurring tasks, to illustrate the interesting differences between recurring meetings and recurring tasks, and to explore the problem space of changes to a recurrence pattern. If recurrence was terminated, it should be possible to reinstate the series.Ĭonceptual differences between recurring meetings and recurring tasks Terminating the series without deleting the active task.Deleting the active task in the series (and choosing yes to terminate the series).If the client doesn't know about recurrence and doesn't offer a prompt, the series should continue. If the active task in a series is deleted, the user should be prompted to determine whether they want to continue or terminate the series. Marking a task complete results in the generation of a new task to continue the series, according to the recurrence schedule. Users specify the schedule for recurrence.Įdit the recurrence schedule for an existing recurring series.Ĭontinue a series. The end result for both is the same: a recurring task, the first in a recurring series. Alternately, create a new task with recurrence defined. User scenariosĪdd recurrence behavior to an existing task, thus creating a recurring series. The recurrence property on a Planner task allows users to automate the creation of future tasks that represent real-life tasks that need to be completed repetitively. This article describes how to use recurrence with Planner tasks to automate the creation of repetitive tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |