OOTB ACL on Asset CI Install Status Mappings and Asset CI Hardware State Mappings

Peter525
Tera Expert

Hello -

 


I'm looking to disable the some of our unused CI and Hardware mappings, but noticed that there are ACLs on both preventing modifications to OOTB mappings. Is it safe to override this ACL anyway, or is there a good reason to leave the OOTB mappings alone and active?

 

Thanks.

1 ACCEPTED SOLUTION

Tony Chatfield1
Kilo Patron

Hi, OOB ACL's are there to support\control OOB functionality, disabling an ACL will not prevent use of the process or application but it will result in a structure that is no longer aligned with ServiceNow best practice and may result in unexpected behaviour. Before making the changes you are considering I would review the impact carefully and test thoroughly in a dev instance, ensuring that you test with users covering all of the roles involved in the process.

From a technical debt, and ease of upgrade perspective;
If you are not utilizing these mappings and they are not actively impacting your BAU operations, then I would leave them as they are.

View solution in original post

1 REPLY 1

Tony Chatfield1
Kilo Patron

Hi, OOB ACL's are there to support\control OOB functionality, disabling an ACL will not prevent use of the process or application but it will result in a structure that is no longer aligned with ServiceNow best practice and may result in unexpected behaviour. Before making the changes you are considering I would review the impact carefully and test thoroughly in a dev instance, ensuring that you test with users covering all of the roles involved in the process.

From a technical debt, and ease of upgrade perspective;
If you are not utilizing these mappings and they are not actively impacting your BAU operations, then I would leave them as they are.