Space banner

 

This version is currently available to SaaS customers only. It will be available to on-premises customers soon.

BMC

BMC Helix Virtual Agent 22.1

All versions
Use BMC Helix Virtual Agent to enable your end users to request services and resolve their issues in a conversational interface. Using natural language, BMC Helix Virtual Agent can report issues, create requests and cases, or search for knowledge articles on behalf of the users.


Release notes and notices
updated 13 Aug

Learn what’s new or changed for BMC Helix Virtual Agent 22.1, including new features, urgent issues, documentation updates, and fixes or patches.

Tip

To stay informed of changes to this list, click the  icon on the top of this page.


Related topics

Known and corrected issues

Support information

BMC Helix Innovation Suite Release notes and notices Open link


The following updates have been added since the release of the product:

Date

Summary

Reference
August 11, 22.1 enhancements and patches
July 28, 202322.1 enhancements and patches
June 7, 202322.1 enhancements and patches
March 24, 2023

This patch includes the following enhancements: 

  • IBM Watson Discovery has migrated its functionality from v1 to v2. For more information, see Migrating to Discovery v2 Open link .
  • Optionally display the company logo in BMC Helix Virtual Agent web UI.
  • Highlight key words in knowledge articles for users in BMC Helix Virtual Agent.
  • Display chat expiration message after the session timeout. 
  • Provide an initial intent in BMC Helix Virtual Agent at the start of the chat session. 
22.1 enhancements and patches
January 13, 2023

This patch includes the following enhancements: 

  • Permission settings to provide permission to a specific user role or group to use a chatbot.
  • Proactive notification settings to notify the user if the user is idle or inactive during conversation with the chatbot.
22.1 enhancements and patches
November 2, 2022

Issues that were fixed in this patch and issues that remain open

22.1 enhancements and patches
October 10. 2022

Issues that were fixed in this patch and issues that remain open

22.1 enhancements and patches
September 2, 2022

This patch includes the following enhancement: 

  • Update Watson SDK to latest version 9.3.x that will offer latest Watson features, such as auto-learn.
  • BMC Helix Virtual Agentcan display 63 characters in the titles of knowledge articles.
22.1 enhancements and patches
July 29, 2022

BMC Helix Virtual Agent includes the following enhancements:

  • View knowledge search metrics in the Chatbot Overview dashboard in BMC Helix Dashboards.
  • Display a message to end users when all agents are busy.
  • Support for rich text formatting in comments added to BMC Helix Digital Workplace Catalog service requests.
22.1 enhancements and patches

Planning and deploying chatbots

 

Before implementing chatbot, plan and identify the use cases that you want to address by using chatbots.

Integrating

 

As an administrator, set up integrations with other BMC products or third-party software.



Administering

 

As an administrator, change the branding of  BMC Helix Virtual Agent, configure the chatbot channels and knowledge search providers, and view the chatbot usage reports.

Troubleshooting

 

Resolve issues that you might encounter while using BMC Helix Virtual Agent.



Developer Communities

Developer Communities

Helix Communities

Communities

Videos

Videos

Education

BMC Training and Certification 

PDFs and videos

This topic describes and links to PDFs and videos that support this product release. If the ready-made PDFs of this space do not satisfy your requirements, you can export a custom PDF. 

or register to view the contents of this page.

Videos

The following list displays the topics that contain videos that supplement or replace the text-based documentation:


Frequently asked questions

This topic provides information that supplements the BMC Helix Virtual Agent documentation.

Frequently asked questions

This section provides answers to frequently asked questions about BMC Helix Virtual Agent.

You can enable chat for services from IBM Watson Assistant Skills or by using the Publish Chat-enabled service wizard in BMC Helix Virtual Agent.


