cmdb_ci field on incident is not getting read only

HanumanthaRR
Giga Contributor

2 hours ago - last edited 2 hours ago

Hi Everyone,

When an incident is closed, CI field is getting read only because of the OOB UI policy "Make Fields read-only on close". as part of an enhancement, I have deleted the UI policy action of cmdb_ci. so its is editable even after incident is closed.

later as per discussions in the internal team, reverted the changes. then cmdb_ci field expected to be readonly on closing the incident. but ci field is editable even after closing the incident.

please see below screenshots where the ui policies are same as OOB version. but i am not understanding why the ci field is not getting readonly.

 

HanumanthaRR_1-1793903182803.png

 

HanumanthaRR_0-1793903149654.png

 

0 Helpfuls
  • 69 Views
1 REPLY 1

AshishKM
Kilo Patron

an hour ago

Hi @HanumanthaRR ,

As per given screen shot, seems like you create a new UI Policy on incident table, but condition is not matched with OOTB UI Policy "Make fields read-only on close".

 

You can also check if the deleted UI Policy Action can be retrieved from Delete Table. 

Second, you can add new UI Policy Action under OOTB UI Policy

Or you can update the condition in your custom UI Policy same as OOTB.

 

This UI Policy is only enforcing the mandatory check on form load. 

AshishKM_0-1793905494244.png

 

Thanks,

AshishKM


Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
0 Helpfuls