Workflow-Automation

By continuing to use the website, you consent to the use of cookies for functional and statistical purposes.

Info

Easy Workflow-Automation

The Allegra Workflow Engine is nearly infinitely flexible in automating standard workflows. In this way, you can accurately map your processes as a state machine, control external components such as ERP, CRM or test systems, or react to external control. You can implement a lot without programming knowledge in the graphical workflow editor. If it gets complicated, you can do practically anything with the help of Groovy scripts. [Nbsp]

The Allegra Workflow Engine is nearly infinitely flexible in automating standard workflows. In this way, you can accurately map your processes as a state machine, control external components such as ERP, CRM or test systems, or react to external control. You can implement a lot without programming knowledge in the graphical workflow editor. If it gets complicated, you can do practically anything with the help of Groovy scripts. [Nbsp]

The Allegra Workflow Engine is nearly infinitely flexible in automating standard workflows. In this way, you can accurately map your processes as a state machine, control external components such as ERP, CRM or test systems, or react to external control. You can implement a lot without programming knowledge in the graphical workflow editor. If it gets complicated, you can do practically anything with the help of Groovy scripts. [Nbsp]

Trigger and escalations

The Allegra workflow engine supports you with automatic triggers and escalations. So you can easily map service level agreements and never let your customers wait for an answer.

Guards

With Guards you can control who is allowed to do something in the workflow. For example, you can map an approval process or check whether conditions in and out of the system have been complied with prior to a change of state. Standard guards are the roles and attribute values ​​that can be checked. More complex conditions can be realized with Groovy scripts.

Actions

With each state transition, you can perform actions. For example, you can change the responsible engineer, send an e-mail, block the process against editing, or pass   data to an external system.

Many actions are already built in and can be easily selected. If that's not enough, you can run scripts and do practically anything that's imaginable.