Automations are scripted extensions to the Verint Community platform that are developed and managed through the Administration area of Verint Community.
What is an automation?
Automations are executed when they are trigged by an external event. Supported trigger types are:
- Scheduled. Scheduled automations define a recurring schedule and are triggered on that schedule by the Verint Community Job Server.
- API Events. Automations that subscribe to one or more API events are triggered whenever the subscribed event occurs within the Verint Community platform.
- Manual. Manually triggered automations can be triggered by other scripted components in Verint Community (widgets, themes, other automations) or by plugins.
- HTTP Request. Automations enabling HTTP triggering are exposed as extensions to the REST API enabling web-based clients to trigger the automation.
Automations also can optionally expose configuration options to allow community managers to provide parameters and other configuration details to each automation.
Once triggered, automations have access to the trigger arguments (details about the API Event, parameters sent from a manual execution, or details about the HTTP request for HTTP request triggers), configuration data, and the full scripting/widget API to implement custom behaviors.
Automation types and active automations
Automations follow a model similar to widgets: Developers implement the type and community managers use/configure/enable those types.
Automation types are defined in Automation Studio (Administration > Automations > Automation Studio) and are implemented in Velocity or Server-side JavaScript using the Scripting/Widget API. See Working with Automation Studio for more details.
Community managers can manage instances of automation types in Automations (Administration > Automations > Automations). From this administrative user interface, community managers select, configure, name, and enable/disable automations.