This documentation supports the 22.1 version of BMC Helix ITSM: Service Desk.To view an earlier version, select the version from the Product version menu.

Resolving tickets with the help of knowledge articles


Knowledge articles are created to document information that can be referred to when working on different tasks. These articles can provide information about known issues and their resolutions, configuration or set up information for common assets in the organization, or any information that should be shared in the organization. If you have installed BMC Helix ITSM: Knowledge Management with BMC Service Request Management, you can use knowledge search to look for existing documented solutions to similar incidents, or to help identify the root cause during a problem investigation.

BMC Helix ITSM: Service Desk allows users to leverage the knowledge articles by displaying a list of related knowledge articles when creating or updating a ticket. Recommended Knowledge displayed for a ticket are the results based on a search conducted by using key text in the ticket. Retired articles are not displayed under Recommended Knowledge. You can search for retired articles only through the global search or advanced search by using the Search for knowledge resources option.

You can relate an existing knowledge article to a ticket so that users can view information that was useful when you worked on a request. Relating the knowledge resource to a ticket updates the usage percentage of the resource and increases its credibility and use for resolving a request. It will also increase the resource's relevance to similar type of requests, placing it higher in the list when Recommended Knowledge for similar requests is displayed.

Before you assign an incident request, determine whether you can resolve the incident yourself. Use the Incident Management Incident Matching feature or BMC Helix ITSM: Knowledge Management to look for matching or similar incident requests, problem investigations, known errors, and solution entries.

Before you can use BMC Helix ITSM: Knowledge Management with Incident Management, you must be licensed to use it.

To search for a knowledge article from a BMC Helix ITSM: Service Desk record

  1. Open the record that you are working on.
  2. Click Functions > Search Knowledge Base to launch the Search Knowledge dialog box.
    An advanced search is performed automatically, using values from the Categorization tab of the Incident, Problem, or Known Error record, and the search results are displayed.
  3. To modify the search criteria, click the  Advanced Search  link in the  Search Knowledge  dialog box and modify the criteria as required.

    If you prefer to search by keyword only, clear the check boxes in the Product Categorization and Operational Categorization sections. For more information, see How knowledge articles are found .

  4. Select a knowledge article in the list of search results to view it.
  5. (Optional) If you find that the information in the knowledge article is useful, click Use.

    For Incident records, clicking Use populates the fields in the Categorization tab with the resolutions categories that are defined in the knowledge article. Additionally, a Resolved by relationship with the knowledge article is created. For more information, see Improving findability through categorization.

    Alternatively, you can click Relate to associate the knowledge article to the Incident.

Example of resolving an incident by using an existing knowledge article

Jennie Tennyson, a Level 1 Service Agent, is working on an incident reported by Greg Johnson, the Director of HR, who got the Blue Screen of Death after rebooting his laptop.

KnowledgeUseCase1.png

The process is as follows:

  1. Jennie is working on Greg's incident request related to the Blue Screen of Death that appeared after he rebooted his laptop. Jennie opens the incident request, and views the list of resources displayed on the right pane of the Incident Request screen.
    These resources are searched for based on keywords the system identifies in the incident ticket. For the current incident, knowledge articles related to the blue screen of death are displayed. One of the knowledge articles is related to a security patch that was recently deployed to the type of laptop that Greg uses, and is known to cause blue screen issues.
  2. She clicks the knowledge article to preview its contents.
    The information provided can be used to resolve Greg's issue, so Jennie contacts Greg and gives him with the information provided in the knowledge article.
  3. She clicks the Share icon_share.gif icon and emails the link to Greg for his reference.
  4. She wants to make sure that she is updated anytime the contents of the knowledge article are updated, so she clicks icon_follow.gif to follow the article.
  5. She clicks the Save to Ticket option to save the knowledge article to the ticket so that it is listed under Saved Resources. Users can view the related knowledge article as a resource that was helpful in resolving the incident when they refer to this incident ticket.
  6. Upon further investigation, she realizes that in addition to the steps in the knowledge article, Greg needs to apply an additional fix to complete the process. The additional fix to be applied to resolve the issue completely is not included in the knowledge article, so Jennie opens the Knowledge Article, clicks the Activity tab on the right panel of the knowledge article, and types in a new post related to the additional step.
  7. The knowledge article helped Jennie resolve the issue, so she clicks Yes to mark the knowledge article as a helpful resource. This improves the rating of the knowledge article as a resource, and lists it higher in the order when it is displayed as a Recommended Knowledge for similar issues.
  8. She clicks the far left side of the screen to navigate back to the ticket.
  9. She marks the incident record as Resolved, provides the appropriate Resolution categorization and Product Resolution categorization, and then closes the ticket.

Jennie notices that the reuse count of the article has incremented. When an article is related to an incident, and it is used to resolve that incident ticket, the reuse count of the article increments. The reuse count indicates usefulness of the article to resolve incident tickets. However, if the article is only related or pinned to the incident without using it to resolve the incident, the reuse count of the article does not increment.

Jennie can also create a new knowledge article to capture information she thinks may be useful to other service desk agents to resolve similar issues. 

 

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