Task expiration

Task expiration addresses the following two problems that you might experience:

• Tasks become irrelevant after a period of time, and you know those tasks are not going to be completed
• Events linger with incomplete tasks, and you want the events to complete

Task expiration is a great way to clean up events. When you expire a task, it functions like it is completed—child tasks become active (even though no one acted on them) and events complete.

Key info

• Tasks can be expired in two ways:

  Method	Description	More info
  Automatic (Scheduled)	A task can be set up to expire based on the number of days from an event's creation, activation, due, or termination date. An administrator sets this up on the Manage Task Definitions page.	If the task was expired through the nightly job, the assignee is not modified and Completed By is set to the assignee at the time of the status change If the task is an unclaimed team task, the assignee remains blank
  Manual	A permissioned user can click the Expire Task button to expire the task manually (on demand).	The assignee is not modified Completed By is set to the user who clicked the Expire Task button The system treats the task as a completed task All child tasks activate as long as their activation date settings are met

• When a task expires, completion date is set to the date the task was expired, status becomes Expired, and a system note (audit note) is created.
• A task that requires a document upload for a benefiter cannot be expired.

Good to know

• An expired task equates to a completed task, allowing dependent tasks to be activated if the parent expires.
• An expired task can be reopened/unexpired like a completed task. After that, the task cannot automatically expire again. It can be completed, deleted, or manually expired.
• Expired tasks are tracked on these reports: Assignee Promptness and Task Promptness.
• Event status is set to Completed if all tasks are completed or expired.