The failed case of itsm project import process

Itsm project
phenomenon : After the process design is exported, it fails when importing the exported file.
Cause : When the deleted node has a dependency relationship, other related data nodes are not changed accordingly, and are saved directly, which causes the value of the "return to" field in the dependent node to be abnormal, and further leads to the existence of data in the exported process data Pollution.
Case:
Here we take the two nodes " Basic Environment Information " and " IP Address Assignment " as examples. After I delete the " Basic Environment Information " node, the value of the " return to " field of the " IP Address Assignment " node will not be modified. , Go directly to the next step to save, after the export process, see if it can still be imported? Import process: Import process result: Import failed here, let us look back and forth at the specific value of the " Assign IP address " node, as shown in the figure: When we directly save the node, there will be an error: Correct the node Save the editing and modification: the last step: export the entire process, and then import the entire process. result:
Insert picture description hereInsert picture description here

Insert picture description here

Insert picture description here
Insert picture description here

Insert picture description here

Insert picture description here
Insert picture description here

Insert picture description here

Insert picture description here

总结:删除的节点在后续的节点有使用到,请把后续的这些节点的信息重新进行编辑,进行保存,不要有遗漏,
否则导出的流程设计数据是存在污染的,进一步会导致流程设计数据无法导入。

Guess you like

Origin blog.csdn.net/qq_42631707/article/details/102569172