Make Configuration Item mandatory for Change

[mah1]

Vancouver Patch 5

We had a need to make configuration item mandatory for a Change.  This was done using a dictionary override and appeared to be working. However, we recently discovered a handful (around 12) of changes that have been created in the past year with an empty configuration item. I am not able to reproduce this; every time I create a change and try to save without specifying a configuration item, the standard "The following mandatory fields are not filled in: Configuration item" message is displayed and the change is not saved.  I checked all the views and configuration item is flagged as mandatory in all of them. 

How can this be made full-proof so that a change cannot be saved without a configuration item? Use a UI Policy instead of the dictionary override?  Is there any way to determine the circumstances that are permitting a change to be saved without a configuration item?

Thank you

[Anurag Tripathi]

The changes you saw without a CI, were they created without a CI or there was a CI which got deleted or removed later? 

[mah1]

It appears they were created without a CI.

Thank you

[Anurag Tripathi · Accepted solution]

Were they created by some automation or some integration?

Unless you find where was the leak you cant fix it.  Maybe add a Data Policy as well as it checks for mandatory fields form all sources, manual or integration etc.

[mah1]

As far as I can tell, they were created manually by different people using the change form not via automation or integration.

I will look into adding a Data Policy.  If I add a Data Policy, should I remove the dictionary override?

Thank you