Eliminate "recreation" when the CI Type is changed to a sub-type in the same branch

Idea ID 1794329

Eliminate "recreation" when the CI Type is changed to a sub-type in the same branch

When a CI is rediscovered by a specific discovery job and the CI Type is changed the CreatedBy and the CreateTime attributes are reset.

This behavior is expected when the CI type changes to a different branch (i.e. unix to netdevice).

But why is it appled when the CI type is simply made more precise, using a sub-type of a CI type (i.e. node --> host_node --> unix)?

We think it will make more sense to not touch the CreatedBy and the CreateTime attributes in that situation.

Regards,

Benoit

 

5 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage and we expect the community to help prioritize the idea with comments and voting

Honored Contributor.. Honored Contributor..
Honored Contributor..

Hello,

I was trying to solve it withing one support case - without result (still open). And be happy not to hear what our Process Managers and Audits say when they can see that the elementary metadata like CreatedBy and CreateTime are not constant but change over time .... indeed it doesn't help  UCMDB/UD to be "source of truth" at all.

I.

Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

Micro Focus Expert
Micro Focus Expert
Status changed to: Already Offered

We investigated this issue, attempting to recreate the problem using CMS 2019.05.  We are able to demonstrate that the behavior requested by this ER is actually already fulfilled with CMS 2019.05.  This means you can resolve the issue by performing an upgrade to the latest CMS version we have available.

If, in your testing, you find this not to be the case in your environment, please reach out to me and we can re-open this ER and include your findings in our analysis.

About the Author
Bill has over 26 years of experience in the IT industry focusing on providing business solutions utilizing HPE Software’s tools at enterprise scale. He comes from the HPE-IT organization where he managed the first deployment of HPSC (now HPSM) and then later UCMDB with its discovery partner UD. Bill also managed a team of IT Developers, who created customized configuration management solutions for HPE-IT and HPE’s ES clients.
Most "Liked" Contributors
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.