This documentation supports the 20.02 version of Remedy Service Desk.To view an earlier version, select the version from the Product version menu.

Creating a known error

If you agree with the specialist's recommendation that a change is the best way to remove the root cause of the problem, initiate the change by creating a known error and assigning it to the change coordinator of the affected service.

If Remedy Knowledge Management is installed in your environment, you can create knowledge articles to describe known errors. This information could be useful to subsequent users who encounter or analyze the same or similar issues and problems. For information about how to do this, see Recording-a-Known-Error-in-a-knowledge-article.

To create a known error

  1. Open the relevant problem investigation as described in Viewing-problem-investigations.
  2. Set the Status field to Completed and the Status Reason field to Known Error.
  3. Click Save.
  4. When prompted by the system, click Yes.
     The Known Error form opens and a relationship is created between the known error and the problem investigation.
  5. In the Notes field, enter a brief description of the known error and a detailed description of the change requirements.
  6. Select the impact and urgency. The priority and weight are calculated based on the impact and urgency. If required, you can adjust the weight.
  7. Select whether view access is internal or public.
     This field is for informational purposes to indicate whether the known error is for internal or public consumption.
  8. From the Known Error Location list, select the client company.
  9. From the Categorization tab, select the operational and product categorizations.
     Operational categorization is based on a three-tier hierarchy that is defined in the Operational Catalog.
  10. Ensure that the assignments are correct:
    1. Ensure that your support group appears in the Coordinator Group field.
    2. Ensure that your name appears in the Problem Coordinator field.
    3. Ensure that the Change Coordinator's support group name appears in the Assigned Group field.
    4. Ensure that the Change Coordinator's name appears in the Assignee field.
  11. Ensure that the known error is related to all the affected service infrastructure and to the CI in which the problem resides. For information about how to do this, see Defining relationships.
  12. Ensure that the Status is set to Assigned.
  13. Click Save.

 

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