Deploying the sample Transfer to Service workflow for Messaging

Last Updated : Sep 28, 2020 |

About this task

Avaya provides a sample Transfer to Service workflow for the Messaging channel. With this procedure, you can deploy the sample Transfer to Service workflow and configure the workflow attributes.

Before you begin

  • Download the latest version of the sample workflow from PLDS.

  • In the Windows hosts file, add an entry containing the cluster IP address and FQDN of Avaya Oceana® Cluster 1. The FQDN in the entry must be different from the FQDNs of Avaya Oceana® Cluster 1 nodes.

Procedure

  1. In your web browser, enter the following URL to open the Designer Console of Engagement Designer:

    https://<AvayaOceanaCluster1_FQDN>/services/EngagementDesigner/index.html

  2. Click Import.
  3. In the Import Workflow dialog box, click Choose File.
  4. Browse to the folder containing the sample workflow, select the workflow, and click Import.
  5. Click Save Workflow.
  6. In the Save Workflow dialog box, do the following:
    1. In the Workflow field, type OceanaMessagingTransfer.

      You can provide any name for the workflow.

    2. Select the folder where you want to save the workflow.
    3. Click Save.
  7. Click Deploy Workflow.
  8. In the Deployment Details dialog box, click OK.
  9. In your web browser, enter the following URL to open the Admin Console of Engagement Designer:

    https://<AvayaOceanaCluster1_FQDN>/services/EngagementDesigner/admin.html

  10. On the Workflows tab, verify that the OceanaMessagingTransfer workflow is available in the list of deployed workflows.

    If the workflow is not available in the list, you must redeploy the workflow.

  11. On the Workflows tab, select the check box for the OceanaMessagingTransfer workflow and click Attributes.
  12. Optional In the Workflow Attributes dialog box, do the following:
    1. In the BotEnabled field, replace the default value False with the value True.

      When you replace the default value, the workflow enables the Bot after the contact is transferred to a service. The default value False specifies that the workflow always attempts to skip the Bot.

    2. Click Close.