Contoso identifies the following technical requirements:
* Data scientists must test Butler by using ASDK.
* Whenever possible, solutions must minimize costs.
* Butler must greet users by name when they first connect.
* Butler must be able to handle up to 10.000 messages a day.
* Butler must recognize the users' intent based on basic utterances.
* All configurations to the Azure Bot Service must be logged centrally.
* Whenever possible, solutions must use the principle of least privilege.
* Internal users must be able to access Butler by using Microsoft Skype for Business.
* The new Bookings app must provide a user interface where users can interact with Butler.
* Users in an Azure AD group named KeyManagers must be able to manage keys for all Azure Cognitive Services.
* Butler must provide users with the ability to reserve a room, cancel a reservation, and view existing reservations.
* The new Bookings app must be available to users in North America and Europe if a single data center or Azure region fails.
* For continuous improvement, you must be able to test Butler by sending sample utterances and comparing the chatbot's responses to the actua intent.
https://docs.splunk.com/Documentation/Splunk/8.0.2/Knowledge/SetupaGETworkflowaction Define a GET workflow action Steps
* Navigate to Settings > Fields > Workflow Actions.
* Click New to open up a new workflow action form.
* Define a Label for the action.
The Label field enables you to define the text that is displayed in either the field or event workflow menu. Labels can be static or include the value of relevant fields.
* Determine whether the workflow action applies to specific fields or event types in your data.
Use Apply only to the following fields to identify one or more fields. When you identify fields, the workflow action only appears for events that have those fields, either in their event menu or field menus. If you leave it blank or enter an asterisk the action appears in menus for all fields.
Use Apply only to the following event types to identify one or more event types. If you identify an event type, the workflow action only appears in the event menus for events that belong to the event type.
* For Show action in determine whether you want the action to appear in the Event menu, the Fields menus, or Both.
* Set Action type to link.
* In URI provide a URI for the location of the external resource that you want to send your field values to.
Similar to the Label setting, when you declare the value of a field, you use the name of the field enclosed by dollar signs.
Variables passed in GET actions via URIs are automatically URL encoded during transmission. This means you can include values that have spaces between words or punctuation characters.
* Under Open link in, determine whether the workflow action displays in the current window or if it opens the link in a new window.
* Set the Link method to get.
* Click Save to save your workflow action definition.