About Triggers and Actions

Communication between components (including components rendered in inline frames) can be configured so a trigger within a component calls an action on another component.

Triggers are part of Oracle Content Management intercomponent communication. Any component can raise any number of triggers. The component can provide a payload for a trigger, which then is passed to any action that is executed when the trigger is raised. You can select what actions will be executed for each trigger. Components that are built to work together can automatically raise triggers to execute actions on the other component without user interaction.

The basic process involves:

1. Registering triggers

2. Raising triggers

3. Registering actions

4. Executing actions to verify the setup

For example, you can use the Button component to perform one or more actions such as showing or hiding page components and showing messages. You could have a list of business office locations in one component and when a location in the list is clicked, then details about the location are displayed in another component.

For components you customize, the triggers and actions are part of the component registration data and not part of the component implementation. In the registration data there is a "triggers": [], and "actions":[], entry that contains the list of triggers and actions the component supports. The actual syntax is the same as for local and remote components, only the location and how it's retrieved is different.

See Use Triggers and Actions in Building Sites with Oracle Content Management.