Event activation buttons

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

Let us know what you're looking for

Do you prefer to ask us directly?

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

or use this contacts

Event activation buttons

From a task, you can activate an event using a button. The button will be offered to the user in the task detail if the condition for the occurrence of the event is User Button. Depending on the type of condition, the option will affect how the task behaves.

Every Event Activation

User Button

The user will be offered a button with the name entered in the Button field and the interim event generation icon. If specified, the help will be displayed when the mouse hovers on the button.

The user will generate this event by pressing the button and the task will continue; its status is unchanged. The object state attribute from this setting is irrelevant to this option (it is not reflected anywhere in the system behavior).

End User Button

As in the previous case, the button will be offered with help, if applicable. The icon will indicate the end event.
After the user invokes the event, the event itself is activated, but the object state is also changed to the state specified in the Object state. The specified state should be the end state (Completed, Cancelled).

What to use the event-related buttons for

The definition of the event together with the button creates the possibility to control the processing of follow-up steps directly from the task. By terminating a specific action instead of the "normal" end of the task, the user can directly activate the follow-up task.

Example (end event): The manager receives a draft document from the employee for approval. The task can be terminated with the accept or reject buttons, and depending on the option, another follow-up step is activated. In addition, the worker's decision given by the button option is archived as an event for the task.

Example (running event): Within the task that the worker receives based on the pattern, there will be an option to "report a problem" (escalation). With this button, the worker can start solving the task at the level of his or her manager. At the same time, however, the task remains open and active for him or her to process. The manager will be given a new task on the basis of which he or she can engage in solving the problem or otherwise react.