https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studioen-US14.0.0.586 14https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studioFri, 28 Jun 2019 19:33:12 GMTe86d4249-5c08-463f-979b-98ee77ba4541Ben Tiedthttps://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio#commentsCurrent Revision posted to Developer Training by Ben Tiedt on 06/28/2019 19:33:12<br /> <p>Automation Studio is the integrated development environment for automations. Automation Studio is available by navigating to <strong>Administration &gt; Automations &gt; Automation Studio.</strong></p> <p><img alt=" " src="/resized-image/__size/1280x0/__key/communityserver-wikis-components-files/00-00-00-12-83/pastedimage1560885976372v1.png" /></p> <p>[toc]</p> <h2><a id="When_would_I_use_Automation_Studio" name="When_would_I_use_Automation_Studio"></a>When would I use Automation Studio?</h2> <p>Automation Studio is used by developers to review, create, modify, revert, and delete [[Automations|automations]]. Automations are implemented using server-side Javascript or Velocity. For more information on scripting within Verint Community, see [[Scripting]].</p> <h2><a id="Automation_Component_Definitions" name="Automation_Component_Definitions"></a>Automation Component Definitions</h2> <p>Each automation installed in the community is listed within the navigation tree. Each automation includes the following components represented as items under the automation in the tree.</p> <h3><a id="Overview" name="Overview"></a>Overview</h3> <p>The overview is shown by clicking the automation in the tree. The overview defines the integration for the automation with Verint Community. Specifically:</p> <ul> <li><strong>Name.</strong> How the automation is represented elsewhere in Verint Community for community managers to use.</li> <li><strong>Description.</strong> A brief description of the behavior/purpose/implementation of this automation.</li> <li><strong>Execute as the service account.</strong> When checked, the automation will always be executed as the service account (which has full permission to perform any action). If left unchecked, the automation will run as the current accessing user when the trigger that causes the automation to execute is executed.</li> <li><strong>Triggers.</strong> Identifies how the automation can be triggered. One or more triggers can be enabled. To learn more about triggers, see [[Trigger Types]].</li> </ul> <p>The overview also includes identifiers and file location details for automations and lists all supplementary files used by the automation. When viewing changes, the overview will highlight the components/files that are modified and can be used as a starting point for reviewing changes between automation versions.</p> <h3><a id="Implementation" name="Implementation"></a>Implementation</h3> <p>The implementation is a script, written in either server-side JavaScript or Velocity (see more about [[Scripting|scripting]]), is executed when a trigger (defined on the automation&#39;s overview) is executed. Details about the trigger is available in the <code>context_v2_automationTrigger</code> scripting API. The <code>context_v2_automationTrigger</code> should be reviewed to initiate an action and, in the case of manual and HTTP execution, to respond to the calling trigger. For more details about interacting with triggers, see [[Trigger Types]].</p> <p>Automations can [[Automation Targets|target]] special integration points within Verint Community. When implementing an automation targeting a specific integration point (for example [[Points Automations|points]] or [[Achievement Automations|achievements]]), the implementation is expected to perform a specific purpose (for example, a points automation should award/revoke points).</p> <h3><a id="Configuration" name="Configuration"></a>Configuration</h3> <p>Automations can optionally expose configuration options that will be exposed to community managers when they select and enable the automation. Configuration options are defined using the dynamic configuration XML format. See [[Supporting Configuration]] for more details about defining configuration options.</p> <h3><a id="Resources" name="Resources"></a>Resources</h3> <p>Automations support translations of strings stored in their resource list. The resource component of an automation contains all of the named translated strings in each available language to the community. The automation can reference these translated strings by their name in the automation&#39;s configuration, name, description, and in scripts.</p> <h3><a id="Files" name="Files"></a>Files&nbsp;</h3> <p>Automations can include additional files to implement the automation&#39;s behavior. Images, stylesheets (CSS and LESS), additional server-side JavaScript and Velocity files, and other file types can be included and referenced or executed by the automation. Additional files are listed under the automation in the navigation tree and categories as Images, Fonts, Style Sheet Includes, Scripts, or Other to help find files quickly.</p><div style="clear:both;"></div> https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio/revision/4Fri, 28 Jun 2019 19:03:06 GMTe86d4249-5c08-463f-979b-98ee77ba4541Ben Tiedthttps://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio#commentsRevision 4 posted to Developer Training by Ben Tiedt on 06/28/2019 19:03:06<br /> <p>Automation Studio is the integrated development environment for automations. Automation Studio is available by navigating to <strong>Administration &gt; Automations &gt; Automation Studio.</strong></p> <p><img alt=" " src="/resized-image/__size/1280x0/__key/communityserver-wikis-components-files/00-00-00-12-83/pastedimage1560885976372v1.png" /></p> <p>[toc]</p> <h2><a id="When_would_I_use_Automation_Studio" name="When_would_I_use_Automation_Studio"></a>When would I use Automation Studio?</h2> <p>Automation Studio is used by developers to review, create, modify, revert, and delete [[Automations|automations]]. Automations are implemented using server-side Javascript or Velocity. For more information on scripting within Verint Community, see [[Scripting]].</p> <h2><a id="Automation_Component_Definitions" name="Automation_Component_Definitions"></a>Automation Component Definitions</h2> <p>Each automation installed in the community is listed within the navigation tree. Each automation includes the following components represented as items under the automation in the tree.</p> <h3><a id="Overview" name="Overview"></a>Overview</h3> <p>The overview is shown by clicking the automation in the tree. The overview defines the integration for the automation with Verint Community. Specifically:</p> <ul> <li><strong>Name.</strong> How the automation is represented elsewhere in Verint Community for community managers to use.</li> <li><strong>Description.</strong> A brief description of the behavior/purpose/implementation of this automation.</li> <li><strong>Execute as the service account.</strong> When checked, the automation will always be executed as the service account (which has full permission to perform any action). If left unchecked, the automation will run as the current accessing user when the trigger that causes the automation to execute is executed.</li> <li><strong>Triggers.</strong> Identifies how the automation can be triggered. One or more triggers can be enabled. To learn more about triggers, see [[Trigger Types]].</li> </ul> <p>The overview also includes identifiers and file location details for automations and lists all supplementary files used by the automation. When viewing changes, the overview will highlight the components/files that are modified and can be used as a starting point for reviewing changes between automation versions.</p> <h3><a id="Implementation" name="Implementation"></a>Implementation</h3> <p>The implementation is a script, written in either server-side JavaScript or Velocity (see more about [[Scripting|scripting]]), is executed when a trigger (defined on the automation&#39;s overview) is executed. Details about the trigger is available in the <code>context_v2_automationTrigger</code> scripting API. The <code>context_v2_automationTrigger</code> should be reviewed to initiate an action and, in the case of manual and HTTP execution, to respond to the calling trigger. For more details about interacting with triggers, see [[Trigger Types]].</p> <h3><a id="Configuration" name="Configuration"></a>Configuration</h3> <p>Automations can optionally expose configuration options that will be exposed to community managers when they select and enable the automation. Configuration options are defined using the dynamic configuration XML format. See [[Supporting Configuration]] for more details about defining configuration options.</p> <h3><a id="Resources" name="Resources"></a>Resources</h3> <p>Automations support translations of strings stored in their resource list. The resource component of an automation contains all of the named translated strings in each available language to the community. The automation can reference these translated strings by their name in the automation&#39;s configuration, name, description, and in scripts.</p> <h3><a id="Files" name="Files"></a>Files&nbsp;</h3> <p>Automations can include additional files to implement the automation&#39;s behavior. Images, stylesheets (CSS and LESS), additional server-side JavaScript and Velocity files, and other file types can be included and referenced or executed by the automation. Additional files are listed under the automation in the navigation tree and categories as Images, Fonts, Style Sheet Includes, Scripts, or Other to help find files quickly.</p><div style="clear:both;"></div> https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio/revision/3Tue, 18 Jun 2019 19:25:43 GMTe86d4249-5c08-463f-979b-98ee77ba4541Ben Tiedthttps://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio#commentsRevision 3 posted to Developer Training by Ben Tiedt on 06/18/2019 19:25:43<br /> <p>Automation Studio is the integrated development environment for automations. Automation Studio is available by navigating to <strong>Administration &gt; Automations &gt; Automation Studio.</strong></p> <p><strong><img alt=" " src="/resized-image/__size/1280x0/__key/communityserver-wikis-components-files/00-00-00-12-83/pastedimage1560885934704v1.png" /></strong></p> <p>[toc]</p> <h2><a id="When_would_I_use_Automation_Studio" name="When_would_I_use_Automation_Studio"></a>When would I use Automation Studio?</h2> <p>Automation Studio is used by developers to review, create, modify, revert, and delete [[Automations|automations]]. Automations are implemented using server-side Javascript or Velocity. For more information on scripting within Verint Community, see [[Scripting]].</p> <h2><a id="Automation_Component_Definitions" name="Automation_Component_Definitions"></a>Automation Component Definitions</h2> <p>Each automation installed in the community is listed within the navigation tree. Each automation includes the following components represented as items under the automation in the tree.</p> <h3><a id="Overview" name="Overview"></a>Overview</h3> <p>The overview is shown by clicking the automation in the tree. The overview defines the integration for the automation with Verint Community. Specifically:</p> <ul> <li><strong>Name.</strong> How the automation is represented elsewhere in Verint Community for community managers to use.</li> <li><strong>Description.</strong> A brief description of the behavior/purpose/implementation of this automation.</li> <li><strong>Execute as the service account.</strong> When checked, the automation will always be executed as the service account (which has full permission to perform any action). If left unchecked, the automation will run as the current accessing user when the trigger that causes the automation to execute is executed.</li> <li><strong>Triggers.</strong> Identifies how the automation can be triggered. One or more triggers can be enabled. To learn more about triggers, see [[Trigger Types]].</li> </ul> <p>The overview also includes identifiers and file location details for automations and lists all supplementary files used by the automation. When viewing changes, the overview will highlight the components/files that are modified and can be used as a starting point for reviewing changes between automation versions.</p> <h3><a id="Implementation" name="Implementation"></a>Implementation</h3> <p>The implementation is a script, written in either server-side JavaScript or Velocity (see more about [[Scripting|scripting]]), is executed when a trigger (defined on the automation&#39;s overview) is executed. Details about the trigger is available in the <code>context_v2_automationTrigger</code> scripting API. The <code>context_v2_automationTrigger</code> should be reviewed to initiate an action and, in the case of manual and HTTP execution, to respond to the calling trigger. For more details about interacting with triggers, see [[Trigger Types]].</p> <h3><a id="Configuration" name="Configuration"></a>Configuration</h3> <p>Automations can optionally expose configuration options that will be exposed to community managers when they select and enable the automation. Configuration options are defined using the dynamic configuration XML format. See [[Supporting Configuration]] for more details about defining configuration options.</p> <h3><a id="Resources" name="Resources"></a>Resources</h3> <p>Automations support translations of strings stored in their resource list. The resource component of an automation contains all of the named translated strings in each available language to the community. The automation can reference these translated strings by their name in the automation&#39;s configuration, name, description, and in scripts.</p> <h3><a id="Files" name="Files"></a>Files&nbsp;</h3> <p>Automations can include additional files to implement the automation&#39;s behavior. Images, stylesheets (CSS and LESS), additional server-side JavaScript and Velocity files, and other file types can be included and referenced or executed by the automation. Additional files are listed under the automation in the navigation tree and categories as Images, Fonts, Style Sheet Includes, Scripts, or Other to help find files quickly.</p><div style="clear:both;"></div> https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio/revision/2Tue, 18 Jun 2019 19:20:05 GMTe86d4249-5c08-463f-979b-98ee77ba4541Ben Tiedthttps://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio#commentsRevision 2 posted to Developer Training by Ben Tiedt on 06/18/2019 19:20:05<br /> <p>Automation Studio is the integrated development environment for automations. Automation Studio is available by navigating to <strong>Administration &gt; Automations &gt; Automation Studio.</strong></p> <p>[toc]</p> <h2><a id="When_would_I_use_Automation_Studio" name="When_would_I_use_Automation_Studio"></a>When would I use Automation Studio?</h2> <p>Automation Studio is used by developers to review, create, modify, revert, and delete [[Automations|automations]]. Automations are implemented using server-side Javascript or Velocity. For more information on scripting within Verint Community, see [[Scripting]].</p> <h2><a id="Automation_Component_Definitions" name="Automation_Component_Definitions"></a>Automation Component Definitions</h2> <p>Each automation installed in the community is listed within the navigation tree. Each automation includes the following components represented as items under the automation in the tree.</p> <h3><a id="Overview" name="Overview"></a>Overview</h3> <p>The overview is shown by clicking the automation in the tree. The overview defines the integration for the automation with Verint Community. Specifically:</p> <ul> <li><strong>Name.</strong> How the automation is represented elsewhere in Verint Community for community managers to use.</li> <li><strong>Description.</strong> A brief description of the behavior/purpose/implementation of this automation.</li> <li><strong>Execute as the service account.</strong> When checked, the automation will always be executed as the service account (which has full permission to perform any action). If left unchecked, the automation will run as the current accessing user when the trigger that causes the automation to execute is executed.</li> <li><strong>Triggers.</strong> Identifies how the automation can be triggered. One or more triggers can be enabled. To learn more about triggers, see [[Trigger Types]].</li> </ul> <p>The overview also includes identifiers and file location details for automations and lists all supplementary files used by the automation. When viewing changes, the overview will highlight the components/files that are modified and can be used as a starting point for reviewing changes between automation versions.</p> <h3><a id="Implementation" name="Implementation"></a>Implementation</h3> <p>The implementation is a script, written in either server-side JavaScript or Velocity (see more about [[Scripting|scripting]]), is executed when a trigger (defined on the automation&#39;s overview) is executed. Details about the trigger is available in the <code>context_v2_automationTrigger</code> scripting API. The <code>context_v2_automationTrigger</code> should be reviewed to initiate an action and, in the case of manual and HTTP execution, to respond to the calling trigger. For more details about interacting with triggers, see [[Trigger Types]].</p> <h3><a id="Configuration" name="Configuration"></a>Configuration</h3> <p>Automations can optionally expose configuration options that will be exposed to community managers when they select and enable the automation. Configuration options are defined using the dynamic configuration XML format. See [[Supporting Configuration]] for more details about defining configuration options.</p> <h3><a id="Resources" name="Resources"></a>Resources</h3> <p>Automations support translations of strings stored in their resource list. The resource component of an automation contains all of the named translated strings in each available language to the community. The automation can reference these translated strings by their name in the automation&#39;s configuration, name, description, and in scripts.</p> <h3><a id="Files" name="Files"></a>Files&nbsp;</h3> <p>Automations can include additional files to implement the automation&#39;s behavior. Images, stylesheets (CSS and LESS), additional server-side JavaScript and Velocity files, and other file types can be included and referenced or executed by the automation. Additional files are listed under the automation in the navigation tree and categories as Images, Fonts, Style Sheet Includes, Scripts, or Other to help find files quickly.</p><div style="clear:both;"></div> https://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio/revision/1Fri, 14 Jun 2019 20:57:59 GMTe86d4249-5c08-463f-979b-98ee77ba4541Ben Tiedthttps://community.telligent.com/community/11/w/developer-training/65570/working-with-automation-studio#commentsRevision 1 posted to Developer Training by Ben Tiedt on 06/14/2019 20:57:59<br /> <p>TBD</p><div style="clear:both;"></div>