Reviewing an Alert Task Configuration

After you have configured the steps to define a Bot alert task, you are ready to review your configuration before you save and close Bot Builder.

You must click Finish on the Review page to set the status of a task configuration to configured. Only tasks with Status set to configured can be published to a company, space, or accessed on the Developer tab on the GET BOTS page in the Kore application.

The fields displayed on the Review page depend on the Connection Type setting as webhook, web service, or RSS, and if the task was previously created and saved. The following illustration is an example of the Review page for an existing RSS task.

The following table describes the fields displayed on the Review page when you create a new task.

Field NameDescription
Name The name of the task displayed in the end-user interface, for example, New Follower, is displayed as shown in the following illustration.

Connection Type Shows the type of task. One of:
  • Webhook - The web application pushes data for the task to Kore.
  • RSS - The web services sends data to Kore with polling.
  • Webservice - The web service sends data to Kore when polled by Kore.
Label The name of the task.
State The state of the task. One of:
  • inProgress - The task configuration was started, but not yet complete.
  • upgradeInProgress - A copy of a published task used to edit, and when configured, deploy to end-users as an upgrade for the original task.
  • configured - The task configuration is complete, available for the developer, but not yet published for use.
  • awaitingApproval - The upgraded task is published for enterprise or space use, but has not yet been deployed.
  • published - The task is published for personal, enterprise, or public use.
Short Description The Short description for the task displayed immediately below the task title in the user interface.
Content Type The data type of the request object for the task.
Auth Mechanism The type of authorization mechanism defined. One of:
  • Basic - A standard protocol to collect username and password information. Kore uses SSL encryption in combination with basic authentication to help secure end-user information.
  • OAuth v1 - Enables web applications or web services to access protected resources using an API without end-users having to disclose their log on credentials to Kore. 
  • OAuth v2 - The newest version of OAuth protocol focusing on specific authorization flows for web applications and web services.
  • API Key - An identification and authorization token generated or provided by a web application or web service used to identify the incoming application request, and in some cases, also provides authentication for secure access.
  • None - Authentication is not required for this task.
Identity Provider The name defined for the authorization mechanism type.
Request Chain The URLs and paths to your Bot to initiate the delivery of the data payload from the Bot to Kore.
Alert Task Fields The fields displayed to the end-user to collect data to define the task request.
Alert Task Filters Filters the end-user can use to only show some of the data from the task response payload.
Trigger Interval The elapsed time between last task request object and the next automated task request, when specified.
Post Title The title for the body content of the data from the request object in the task displayed to the end-user.
Post Description The body content of the data from the request object in the task displayed to the end-user.
Search Keywords Search keywords defined that the end-user can search for to identify this task.

After you review your alert task, you can select a previous step in your task configuration and edit the settings, or click Finish to save and close your task configuration.

Next Steps

After you review and save a task, the Bot is available on the Developer tab in the GET BOTS page of the Kore application. To make the task available to an enterprise or space, you must first publish the task. For more information, see Publishing Tasks.