Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you select the Attribute Conversation Item, then select the required attribute from the drop-down list. You can also enter the first character of the attribute name to scroll down the list to that letter. All Attributes must be defined in Attributes tab before you create or edit the conversation. conversation. In case the required attribute is not available in the list, click on 'Create Attribute' to add a new global attribute and use it in your skillFor further details refer to the Create Global Attributes article.

All details in the Attribute will be used in the Conversation Flow including the prompt and validation. For further details refer to the Create Global Attributes article.Image Removed 

Image Added

Info

Every Attribute added to the conversation flow is marked as Mandatory by default. In such a case, a default value is required. If the attribute prompt type is Static, you can unselect the Mandatory field. 

While executing a Skill, End-user can skip Static Prompt attributes using Skip command. Refer System Commands on Bot Settings more information on Skip Command in Luma.

...

  1. If you select Text, provide the Message in the text box and press Enter. You can specify multiple text messages, however, only one random text message is displayed to the user.
  2. If you select Quick Replies, the following supported formats are displayed:

    • Text
    • URL

      Provide the Message in the text box and the Button labels, as shown below. The system automatically uses the button label as the Payload. You can modify the Payload to meet your needs, which is used to pass any values for integration with other systems. For example, if you want to view the tickets by their priority (high, medium and low), mention those values as the button labels as shown below. If the priority is denoted as 1 for high, 2 for medium, and 3 for low in the corresponding system, then you can specify 1, 2, and 3 against the corresponding buttons as the payload.

  3. If you select Card, provide the prompt Message in the text box. Enter the Card Title, Card Subtitle and Button details. The system automatically uses the button label as the Payload. You can modify the Payload to meet your needs, which is used to pass any values for integration with other systems. For example, you may want to view the list of pending tickets and take an action to either approve, reject, or request additional information from the user. You can provide the button labels as Approve, Reject, and Need Info. Similarly, the corresponding payload information can be specified as shown below. 
  4. If you select Image, provide the prompt Message in the text box. Enter the Image URL and Tooltip details. For example, you may want to view the map of the place u wish to visit. You can provide the corresponding Image URL.
  5. Information Message could be used as the last step in the conversation to,
    1. Display the result of the integration call. 
    2. Suggest the list of skills to be suggested to the user as post fulfillment of the skill.

...

You can also format the bot messages using Smart Look upsLookups. Type '@' to enable smart lookups and select the Format Category from dropdown.  This standardizes the text format on all configured channels such as MS Teams, Slack, Whatsapp, Business Hangouts, Web widget.  

...

Info
titleNote
  • Once the skill is created, it remains in a Pending status. The skill cannot be executed unless you perform Build and Publish.
  • If you make any changes to a skill and save it, it remains in a Pending with Changes status until the changes are published.
  • Once the skill is published, the status changes to Published.

 To publish a skill, on the Skill Builder, click Build & Publish Skills on the right side of the Skill Builder page. For more details on Building and Publishing skills see Build and Publish.

Reorder Attributes, Quick replies, and Cards

To change the conversation flow according to your requirement, you can reorder the following in the Edit mode of the respective task or operation.

...

Grant access to skill to individual users and groups so that correct people can execute the skill. For a smaller organization, where skill has to be accessed by only a limited or few sets of users, you can directly add the users to the skill instead of creating a group and adding the skill and users to the group. For more details on permissions, see Define Roles, Permissions, and Groups.

...