Idea ID: 1658568

Make the Global ID field in SMAX CIs Read-Only (on update)

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

My Dutch customer finds it unacceptable that users can update the Global ID field, if they can update CIs.

  • This Global ID comes from the Master Data Repository (normally UCMDB)
  • Unfortunately a lot of roles can update fields like Support Groups etc. (Config, ITAM, SLM, ...)
  • This means that there is a risk that people (accidentally) update this Global ID

The consequences of corrupting the Global ID for a CI are:

  • UCMDB integratie creates a duplicate CI as the existing CI is now considered for a CI with different Global ID
  • The same will happen for relationships to these old and new CIs
  • Data entered manually in the corrupted CI will not be in the new CI; e.g. Owner, 1st/2nd/3rd Level Support, ...

Suggested solution:

  • Make the Global ID field in CIs Read-Only (on update)

This avoids the risk of (accidental) updates to the field, but still lets people or interfaces create any new CIs with a Global ID.





  • Per the above note, It appears that the required functionality already exists in the product. The idea can be re-opened as needed with further discussion

  • Thank you  for the well documented Idea. If the 'managed externally' flag is on, the global ID becomes read-only (see image).  So in order for someone to acidentally or erroneously change the ID, they would first have to uncheck that flag, and then change the ID.  (And that change would be audited.)

    You could lock the extrenal flag to certain roles with a BR if still a concern. (And this would be a good OOTB optional rule).



  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.