Updating prompts and skills for consistent and efficient responses from BMC HelixGPT

The BMC HelixGPT administrator can easily manage skills and prompts by associating custom skills from one model to another and linking or unlinking custom prompts between different skills reducing the efforts to create new prompts and skills each time. The system's default settings remain fixed for out-of-the-box skills and prompts; you cannot modify them. However, you can modify custom prompts and skills to meet your needs.

As an administrator, you can version, edit, activate, copy, and delete prompt versions by selecting the prompt and following the respective actions.

Customized updates to prompts help you get more specific and relevant answers that fit your needs or scenarios.

Related topics

Skills

Prompts

Creating-prompts-and-skills-for-consistent-and-efficient-responses-from-BMC-HelixGPT


To associate a skill with another model

  1. In HelixGPT Manager, select the application and skill for which you want to change the model.
  2. From the Provider and Model lists, select the service provider and model version, respectively.
  3. Click Apply.

You can associate custom skills from one model to another. However, you cannot associate out-of-the-box skills from one model to another.


To link and unlink a prompt

You can reuse a prompt from a different skill in a new skill by linking it. In addition, if you do not want a prompt associated with a skill, you can unlink it. Unlinking helps to remove a prompt from a skill without deleting the prompt completely.

Important

  • You cannot link or unlink a prompt from an out-of-the-box skill.
  • When you unlink a service prompt from a skill, the entry is deleted only if the active router prompt is set as the starter prompt for that skill.
  1. In HelixGPT  Manager, select the application and the skill from which you want to link or unlink a prompt.
  2. To link a prompt, follow the steps below:
    1. On the Prompts tab, click Link prompt.
      A Link prompt dialog box opens.
    2. select the prompt from the list that you want to link in your skill.
      You can also directly type the name of the prompt or application in the Search box to filter the long list and select the prompt you want to link.

    1. Click Link.
  2. To unlink a prompt, complete the following steps:
    1. On the Prompts tab, click the Action button for the prompt you want to unlink.
    2. Click Unlink.
      unlink.png

    1. Confirm the unblinking.


To rename a prompt

The prompt name must be unique within an application. If a prompt with the same name already exists in the target application, you must rename the prompt when copying it from one application to another.

  1. In HelixGPT  Manager, select the application and the skill for which you want to rename a prompt.
  2. On the Prompts tab, find the list of prompts and click the Actions list next to the prompt you wish to rename.
  3. A Rename prompt dialog box is displayed. Enter the Prompt name and click Save.

image-2024-11-14_15-52-11.png


Versioning prompts

Versioning prompts in BMC HelixGPT enhances prompt management by enabling customers to create, save, and switch between different versions for various use cases. This feature helps retain changes for future reference, enhancing efficiency.

Consider the following points when you version a prompt:

  • You can version only the custom prompts.
  • If you want to version an out-of-the-box prompt, create a copy of that prompt and then version the copied prompt. 
  • When you create a new version of an existing prompt, the system automatically increments the version number from the latest available one. For example, if you have 4 prompt versions and want to add a prompt version to v2, the new prompt version is v5, not v3.
  • By default, when a new prompt version is added to a skill, it automatically becomes the active version for that skill.
  • When you rename a prompt, the system also automatically renames all its prompt versions.
  • When you publish a service prompt such as Guest Wi-Fi, it is added only to the active version of the router prompt in the target skill. If deleted, the entry is removed only from the active version of the router prompt.

To version a prompt

  1. In HelixGPT  Manager, select the application and the skill for which you want to version a prompt.
  2. On the Prompts tab, from the list of prompts, select the prompt for which you want to create the version.
  3. Click Add Version. Enter the required details.
  4. Click Create.

The following screenshot shows an example of options available for a prompt version:

image-2024-11-14_15-51-3.png

To edit a prompt version

  1. Select the radio button next to the appropriate version.
  2. Click Edit. 
  3. Click Save.

While editing a version, you cannot edit the prompt name, type, and version number. 

To activate a prompt version

When you add a new version, it automatically becomes the active version. To change the active version:

  1. In HelixGPT Manager, select the application and the skill for which you want to activate the prompt version.
  2. On the Prompts tab, from the list of prompts, select the prompt for which you want to activate the prompt version.
  3. Select the appropriate version and click Activate.

image-2024-11-14_15-48-38.png

To copy a prompt version

