Introduction to examples

The document describes examples of event rule configuration for event processing automations for the system. Details of the general event configuration are described in the 'howto' documentation in the documentation portal.

The document describes the mechanism of events and defining system reactions based on information about changes in object states. Sometimes there is a need to automatically notify system users (or other people) in response to such actions. This is what the event mechanism is for. It allows you to define a number of rules that will be processed by the server and, based on the defined parameters, will generate appropriate actions. Such actions may include, for example, sending an email with specific content to a selected list of people.

The AMAGE system has a built-in set of predefined tasks that, if a configuration is prepared for them, can be run periodically. This article describes their operation and configuration. Scheduler internally uses the Quartz library and CRON-style scheduling. This article gives specific examples of scheduling for specific tasks, but without explaining how the fields are written and what they mean.

The document describes how to configure the system through automatic functions (scheduler). In this example, we analyze the possibility of receiving reports to an email box with a specified period of time. In order for there to be the possibility of receiving a report to an email inbox, you need to do two things. Define a report tab, which will store information about the configuration of a given report, i.e. how to generate a report and from what data. Then such a bookmark is enabled to automatically generate a report at a certain time and send it to selected email addresses. All these steps are described in this document.