Known Error Record - Revision history

User at 22:22, 5 January 2023

2023-01-05T22:22:09Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T16:47:37Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 17:50, 29 January 2021

2021-01-29T17:50:53Z

User: Created page with "The details of each Known Error are recorded in a '''Known Error Record''' stored in the Known Error Database (KEDB).Defining Known Error Record [https://wiki.en...."

2021-01-29T17:50:15Z

Created page with "The details of each Known Error are recorded in a '''Known Error Record''' stored in the Known Error Database (KEDB).<ref>Defining Known Error Record [https://wiki.en...."

New page

The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a workaround does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB|KEDB]] in principle.

A Known Error record contains:<ref>What Does a Know Error Recor Contain? [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Advisera]</ref>
*status (e.g. “Archived” or “Recorded Problem” when Known Error is created, but root cause and workaround are not known yet)
*error description – content of this field is used for searching through Known Errors (e.g. by Service Desk staff or users) while searching for incident/problem resolution (e.g. “Printer does not print after sending a document to the printer. However, when printing a status page locally on the printer, everything works fine.”)
*root cause – entered by Incident/Problem Management staff (e.g. “Since printer does not accept documents to be printed from user computers, but prints out status report – a faulty network card is the cause of the problem.”)
*workaround – e.g. “Closest printer to the user should be set as default printer or user should be instructed which device to use until new printer is provided.”

@@ Line 1: / Line 1: @@
-The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a [[workaround]] does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB)|KEDB]] in [[principle]].
+== What is a Known Error Record? ==
-A Known Error record contains:<ref>What Does a Know Error Recor Contain? [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Advisera]</ref>
+The details of each Known Error are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>[https://wiki.en.it-processmaps.com/index.php/Problem_Management Defining Known Error Record -IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a [[workaround]] does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the KEDB in principle.
 *status (e.g. “Archived” or “Recorded Problem” when Known Error is created, but root cause and workaround are not known yet)
-*error description – content of this field is used for searching through Known Errors (e.g. by [[Service]] Desk staff or users) while searching for incident/problem resolution (e.g. “Printer does not print after sending a document to the printer. However, when printing a status page locally on the printer, everything works fine.”)
+*error description – content of this field is used for searching through Known Errors (e.g. by Service Desk staff or users) while searching for incident/problem resolution (e.g. “Printer does not print after sending a document to the printer. However, when printing a status page locally on the printer, everything works fine.”)
-*root cause – entered by Incident/Problem [[Management]] staff (e.g. “Since printer does not accept documents to be printed from user computers, but prints out status report – a faulty [[network]] card is the cause of the problem.”)
+*root cause – entered by Incident/Problem Management staff (e.g. “Since printer does not accept documents to be printed from user computers, but prints out status report – a faulty network card is the cause of the problem.”)
-*workaround – e.g. “Closest printer to the user should be set as default printer or user should be instructed which [[device]] to use until new printer is provided.”
+*workaround – e.g. “Closest printer to the user should be set as default printer or user should be instructed which device to use until new printer is provided.”

@@ Line 1: / Line 1: @@
-The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a workaround does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB)|KEDB]] in principle.
+The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a [[workaround]] does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB)|KEDB]] in [[principle]].
 A Known Error record contains:<ref>What Does a Know Error Recor Contain? [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Advisera]</ref>
 *status (e.g. “Archived” or “Recorded Problem” when Known Error is created, but root cause and workaround are not known yet)
-*error description – content of this field is used for searching through Known Errors (e.g. by Service Desk staff or users) while searching for incident/problem resolution (e.g. “Printer does not print after sending a document to the printer. However, when printing a status page locally on the printer, everything works fine.”)
+*error description – content of this field is used for searching through Known Errors (e.g. by [[Service]] Desk staff or users) while searching for incident/problem resolution (e.g. “Printer does not print after sending a document to the printer. However, when printing a status page locally on the printer, everything works fine.”)
-*root cause – entered by Incident/Problem Management staff (e.g. “Since printer does not accept documents to be printed from user computers, but prints out status report – a faulty network card is the cause of the problem.”)
+*root cause – entered by Incident/Problem [[Management]] staff (e.g. “Since printer does not accept documents to be printed from user computers, but prints out status report – a faulty [[network]] card is the cause of the problem.”)
-*workaround – e.g. “Closest printer to the user should be set as default printer or user should be instructed which device to use until new printer is provided.”
+*workaround – e.g. “Closest printer to the user should be set as default printer or user should be instructed which [[device]] to use until new printer is provided.”

← Older revision		Revision as of 17:50, 29 January 2021
Line 1:		Line 1:
−	The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a workaround does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB\|KEDB]] in principle.	+	The details of each [[Known Error]] are recorded in a '''Known Error Record''' stored in the [[Known Error Database (KEDB)]].<ref>Defining Known Error Record [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB). IT Processmaps]</ref> Known errors exist because the fix is temporary. The known error database consists of records where a permanent solution does not exist, but a workaround does. For a known error record, if a permanent solution was to be implemented, then the record can be expunged or archived for evidence. Known error records with an implemented permanent solution must not be a part of the [[Known Error Database (KEDB)\|KEDB]] in principle.

	A Known Error record contains:<ref>What Does a Know Error Recor Contain? [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Advisera]</ref>		A Known Error record contains:<ref>What Does a Know Error Recor Contain? [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Advisera]</ref>