You can copy a prompt version from one skill to another from any application.

The version number of a copied version starts with version 1, regardless of the version from which it was copied.

  1. In HelixGPT Manager, select the application and the skill from which you want to copy a prompt version.
  2. Select the prompt version you want to copy and click Copy. 
  3. In the Copy prompt dialog box, specify a Prompt name for the new prompt.
    The name must be unique for that application.
  1. From the list of skills and their applications, select the skill that you want to copy
    You can also directly type the name of the skill or application in the Search box to filter the long list and select the skill you want to copy.
  2. Click Copy.

copy_prompt.png

To delete a prompt version

You can delete a specific version of the prompt. Deleting a version of a prompt removes it from all skills or applications where it’s used.

  1. Select the radio button next to the appropriate version.
  2. Click Delete.
    A confirmation dialog box appears to finalize the deletion.
  3. Click Yes.

image-2024-10-30_15-20-45.png

To delete a prompt with all the versions

You can delete a complete prompt, which removes all versions associated with it.

  1. Click the Actions list next to the prompt you want to delete.
  2. Click Delete.
    A confirmation dialog box is displayed.
  3. Click Yes.

image-2024-10-30_14-53-15.png


To change the model for a prompt

By default, the prompts added to the skill leverage the model selected while creating the skill. As an administrator, you can change the model for individual prompts in a skill to improve their relevance and BMC HelixGPT response time. 

  1. In the HelixGPT Manager, select the application and the skill.
  2. Go to the Prompts tab and Edit the prompt for which you want to change the model.
    prompt_model.png
    The Prompt version editor opens.
  3. In the Promot version editor, in the Model section, disable the radio button to select the different Provider and Model.
    By default, the radio button is enabled to use the same provider and model for skill and prompt.
  4. Select the Provider and Model from the respective drop-down lists.
  5. Click Save.
    model.png


To add multiple response prompts for a skill

To configure multiple response prompts, you must modify the Router prompt. Make the following changes when updating the Router prompt:

  1. The classificationType key must have the value response.
  2. The nextPromptType and serviceName keys must have the <response prompt name> as a value.

See the example to modify the Router prompt:


Click here to view the example of translating the query in Spanish
8. If the user input text is a query about translating to Spanishthen classify the input text as 'live chat' in the classification field of the result JSON.  
The JSON format should be   {{       "classificationType": "response",       "nextPromptType": "Spanish Response",       "services":
[          {{             "serviceName": "Spanish Response",             "confidenceScore": "1.0",             "nextPromptType": "Spanish Response"          }}       ],       "userInputText": "...."    }}
9.


To configure options for the Response prompt

To configure options for the Response prompt, add a custom prompt of type Response to a custom skill and modify the code to include multiple options. See the example below:

Click here to view the example of Response prompt to configure multiple options
Return the response in the following format and ignore the input.
You must return these options: "example1", "example2", "example3"
input - {input}
Do not include any explanations,
only provide a RFC8259 compliant JSON response following this format without deviation:
{{
       "output": "Hello",
       "options": ["example1", "example2", "example3"]
}} 

Consider the following when configuring options:

  • If the Response prompt is not the starter prompt, you must add an instruction in the Router prompt.
  • The nextPromptType and serviceName keys must have the <response prompt name> as a value.


To obtain JSON from the Response prompt

To obtain a JSON string from the Response prompt, enclose the code block within double curly brackets. See the example below.

Click here to view the example of obtaining a JSON string from the Response prompt
Here is an example input -
{input}
Give a 2-line explanation about the following response and you must return it with your explanation.
The response must be formatted in a Markdown `json` code block.
"{{  "name": "name",  "scope": "scope",  "guid": "guid",  "overlayGroupId": "overlayGroupId",  "type": "type",  "layout": "{{"outlets":[{{"name":"name","columns":[{{"children":["children"]}}]}}]}}",  "componentDefinitions":
[    {{      "resourceType": "resourceType",      "guid": "guid",      "type": "type",      "propertiesByName": {{        "availableOnDevices": "[\"desktop\",\"tablet\",\"mobile\"]",        "recordDefinitionName": "recordDefinitionName",        "enableFiltering": "enableFiltering",        "enableRowSelection": "enableRowSelection",        "enableFilterPresets": "enableFilterPresets"      }}}}]}}" 


 

Where to go from here

Defining-knowledge-search-settings


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*