{"id":17685,"date":"2016-06-02T20:21:09","date_gmt":"2016-06-02T20:21:09","guid":{"rendered":"http:\/\/apidocs.kore.com\/?post_type=docs&p=1820"},"modified":"2021-03-30T12:53:04","modified_gmt":"2021-03-30T11:53:04","slug":"creatingflows","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v7-1\/docs\/bots\/bot-builder-tool\/action-info-task\/creatingflows\/","title":{"rendered":"Flows"},"content":{"rendered":"
\r\n\t
\r\n\t\t
\r\n\t\t\t

Bot Builder Platform offers the unique ability to map bot tasks to other bot tasks within the same or different bot.
\nFor example, you can match an Add a Comment<\/em> or Assign a Ticket<\/em> task to an alert that occurs when a new service ticket is created. The event data detailed within alert tasks can be used to auto-populate the input field of Action tasks in the same or different system. Bots also can suggest actions to the user based on the content found within an alert and support the automatic execution of actions based on event data.
\nFlow tasks link a message response from one task to another related task of the same, or different bot. You can create flows between different Bots from action tasks to action tasks, alert tasks to action tasks, and alert tasks to dialog tasks.
\nTo map dialog tasks to other dialog tasks, or to sub-intents within the dialog task, you must use conditional transitions. For more information, see Creating Dialog Task Flows<\/a>.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

<\/div><\/div>\r\n\t
\r\n\t\t
\r\n\t\t\t

How Flows Work<\/span><\/h2>\n

When a bot sends a message to a user, they can click the task icon located to the right of the message\u00a0to display the tasks mapped to the task as a flow\u00a0as shown in the following image. The user can use the Tweet<\/em> task to tweet the message, or post to their Linked In<\/em> account using the Share Post<\/em> task.
\n<\/a>
\n\"Flows<\/a>
\nTo view the mapped tasks, the user can click the\u00a0Task<\/strong> icon, selects a task, and then define the parameters for the task.
\nYou can use parameters from the first task’s payload to pre-populate fields in the following tasks. For example, in a\u00a0Twitter<\/em>\u00a0task payload response, the New Follower Name<\/strong>\u00a0can be\u00a0pre-populated in the Salesforce Create Contact<\/em> task.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

<\/div><\/div>\r\n\t
\r\n\t\t
\r\n\t\t\t

Creating a Flow<\/span><\/h2>\n

To create a new flow, you need an existing bot as well as at least one published task. For more information, see Defining Bot Tasks<\/a>.
\nFollow these steps to create a Flow:<\/p>\n

    \n
  1. Open the bot in which you want to create a Flow.<\/li>\n
  2. Hover over the left-side navigation panel, and click Bot Tasks<\/strong>.<\/li>\n
  3. On the Bot Tasks page, hover over the\u00a0Flows<\/strong> tab and click the plus icon.\u00a0<\/strong><\/li>\n
  4. The\u00a0Create Flow<\/strong>\u00a0page opens.
    \n    \"\"<\/a><\/li>\n
  5. In the When this Task is triggered\/executed<\/strong> column on the left, click Click to select a Task<\/strong> to display the tasks available.\n
    Note:<\/strong> Only tasks that are published and approved by the Bots Admin are displayed as options to create a flow.<\/div>\n

    \"\"<\/a><\/li>\n

  6. Select the task that you want to add a\u00a0flow to, for example, Schedule Weather Report<\/b>. A list of fields is displayed for mapping.<\/li>\n
  7. In the Execute this Task<\/strong> column on the right, click Click to select a Bot<\/strong> and choose a Bot for the task that you will map to, for example,\u00a0Flight Management<\/strong>.<\/li>\n
  8. For the second bot, select\u00a0Click to select a Task<\/strong> to map the bot tasks and display the field mapping dialog.<\/li>\n
  9. Drag-and-drop fields in the When this Task is triggered\/executed<\/strong> column on the left to the Field section on the right for the following fields:\n
      \n
    • Label Mapping<\/strong> – The field label displayed to the end-user.<\/li>\n
    • Value Mapping<\/strong> – The value displayed in the field for the end-user.<\/li>\n<\/ul>\n<\/li>\n
    • Click the expand text area icon to display the mapping fields in a full-size editor.<\/li>\n
    • After you map a parameter from one\u00a0task to the next task, select one of the following options shown in the previous illustration for each Field<\/strong> displayed:<\/span>\n
        \n
      • Editable<\/strong> – The mapped value is displayed and editable by the end-user.<\/li>\n
      • Hidden<\/strong> – The Field<\/strong> is not displayed to the end-user. For example, you may need to pass a User ID<\/span> to the Bot, but only display the User Name<\/span> drop-down to the end-user.<\/li>\n
      • Read Only<\/strong> – The Field<\/strong> and mapped value is displayed, but not editable by the end-user. For example, for the Assign Task<\/em>\u00a0task for Asana<\/em>, you need the Task Id<\/em> and Workspace<\/em>, which can be mapped from the Asana<\/em> Task Updates<\/em> alert task, but are read-only because the end-user only needs to select which user to assign the task to.<\/li>\n<\/ul>\n<\/li>\n
      • Click Next Step<\/strong> to display the Mapping Name<\/strong> section.<\/li>\n
      • Enter the name of the mapping used in Bot\u00a0Builder in the Mapping Name<\/strong> field to identify this mapping for the flow. Optionally, select Mark this Task\u00a0as Suggested Task<\/strong>\u00a0to show the task\u00a0on the Suggested Tasks<\/strong>\u00a0tab.<\/li>\n
      • If all mandatory fields for the task are defined, the\u00a0Allow flow automation<\/strong> option is displayed.
        \nWhen selected, the end-user can enable this task to run automatically. For example, when an alert message for Crashlytics<\/em> indicates a server is down, using the predefined mapped fields, a JIRA<\/em> ticket can be automatically created without additional end-user input provided all required fields are mapped.<\/li>\n
      • Click Save & Exit<\/strong> to save the flow and close the Create Flow<\/strong> page.<\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n
        <\/div><\/div>\r\n\t
        \r\n\t\t
        \r\n\t\t\t

        Publishing a Flow<\/span><\/h2>\n

        After you configure your flow, you must publish the flow to make the mapping from one task to another available for end-users.
        \nTo publish a flow<\/strong><\/p>\n

          \n
        1. Open the bot that contains the Flow.\n
          Note:<\/strong> Only flows with status set to Configured<\/strong> can be published.<\/div>\n<\/li>\n
        2. Hover over the left-side navigation panel and click Publish<\/strong>.<\/li>\n
        3. Click the Settings<\/strong> \u00a0icon for the flow you want to publish, and then click Publish<\/strong>.<\/li>\n<\/ol>\n

          The Flow published successfully message is displayed and the flow is immediately available for any users that add the task to their account when the flow\u00a0is saved. You can edit the flow at any time and changes are applied immediately for end-users when the flow is saved for any published task approved and deployed by the Bots Admin.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

          <\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"Bot Builder Platform offers the unique ability to map bot tasks to other bot tasks within the same or different bot. For example, you can match an Add a Comment or Assign a Ticket task to an alert that occurs when a new service ticket is created. The event data detailed within alert tasks can...","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[38],"tags":[],"class_list":["post-17685","post","type-post","status-publish","format-standard","hentry","category-action-info-task"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/posts\/17685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/comments?post=17685"}],"version-history":[{"count":3,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/posts\/17685\/revisions"}],"predecessor-version":[{"id":20701,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/posts\/17685\/revisions\/20701"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/media?parent=17685"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/categories?post=17685"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v7-1\/wp-json\/wp\/v2\/tags?post=17685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}