Create a New Conversation in a Bot

To create a new conversation in a bot, do the procedure in this topic.

Figure: Create Conversation Configuration screen

Create Conversation Configuration screen

Examples

Prerequisites

Good to Know

  • In most text fields, you can use process data variables as an alternative to literal data values.
  • You can configure whether this activity waits for other activities before it runs.

    For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?

  • Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

  1. On the Application Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, in the Activity Library open the Bot Integration Bot Integration icon tab.
      2. On the Bot Integration Bot Integration icon tab, drag the Create Conversation Create Conversation icon activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.
  3. Click Create Conversation Configuration Create Conversation Configuration icon.

Procedure

  1. On the Create Conversation Configuration screen, in the Azure Bot Services field, select your Microsoft Azure Bot Service access token.

    To create a new access token, click Add Token Add Token icon. For more information, refer to Access Token for Azure Bot Service.

  2. To connect the request data from your schema to the source system, complete this field as necessary:
    Field Name Definition

    Request Mapping

    Function:
    Connects the bot API request parameter to your schema. This is mandatory only if the request passes data from the process schema to parameters in the bot API.
    Accepted Values:
    Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper.

    Use this screen to connect the request to the data model for your process.

    Default Value:
    None
    Limitations:

    Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

  3. To store the conversation ID as a process data variable, add the variable from the Process Data screen to the field Store Conversation ID in this Variable.
    Field Name Definition

    Store Conversation ID in this Variable

    Function:
    Specifies a process data variable that stores the conversation ID from Microsoft Azure Bot Service.
    Accepted Values:
    A process data variable that accepts an alphanumeric string with no spaces or special characters.
    Default Value:
    None
    Accepts Process Data Variables:
    Yes
    Limitations:

    Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?