Idea ID: 1684116

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

Status : Already Offered
Already Offered
See status update history
over 2 years ago

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

 

Labels:

reconciliation
Parents
  • 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.

Comment
  • 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.

Children
No Data