Custom Triggers Global Triggers Custom Direct Triggers

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

Custom triggers are defined explicitly by a Records Administrator. Custom triggers are more inclusive and less granular than a system-derived trigger based on content state. A custom trigger can affect all eligible content within a given retention category; whereas a system-derived trigger may only affect one content item within a retention category, because it may be the only item in a given state. Three types of custom triggers can be defined: ■ Global triggers, which happen at a time defined by an administrator ■ Custom direct triggers, which use metadata fields as triggering events ■ Custom indirect triggers, which occur on a regular schedule based on audit events The triggers appear in the Triggering Events list of the Disposition Rules screen. For further information, see Chapter 14, Defining Disposition Instructions . Access to creating, editing, and viewing information about triggers can be controlled by security settings. If access control list ACL security is enabled, access to triggers by group and user permissions can be restricted. If default security is used, then the trigger can be assigned to a security group and the filer be designated.

11.1.3 Global Triggers

Global triggers have an activation date. The activation date can be a past, present, or future date. A user can create a trigger and delay the activation of a trigger for an indefinite amount of time until activation is required. In essence this is a dormant trigger, which does not contain an activation date. A user can create a trigger that activates immediately, activate a trigger on a certain date and time, or delay the activation of a trigger for an indefinite amount of time until activation is required.

11.1.4 Custom Direct Triggers

Use custom direct triggers to create customized trigger functionality in addition to the global triggers built into the product and operating behind the scenes. Custom direct triggers are system-derived triggers based on a content state, on content, or record folder date fields only. These triggers are not global triggers. They 11-4 Oracle Fusion Middleware Setup Guide for Universal Records Management only affect an item meeting a given state. Unlike regular global or event indirect triggers, an activation date is not set explicitly for the custom direct trigger and it is not enabled. When created, the custom direct trigger is always active and ready to be used. Custom direct triggers can be created with a date field, folder date field, or both. There is no logical AND relationship between the content and folder date fields. There is a logical AND relationship between content fields or between folder fields if more than one field is specified. The fields are used to activate the trigger for content and the folder fields are used to activate the trigger for folders.

11.1.5 Indirect Triggers