Automations

Ben Tiedt — Fri, 28 Jun 2019 19:30:57 GMT

Current Revision posted to Developer Training by Ben Tiedt on 06/28/2019 19:30:57

Automations are [[Scripting|scripted]] extensions to the Verint Community platform that are developed and managed through the Administration area of Verint Community.

What is an automation?

Automations can implement [[General Purpose Automations|general business logic]] or integrate more directly with [[Points Automations|points]] or [[Achievement Automations|achievements]]. Automations are executed when they are trigged by an external event. Supported trigger types are:

[[Scheduled Trigger|Scheduled]]. Scheduled automations define a recurring schedule and are triggered on that schedule by the Verint Community Job Server.
[[API Event Trigger|API Events]]. Automations that subscribe to one or more API events are triggered whenever the subscribed event occurs within the Verint Community platform.
[[Manual Trigger|Manual]]. Manually triggered automations can be triggered by other scripted components in Verint Community ([[Widgets|widgets]], [[Themes|themes]], other automations) or by [[Plugins|plugins]].
[[HTTP Request Trigger|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|scripting/widget API]] to implement custom behaviors. Automations with [[Automation Targets|special targets]] get access to private APIs integrate deeply with their target.

Automation types and active automations

Automations follow a model similar to [[Widgets|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|Scripting/Widget API]]. See [[Working with Automation Studio]] for more details.

Community managers can manage instances of general purpose automation types in Automations (Administration > Automations > Automations). From this administrative user interface, community managers select, configure, name, and enable/disable automations.

Special automation types are instantiated as part of their integration with Verint Community. For example, [[Points Automations|points automations]] are configured and enabled as part of defining point factors in Administration > Membership > Points.

Automations

Ben Tiedt — Fri, 14 Jun 2019 20:57:52 GMT

Revision 5 posted to Developer Training by Ben Tiedt on 06/14/2019 20:57:52

Automations are [[Scripting|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 Trigger|Scheduled]]. Scheduled automations define a recurring schedule and are triggered on that schedule by the Verint Community Job Server.
[[API Event Trigger|API Events]]. Automations that subscribe to one or more API events are triggered whenever the subscribed event occurs within the Verint Community platform.
[[Manual Trigger|Manual]]. Manually triggered automations can be triggered by other scripted components in Verint Community ([[Widgets|widgets]], [[Themes|themes]], other automations) or by [[Plugins|plugins]].
[[HTTP Request Trigger|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.

Automation types and active automations

Automations follow a model similar to [[Widgets|widgets]]: Developers implement the type and community managers use/configure/enable those types.

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.

Automations

Ben Tiedt — Fri, 14 Jun 2019 20:57:26 GMT

Revision 4 posted to Developer Training by Ben Tiedt on 06/14/2019 20:57:26

Automations are [[Scripting|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 Trigger|Scheduled]]. Scheduled automations define a recurring schedule and are triggered on that schedule by the Verint Community Job Server.
[[API Event Trigger|API Events]]. Automations that subscribe to one or more API events are triggered whenever the subscribed event occurs within the Verint Community platform.
[[Manual Trigger|Manual]]. Manually triggered automations can be triggered by other scripted components in Verint Community ([[Widgets|widgets]], [[Themes|themes]], other automations) or by [[Plugins|plugins]].
[[HTTP Request Trigger|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.

Automation types and active automations

Automations follow a model similar to [[Widgets|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|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.

Automations

Ben Tiedt — Fri, 14 Jun 2019 20:53:55 GMT

Revision 3 posted to Developer Training by Ben Tiedt on 06/14/2019 20:53:55

Automations are [[Scripting|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 Trigger|Scheduled]]. Scheduled automations define a recurring schedule and are triggered on that schedule by the Verint Community Job Server.
[[API Event Trigger|API Events]]. Automations that subscribe to one or more API events are triggered whenever the subscribed event occurs within the Verint Community platform.
[[Manual Trigger|Manual]]. Manually triggered automations can be triggered by other scripted components in Verint Community ([[Widgets|widgets]], [[Themes|themes]], other automations) or by [[Plugins|plugins]].
[[HTTP Request Trigger|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.

Automation types and active automations

Automations follow a model similar to [[Widgets|widgets]]: Developers implement the type and community managers use/configure/enable those types.

TBD

Automations

Ben Tiedt — Fri, 14 Jun 2019 18:39:57 GMT

Revision 2 posted to Developer Training by Ben Tiedt on 06/14/2019 18:39:57

Automations are [[Scripting|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|widgets]], [[Themes|themes]], other automations) or by [[Plugins|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.

Automation types and active automations

Automations follow a model similar to [[Widgets|widgets]]: Developers implement the type and community managers use/configure/enable those types.

TBD

Automations

Ben Tiedt — Fri, 14 Jun 2019 17:09:12 GMT

Revision 1 posted to Developer Training by Ben Tiedt on 06/14/2019 17:09:12

TBD