Change a CI name

[cochrantim]

I have CI's in the system that have been redeployed with new names.

What is the best practice for changing the name since it seems to be a key datapoint?

Tim

[lawrence_eng]

Hi,

For better visibility, I moved your question out of the user group discussion area and into the Implement sub-community.

Thanks,

Lawrence Eng

--

Online Community Program Manager, ServiceNow

[Community Alums · Accepted solution]

Name is a key data point, but for most types of CIs I would recommend just renaming the CI. Hardware CIs will likely have at least a serial number, if not that and an asset tag. Deleting the record isn't a great idea since it removes all the references to historical incident/problem/change data. Retiring the CI isn't a great option either, since any type of automated discovery or data import would likely still update the CI (though there are ways around it).

How exactly is this data getting populated in the first place?        

[NeilH2]

Best practice would probably be to rename the record but if the data is coming from Discovery then the name will auto update on the next scan anyway.

If your manually updating data then renaming will work fine, as @prdelong says retiring or deleting the record will remove historical data which snit ideal.

[cochrantim]

Thank you for the response. The initial data load was an import. Discovery is not an option at this time.

Regards,

Tim

Tim Cochran, PMP

Project Manager

Wyle

Science, Technology & Engineering Group

at NASA GRC

21000 Brookpark Road | Cleveland, OH 44135 | Phone: 216-433-8619 | Fax: 216-433-6364

E-Mail: timothy.c.cochran@nasa.gov<mailto:timothy.c.cochran@nasa.gov>

Note: The contents of this message are mine personally and do not reflect any position of NASA or the Glenn Research Center. This statement included per Glenn Research Center Personnel Policy Statement #OHRWP-9A, December 19, 2002.