How to hide the 'Control assessment not applicable' checkbox from the control assessment?

[Snehal Madakatt]

Hi Team,

Does any one knows how to hide the 'Control assessment not applicable' checkbox which is available on the control assessment. And how to make it visible conditionally? 

In UI builder, the component is not editable presently. So is there any workaround to do this?

Regards,

Snehal

[jaikishan1]

Hi @Snehal Madakatt ,

The assessment data is fetched using a rest api. The use can customize these rest api's to show appropriate warnings or error messages when a user interacts with it. One way to achieve it is:
1. Customize the save API to prevetn the user from updating the field value in the backend.
2. Create a BR or client script which displays an error message or warning message to the user.

The save and fetch apis are provided below:

1. Save api which can be customised to show an info message: http://localhost:9090/sys_ws_operation.do?sys_id=d06e143543dc711042f50db5bab8f235&sysparm_record_tar...
2. api to fetch the assessment data: http://localhost:9090/sys_ws_operation.do?sys_id=c34466f253b310105f9fddeeff7b12bf&sysparm_record_tar...

[rupalipati]

Is there a way to perform similar functionality for inherent assessment? I created a check box field but facing issue with hiding the full component when it is checked

[jaikishan1]

No, Inherent assessment does not support this functionality. Users have to perform the inherent assessment if enabled in the RAM.

[Vaisakh Krishna]

Hi @Snehal Madakatt ,

Yes, this can be done now. We have a configuration available in RAM now for both Control and Residual assessments, where you can choose to hide this option. there is a 'Hide assessment not applicable' available on the form for Control assessment.

https://www.servicenow.com/docs/r/governance-risk-compliance/grc-risk-management-workspace/control-a...

Thanks,

Vaisakh

[DavidW447091066]

If it's an out-of-the-box field that's not configurable in UI Builder, there's no supported way to hide it conditionally. A custom component or script is likely the only workaround.