Known Error data migration

Known Error data migration differs from Interaction, Incident, and Problem because Known Error data must be copied from the knownerror file to the rootcause file, and the field mapping is also more extensive than in other modules.

Because it is a data copy, you cannot use the batch update mode. However, knownerror data volume is usually much less than that of Incident or Interaction.  Therefore, the normal copy mode should be sufficient for most environments.

The Data Migration Tool provides four migration settings, which you should run in their corresponding scenario as described in the following table.

Scenario	Migration setting(s)
Migrating from legacy Known Error	Legacy known error to new known error Legacy known error related record migration Legacy known error attachment to new known error attachment
Migrating from legacy Process Designer Known Error	Legacy Process Designer known error to new Process Designer known error For more information about how to use this migration setting, see Migrating from legacy Process Designer known error records.

Additionally, because knownerror data is copied and the records are re-created in the rootcause file, you must also update the screlation file to correct the relations of known errors. To do this, the out-of-box Process Designer provides another migration script called “Legacy known error related record migration”.

Default Settings:

Source Table	knownerror
Target Table	rootcause
Filter Condition	true

Field Mappings:

Target Field(Problem)	Source Field(Known Error)
id	id
category	category
assignment	assignment
status	status
logical.name	logical.name
brief.description	brief.description
description	description
root.cause	root.cause
update	update
open	open
open.time	open.time
opened.by	opened.by
update.time	update.time
updated.by	updated.by
close.time	close.time
closed.by	closed.by
reopen.time	reopen.time
reopened.by	reopened.by
priority.code	priority.code
ticket.owner	ticket.owner
severity	severity
sysmodtime	sysmodtime
sysmodcount	sysmodcount
sysmoduser	sysmoduser
assignee.name	assignee.name
subcategory	subcategory
product.type	product.type
problem.type	problem.type
company	company
dump	dump
resolution	resolution
workaround	workaround
incident.category	incident.category
current.phase	current.phase
incident.count	incident.count
initial.impact	initial.impact
future.impact	future.impact
impact	impact
users.affected	users.affected
problem.start.time	problem.start.time
expected.resolution.time	expected.resolution.time
location.type	location.type
frequency	frequency
proposed.solution	proposed.solution
review.notes	review.notes
cause.code	cause.code
affected.ci	matching.ci
ci.device.name	matching.device.name
ci.device.type	matching.device.type
ci.assign.group	matching.assign.group
ci.location	matching.location
affected.companies	affected.companies
affected.ci.count	matching.ci.count
last.task.no	last.task.no
kpf.id	kpf.id
kpf.file	kpf.file
folder	folder
closure.code	closure.code
estimatedCost	estimatedCost
estimatedMandays	estimatedMandays
rootcauseDate	knownerrorDate
solutionDate	solutionDate
affected.item	affected.item
rcStatus	rcStatus
interaction.count	interaction.count
publishWorkaround	publishWorkaround

Value Mappings:

Target Value Mapping Field	Mapping Type	Condition	Target Value
category	fixedValue	true	known error
current.phase	fixedValue	rcStatus~="Closed"	Logging
current.phase	fixedValue	rcStatus="Closed"	Closure
isKnownError	fixedValue	true	true
rcStatus	fixedValue	rcStatus~="Closed"	Open
rcStatus	fixedValue	rcStatus="Closed"	Closed

Migrating from legacy Process Designer known error records

If you upgraded your system from an older Process Designer version, you need to migrate your old Process Designer knownerror records to new Process Designer knownerror records by using the Legacy PD known error to new PD known error migration setting. The migration process includes the following procedures:

1. Change the old Known Error record to Problem record, and then create a new Known Error record with a category of "known error."
2. Link the new Known Error record to the Problem record.

3. Copy or do not copy the original relations to the new Known Error record, based on the option you select in the Post Script tab of this migration setting, as described in the following table.

   Option for relation processing	Description
   Skip Copying Relations to New Known Error Records	This option does not copy original relations to new known error records.
   Copy Relations to New Known Error Records	This option copies original relations to new known error records.