Records are getting resolved without closure code and closure notesIssue Client Scripts are not honoured when closing the Problem. Closure code and Closure notes not setting as mandatory Best Practices If you are setting up a web service that permits external users to modify problems on the ServiceNow instance, the changes made through this service are not subjected to the UI policies on the problem form, as they are not updated via the instance UI. To ensure that the Close notes field is completed before a problem is marked as Closed/Resolved, you can create a data policy for server-side imports. Any data that does not adhere to this data policy will result in an error. Additionally, the policy can be applied on the browser by selecting the "Use as UI Policy on client" option in the data policy record. Since UI policies can also manage the visibility of fields on a form, you may want to augment UI policies with data policies rather than replace them. By default, data policies are applied to all GlideRecord operations including those used in Scripted REST APIs, and the REST Table API. You can opt out of applying the data policy to: Target records of web servicesImport setsClient-side UI policies The admin role is required to edit data policies.Related LinksRefer to Data policy for understanding data policies.