Triggers enable you customize the system, reacting to system events and performing any number of tasks such as emailing, suspending users, blocking IP addresses, executing commands etc.
When a user or the system performs an action it generates an event with all the information about the action. These events can be captured by a Trigger and filtered based on the event state or any conditions that you apply to the Trigger. If the event state and conditions pass the tasks you attach to the Trigger are executed.
The Triggers Table
Your tasks will run if all the conditions match the event attributes. The first condition is "Triggers On" which determines the state of the event. Events are either successful or have failed. You can select either of these states or disregard the state choosing the Any Status value.
A Warning status also exists for Alert based events, Alerts are custom events that are fired by the Generate Alert task. Alerts are the only events that generate a Warning status.
You can also define a set of conditions to evaluate the events attributes. All of the attributes an event defines are available, these vary according to the event type. You can set up a set of conditions that should all match (AND) and also a set of conditions where any can match (OR).
Types of Events
The types of events depend on the Hypersocket product you are using, however there are a common set of events shared by all of the Hypersocket Products. Please visit the following article to see the available events.
There are a number of Tasks available, again depending upon your Hypersocket product and the license you have purchased. Please visit the following article to see the available Tasks.
With each trigger its possible to build up a flow of tasks. Every task that is executed generates an output event so the flow is build up by attaching a further trigger to the result of the previous task.
If you select a trigger in the table you will see a flow diagram presented below the table like the figure below. Clicking on the + icon will allow you to build a child trigger that is based on the output event of that triggers task.
The colours in the flow denote the state of the event which triggers the task. In the example below a successful product event triggers a validation task, and if the validation task fails it triggers a notification task.
The following articles walk you through some common types of Triggers that you may want to set up in your system.