BMC recommends that you enable chat for services by using the Publish Chat-enabled service wizard. For more information, see Importing chat-enabled services from BMC Helix Digital Workplace Advanced.


  1. Log in to your IBM Cloud account.
  2. Navigate to the IBM Watson Assistant Skill that is configured with BMC Helix Virtual Agent, and take the backup of the skill.
  3. Navigate to the dialog that contains intent for the service that has dynamic answers.
  4. Create a child dialog and specify its name by using the following syntax:
    Fetch Dynamic Answers - <Service Name>
    For example, Fetch Dynamic answers - Flight Reservation.
  5. Specify the condition as True.
  6. Next to Then set context:, click  , and open the JSON editor.
  7. In the JSON editor, replace the existing text with the following text:

    {
     
    "context": {
       
    "questionIdsWithDynamicAnswer": [
    
    <comma separated values of all the dynamic answers question Id>
    
        ]
      },
     
    "output": {
       
    "text": {
    
    "values": [],
         
    "selection_policy": "sequential"
    
    },
    
    "action": {
         
    "inputMap": {
           
    "service Id": "<serviced of the request>",
          
     "questionIdsWithDynamicAnswer":
    "$questionIdsWithDynamicAnswer"
         
    },
         
    "outputMap": {
           
    "status": "${actionResult.output.status}",
           
    "message": "${actionResult.output.message}"
         
    },
         
    "actionTypeName": "com.bmc.dsm.chatbot:fetchDynamicAnswerUsingServiceRequestId",
    
    "waitForActionExecution": true
    
        }
      }
    }

    The following image shows an example of fetching dynamic answers for the Flight Reservation service:

  8. In the Fill Questions - Flight Reservation child dialog, complete the fields.
    The following table provides examples of field values for the Flight Reservation service:

    Check forSave it asIf not preset, askTypeJSON content

    @sys-date && slot_in_focus

    $departingDate


    Required

    {

      "context": {

        "departingDate": "<? @sys-date+' '+((entities['sys-time'] == null) ? '00:00:00': @sys-time) ?>",

        "show_flyingTo": "true"

      }

    }

    $flyingTo == null && $show_flyingTo == true

    $temp


    Optional

    {

      "context": {

        "temp": "$flyingTo == null && $nextStep == 5",

        "sys_options": "<? context.bmc_lookup_mappings.get('66c33cf7-9a11-9104-a2b8-a5e06f2bc9be') ?>",

        "bmc_dynamicQuestionId": "66c33cf7-9a11-9104-a2b8-a5e06f2bc9be",

        "bmc_isCurrentAnswerValid": "false"

      }

    }

    input.text && slot_in_focus && $bmc_isCurrentAnswerValid

    $flyingTo

    Flying To

    Required

    {

      "context": {

        "flyingTo": "<? input.text ?>"

      }

    }

    $flyingTo != null

    $temp


    Optional

    {

      "context": {

        "temp": "$flyingFrom != null",

        "bmc_dynamicQuestionId": null,

        "bmc_isCurrentAnswerValid": "false"

      }

    }

  9. Save your specifications and close the JSON editor.


  1. Log in to your IBM Cloud account.
  2. Navigate to the IBM Watson Assistant Skill that is configured with BMC Helix Virtual Agent, and take the backup of the skill.
  3. Navigate to the dialog that contains intent for the service that has attachments.
  4. In the Attachment Question child dialog, complete the fields.
    The following table provides examples of field values for the Flight Reservation service:

    Check forSave it asIf not preset, askTypeJSON content

    @sys-date && slot_in_focus

    $returningDate


    Required

    {

      "context": {

        "show_attachmentDocument": "true",

        "returningDate": "<? @sys-date+' '+((entities['sys-time'] == null) ? '00:00:00': @sys-time) ?>"

      }

    }

    $attachRequiredDocument == null && $show_attachmentDocument == true

    $temp


    Optional

    {

      "context": {

        "temp": "$attachRequiredDocument == null",

        "$bmc_isCurrentAnswerValid": "false",

        "bmc_import_wizard_response_type": "Attachment"

      }

    }

    input.text && slot_in_focus && $bmc_isCurrentAnswerValid

    $attachRequiredDocument

    Flying To

    Required

    {

      "context": {

        "attachRequiredDocument": "<? input.text ?>"

      }

    }

    $attachRequiredDocument != null

    $temp


    Optional

    {

      "context": {

        "temp": "$attachRequiredDocument != null",

        "$bmc_isCurrentAnswerValid": "false"

      }

    }

  5. Save your specifications and close the JSON editor.

The following table describes the limitations of real-time translation for specific content:

ContentTranslation limitations or unsupported scenarios
Strings
  • After enabling real-time translation, all responses from the chatbot are translated. You cannot choose specific responses for translation. 
Knowledge articles
  • Custom model and dictionaries in knowledge articles are not translated. 
  • When a knowledge article content is in multiple languages, such as English, French, and German, the knowledge article might not get translated correctly.
  • Names of attachments might not get translated.

  • If the title of a knowledge articles or the content has GUID, the GUID value is not translated. 

  • If the title of a knowledge article or the content has words in upper case, for example ORACLE, such words are not translated.

  • If the knowledge article contain proper nouns as single words (not used in a sentence), for example Java, such words are not translated. However, proper nouns in a sentence are translated correctly. For example, Download Java from Oracle, is translated correctly.
  • If the HTML or JSON in a knowledge article is not valid, the knowledge search returns an error or incorrect translation.
Dates
  • When using BMC Helix Virtual Agent web UI, dates are not translated correctly.
  • When translating from Japanese, dates entered in a format other than yyyy-dd-mm are not translated. Administrators can advise their end-users to enter dates in the appropriate format.
The word Amazon
  • When using Microsoft Azure Translator Speech API to translate from French to Japanese, the word Amazon does not return correct results. Instead of Amazon, users can type search for Amazon so that the correct results are displayed. 


Related spaces

 
Was this page helpful? Yes No Submitting... Thank you

Comments