Workflow Execute

Workflow Execute allows you to integrate a CRM Third-party systems that manage such things as contacts, sales information, support details, and case histories. with CXone Agent or CXone Agent Integrated. This action triggers a workflow. Workflows include things such as displaying data about a contact or creating a ticket. Other actions used in the script send the results and relevant data to the agent application when the agent answers the call. The other actions also pass any necessary information back to the CRM when the call completes. You can define a music file or other audio sequence to play for the contact while the script executes the workflow. This action is located on the Framework tab in Studio.

Dependencies

• Before you can configure this action, you must add a CRM Third-party systems that manage such things as contacts, sales information, support details, and case histories. integration to CXone and enable the workflows you want to use. You can integrate CRMs with CXone Agent, CXone Agent Embedded, and CXone Agent Integrated.
• You must use a separate Workflow Execute action for each workflow you want to use in your script. You can include more than one Workflow Execute action in your script.
• To use the configuration wizard in this action, you must be logged in to CXone or log in to Studio using the Login button with your CXone user name and password. If you log in with the Login with Session ID button when you are not logged in to CXone, the wizard will not appear. This is because access to the wizard depends on Global Authentication, which is only used when you log in with your CXone user name and password.
• To send results of the workflow to the agent application, you must include a Custom Event action in the script. The Custom Event action must call specific events. The events are described in the online help about creating a script to integrate CRMs with CXone Agent, CXone Agent Embedded, and CXone Agent Integrated.
• This action must be used with the Agent Workflow Configuration action. It can only be used in CRM integration scripts.
• The Studio Framework tab must be enabled for your CXone tenant. Contact your CXone Account Representative for more information.

Supported Script Types

Phone	Digital

Input Properties

These properties define data that the action uses when executing.

Property	Description
Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.
configurationId	The configuration ID of the CRM you use. This field is completed automatically by the action's configuration wizard. If you use a variable in this field instead, format it with curly braces ( { } ). For example, {integrationConfigId}.
Phrase	Use this property to document the text that the prompt contains. The script doesn't use the text in this property. Because some prompts can be complex and contain multiple segments, it can be helpful to include the full text written without the formatting required by the Sequence property.
Sequence	Define the prompt that the action plays. A prompt can be a prerecorded WAV audio file or text-to-speech Allows users to enter recorded prompts as text and use a computer-generated voice to speak the content. (TTS). If the prompt is an audio file, enter the file name enclosed in double quotes. For example, "greeting.wav". If the audio file is located in a different folder, include the path to the file. For example, if the script is in the root folder and the audio file is in a subfolder two levels down, enter "Subfolder\Subfolder2\Audio-file.wav". If the script is in a subfolder one level down from the root and the audio file is in a different subfolder on the same level, enter "\..\Subfolder\Audio-file.wav". If the prompt is text-to-speech, enter the text you want the TTS Allows users to enter recorded prompts as text and use a computer-generated voice to speak the content. service to read. Each segment must be enclosed in double quotes and include a string reference character to identify the type of information it is. For example:  "%Your account balance is" "silence.wav"  "${accountBalance}" For more information about formatting prompts in this property, including the string reference prefix characters to use, see the Prompts page. Some actions with the Sequence property have access to the sequence editor, which is a graphical interface you can use to create prompts. This action doesn't access this editor. However you can use the sequence editor from an action that supports it, such as Play. Add Play to your script and create your prompt sequence. Paste the sequence text from the Sequence field in Play into this action and then delete Play. Playing a prompt is optional for this action.
workflowId	The ID of the workflow this action handles. This field is completed automatically by the action's configuration wizard. If you use a variable in this field instead, format it with curly braces ( { } ). For example, {searchWorkflowId}.
workflowPayload	Enter the name of the variable that holds the workflow payload that this action handles. Format the name with curly braces ( { } ). The payload must be converted into JSON. For example, {searchInput.asjson()}.
dynamicDataMappingId	The ID of the dynamic data mapping to display in the customer card when this workflow is executed.
actionType	The workflows for the type of action selected in the WORKFLOW EXECUTE wizard.

Output Properties

These properties contain variables that hold data returned from executing the action. They're available for reference and use when the action completes.

Condition	Description
errorArgs (out)	Enter the name of the variable to hold information about the error. The default variable is workflowErrorOutput. You don't need to format the variable name with curly braces.
resultSet (out)	Enter the name of the variable that you want to hold the result of the specified workflow. The default variable is workflowResultOutput. This field does not require curly braces.
cacheKey (out)	The variable that holds the search results. Results are stored in an elasticache.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition	Description
Default	Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
Success	Path taken if the action completes without errors and any API calls or data returns were successful (2xx response codes).
Timeout	The path taken when the workflow execution exceeds the timeout value specified in the input.
ValidationError	The path taken when any input cannot be validated. This includes: Configuration ID: Must be a valid configuration ID from the Agent Integrations > Configurations page in CXone. Workflow ID: Must be a valid workflow ID from the the Agent Integrations > Configurations page in CXone. Workflow payload: Must be a valid JSON string.
InvalidWorkflow	The path taken when the specified workflow is invalid.
InternalError	The path to take when the action encounters an error.
NotConfigured	The path taken if Agent Integrations are not enabled for your tenant High-level organizational grouping used to manage technical support, billing, and global settings for your CXone environment. Contact your CXone Account Representative to have the feature enabled.

Required SNIPPET Action Code

This action requires Snippet actions with custom code. Information about the required snippets is available in the online help page about integrating your CRM with a CXone Agent application.

Select Actions and Workflows

1. Double-click the Workflow Execute action in your script to launch the Custom CRM Configurations wizard.

   View image

   
2. Select the Custom CRM Configuration you want this Workflow Execute action to use. If the drop-down list is empty, you must set up a configuration before continuing. You must choose the same configuration in both the Agent Workflow Configuration and Workflow Execute actions in this script.

3. Select one or more Actions that you want agents to be able to perform when this script runs.

   Learn more about action types

   Field Value	Details
   Select All	Select all three actions, described below.
   Create Timeline	Agents can add timeline information to the Activities section of the customer card.
   Data Memorialization	Agents can add data from the selected record in the Activities section of the customer card to the record of the current contact. You determine the data that can be added by mapping it for this CRM in the Agent Integrations page in CXone. See the CRM integration steps for your organization's CRM and the agent application you use.
   Search	Agents can perform a second-level search. After performing an initial search, they can search again to reveal more information about the initial search results. The Search must be selected to have any search records displayed in the Customer Card.

4. In the Workflow Mapping section, select the workflows that you want to assign to the Actions you selected. You can only select one workflow per action. The Action column shows which action each workflow option corresponds to.

   The following example image shows the workflows available for ServiceNow. If you use a different CRM, the options will be different.

   View image

   
5. If you want to change a workflow mapping, clear the first selection before choosing a new workflow. If you want to remove all selected mappings, select the checkbox in the column header.
6. Click Next.
7. Verify your selections on the Custom CRM Configurations Updated window. If you need to change a selection, close the window and make your change.
8. Click Save on the Custom CRM Configurations Updated window to apply your selections to the Workflow Execute properties.

Script Example

The following example shows the Workflow Execute action being used to integrate a CRM application with CXone Agent, CXone Agent Embedded, or CXone Agent Integrated. You can find more information about using the action, including a sample script to download, on the help page about the integration process.