Sitecore Content Hub™ provides a triggers framework that supports the system to be unified with external software or systems through standard communications protocols. It allows stakeholders to be notified through their desired medium when particular (self-defined) events occur within Sitecore Content Hub. The creation and overview of existing triggers take place on the Triggers page:
The Triggers page lists all the existing triggers:
Additionally, Administrator users can find a log of triggered messages on the Log tab. The Detail button allows for retrieving data of a trigger message. The search field at the top of the page empowers administrator users to perform a query on the possibly extensive list.
A trigger is configured through three tabbed sections:
- Name: the name given to a trigger (mandatory).
- Description: allows users to add additional descriptive information.
Objective: the objective of the trigger, selectable from any combination of the three options.
Execution type: the execution type is set when the trigger is created. The type is either In process or In background:
An example of the General section follows.
Rule set: specifies the rules to which an event should be triggered.
Actions: specifies a set of actions that will be executed in response to an event. An action can represent anything from pushing a message to an Azure service bus to invoking external APIs, pushing a message into an internal Queue, or sending an email to third parties.
Actions are stored as entities within Sitecore Content Hub. Users can thus select from an existing list of actions, modify outdated actions, or create new ones:
If the trigger is of the type In process, the following types of actions can be added:
- Pre-commit actions
- Security actions
- Validation actions
- Audit actions
- Post actions
If the trigger is of the type In background, you can add the following type of action:
- Post actions
To add an action, click on the button, which appears under the type of action header.
The supported Action types for new actions, created from the Manage Actions option, are:
- Action script
- API call
- Azure Event Hub
- Azure Service Bus
- M Azure Service Bus
- Print Entity Generation
- Reporting channel
- Start state machine
As mentioned previously, the framework also provides the possibility to create new event types that can be used for historical reporting. The creation of a new event type is initiated by the configuration of a new trigger. Relating a trigger with an action of type Reporting channel will create a new event type found in the event filter results of the Chart component.
Can we improve this article ? Provide feedback