Business event

User Modules

Task, project & quality management
Contacts and directories module (CRM)
Web management and automation
Human resources
Products, assets and sales
Finance management
Metrics and Measurements

Technical Modules

Sabre plugin module
Enterprise Architect connector

System Modules

The AyMINE Framework Module
System Management

Give us contact

Do you prefer to ask us directly?

Call us +420 605 203 938 (the Czech Republic)

or use this contacts

Business event

An event in the system indicates that a specific event has occurred in the real world. Examples of events are:

  • beginning of the month,
  • a request from the tax office,
  • employee onboarding.

The event object describes events to which the system can respond in some way. Events can occur repeatedly, each time there is an event occurrence (it is recorded separately in the system).
An event activation means that the conditions for an event occur, the system creates a new occurrence, and triggers the actions that are tied to the occurrence.

When events occur

Events occur in one of the following cases:

  • Time-based events, e.g., the beginning of a day, month, or year.
  • Object change events occur when a given change occurs – an object is created, removed, or its state changes. (e.g., a task is completed)
  • Hand-triggered events represent an event that the system itself does not/cannot recognize, but there are processes in the system that are supposed to respond to the event. An example of such an event is a Request for Information from the tax office, a natural event, etc.

Activating an event manually gives the ability to trigger the processes that should be used to respond to the event. The worker who activates the event does not need to know how the system should respond to the event, only that the event needs to be activated.

Relationship of the event to the object

An event, if it occurs as a result of a change in the state of an object, shall be related to the controlling object. However, it does not have to be related to the object whose changes are actually being monitored. For example, for task-driven events, the occurrence of the event is governed by the occurrence or change of state of the task, but the event definition is related to the task definition. Therefore, the event needs to be reassigned to the task definition and the system itself will ensure that the occurrence of the event is governed by the change of state of the task that was created based on this pattern.

Event Category

AyMINE distinguishes between 2 categories

  • System events are defined by the system. Users can use them, but they can neither be activated nor changed
  • User events are more interesting because they describe events in the business/life of the user. These can be freely managed and manually activated.

Event generation limits

If an event has set dates from when and/or until when it can be triggered, it is never triggered outside these limits, regardless of whether the event that should trigger it has occurred.

Regular event generation

System events are generated periodically according to their definition. User-generated events cannot be set this way. If an action needs to be triggered periodically, it needs to be linked to one of the system events.

Manual event activation

An event can be manually activated by personnel who hold one of the roles assigned to the event. (There can be more than one role.) Workers can see the events available for activation in the list of events to activate in the system home page menu. Events activated in this way are always unbound to any object, so it is not possible, for example, to activate an event bound to a task.

Events with a link to an object can only be activated through the object, typically by changing its state (e.g. completion). Exceptionally, an object may have an operation that leads directly to the generation of an event.