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]

Depends what you are doing on the dictionary override, if it is only making the field mandatory then you can skip it

[mah1]

It is only making the field mandatory.

Thank you

[Anurag Tripathi]

Ya you can skip it then . But test well.

[mah1]

Is there any harm in leaving the dictionary override as is and adding a Data Policy for mandatory configuration item?

Thank you

[mah1]

If I add a Data Policy for this, is there any risk that the existing changes with no configuration item will be deleted?