You can add internal or external event triggers that have
an impact on advanced disposition schedule cutoff of affected entities.
About this task
An internal event trigger is defined by one or more internal entity conditions that, when
met, cause the trigger to be considered active. An external trigger is defined by an externally
managed date occurrence. An authorized user creates internal and external event triggers that are
then used when you define an advanced disposition schedule. You can add recurring event triggers
that have an impact on an advanced disposition schedule vital review of affected entities.For
more information about event triggers, see Event triggers in the IBM Enterprise Records 5.2.1 Knowledge Center.
Procedure
To add an event trigger:
- Select Open Configuration View and
use the following table:
- Select a file plan repository from the Repository menu.
- Select Event Triggers from the Configuration menu.
| Option |
Description |
| To add an internal event: |
- Click Add Event Trigger.
- Choose Internal Event Trigger.
- Set the Internal Event Name value. This
value must be unique across all existing event triggers found on the
repository.
- Set an Internal Event Description value.
- Define one or more aggregation entity property conditions that
define the internal event trigger. Each condition consists of an entity
property name, a condition operator, and a condition comparison value.
The menu of available property names is specific to the Aggregation
entity type selected. The menu of available condition operators and
the condition value field are specific to the data type of the chosen
property name. The operator Is Not Empty does
not require any condition value.
- Click Add Property to insert a new condition
entry row.
- When more than 1 condition is defined, select the appropriate
condition join type:
- Match all of the condition criteria (AND)
- Match any of the condition criteria (OR)
|
| To add an external event: |
- Click Add Event Trigger.
- Choose External Event Trigger.
- Set the External Event Name value. This
value must be unique across all existing event triggers found on the
repository.
- Set an External Event Description value.
- Define the External Event Occurrence
Date value. An External Event Trigger is not considered
active until a date value is established and that date value occurs.
|
| To add a recurring event: |
- Click Add Recurring Event Trigger.
- Set the Recurring Event Name value. This
value must be unique across all existing event triggers found on the
repository.
- Set an Recurring Event Description value.
- Enter the Start Date for the first occurrence of the recurring
event. After this date, the event recurs based on the specified frequency.
- Specify the time interval or the frequency in terms of years,
months, and days after which you want the event to recur.
|
- Click Add to save the new event
trigger to the repository.