When you are initiating a disposition schedule, there are specific parameters you need to define.
You need to define the following parameters:
Cutoff means closing an entity at the specified interval to end its active use. Before any disposition action can be taken on an entity, the cutoff date for the entity should be reached. In addition to cutoff, you need to specify the cutoffset period, which specifies the period before the actual disposition process begins for an entity. That is, the cutoffset period refers to the time gap between the commencement of cutoff and the launch of the disposition action.
A triggering condition specifies a date or an event to start the disposition process for an entity. A disposition schedule is triggered when a specified calendar date is reached or an associated event occurs. The calendar date metadata provides information about the date from which the cutoffset period is determined. An event specifies a condition to start the cutoff date of an object after the specified condition is fulfilled. You can create various types of events: predefined date, property based, external, and recurring. The following table describes these events:
Event | Description |
---|---|
Predefined Date | Defines an action on a specified date. For this event, you set a value for the DateTime property of the Event class. |
Internal | Defines an event based on the property of an object. When the specified property of an object fulfills the condition, the cutoff period starts for the entity. You can specify the property-based condition by setting the Aggregation, Metadata, Metadata Value, and Operator properties of the Event class. |
External | Defines an event that occurs outside the system and that might directly impact the cutoff and disposition of entities. |
Recurring | Defines an event that repeats after a specific time interval. To specify a cyclic event, you need to set the DateTime, Cycle Days, Cycle Months, and Cycle Years properties of the Event class. |
Cutoff Date = Event Date + cutoffset Period
In this expression, Event Date refers to the date obtained from a predefined date, a recurring event, or an external event. However, for internal events, Event Date refers to the system date when the condition specified in the event is fulfilled.
A phase enables you to define a step-wise execution of the disposition schedule. Each phase specifies a disposal action and retention period for an entity. Associating phases with a disposition schedule allows you to perform different operations on an object at different intervals. For example, you might want to review an entity before it is destroyed. To do so, you should assign two phases with the disposition schedule. The first phase specifies that the entity should be reviewed, while the second phase specifies that the entity should be destroyed. While adding multiple phases to a disposition schedule, the retention period of the next phase should be more than the retention period of the existing phase. For example, if the retention period of an existing phase is one year and seven months, the next phase must have a retention period that is more than one year and seven months. For more information on how to create a phase, refer to Creating a Phase object.