Retention Period Cutoff Preceding Disposition Action Content or Folder States

11-2 Oracle Fusion Middleware Setup Guide for Universal Records Management ■ Admin.Triggers : In addition to viewing information about triggers, this right also enables a user to create add, edit, and delete triggers. Security groups can be used to block access to triggers. For example, if you do not want users with the Admin.Triggers right to be able to edit and delete triggers, you can use security groups to restrict access to these functions. Only users with access privileges to the security group assigned to a trigger can edit and delete the trigger. This section covers the following topics: ■ System-Derived Triggering on page 11-2 ■ Custom Triggers on page 11-3

11.1.1 System-Derived Triggering

System-derived triggering uses the following built-in events or actions: ■ Retention period cutoff ■ Preceding disposition action ■ Different content states

11.1.1.1 Retention Period Cutoff

Retention period cutoff causes a cutoff action to occur at the end of the time unit specified in the retention period. After cutoff, the content item is retained for the retention period specified in the disposition rule. For instance, when retention period cutoff is used as a triggering event and a retention period of three calendar years is specified, the cutoff takes place at the end of the current year and the affected content is retained for three years after the end-of-year cutoff. Retention periods for triggers can only be specified if the AllowRetentionPeriodWithCutoff flag is enabled. This is enabled by default. In previous versions of this product, a negative retention schedule could be supplied for a preceding action. This has now been changed so negative retention periods are available only if the following variables are enabled in the records_management_ environments.cfg file: ■ AllowRetentionPeriodWithoutCutoff=1 . When this is enabled, retention periods are allowed with other triggering events in addition to the default ones of Cutoff and Preceding Action. dDispPeriod:allowSignedInteger=1 dDerivedMonthDelay:allowSignedInteger=1 dDerivedDayDelay:allowSignedInteger=1 ■ When these are enabled, a negative retention period can be supplied for any trigger except for Cutoff and Preceding Action. For example: Triggering Event = Contract Ended Retention Period = -1 month Disposition Action = Notify Authors Triggering Event = Preceding Action Retention Period = 3 months Disposition Action = Archive Setting up Triggers 11-3

11.1.1.2 Preceding Disposition Action

When a preceding action in a disposition instruction sequence completes processing, the next subsequent rule begins. The system tracks when a preceding action completes, and automatically triggers the next step in a disposition sequence.

11.1.1.3 Content or Folder States

System-derived global triggers based on an item or folder state can be affected by an implicit or explicit change in an item or a record folder. An example of an implicit change is when an item has an activation date set in the future. The system is aware of the future activation date and it activates the item at the indicated date. Oracle URM automatically changes the state of the item to active. The Records Administrator does not have to perform any explicit action other than indicating the future activation date. An example of an explicit change in state is when an administrator manually cancels or expires a specific item. When content assumes another trigger-dependent state, the associated disposition rule operates on the item.

11.1.2 Custom Triggers