Hello,Let's take a use case (or actually a set of use cases) where users should be able to request different operations related to a given item. Let's say for instance operations such as installing, moving or disposing a server. Knowing that these us...

Hello,It is a well known, and I believe accepted, good practice to avoid synchronous AJAX in client script.  This is for reasons such as UI responsiveness and perf bottleneck. And having such synchronous AJAX will trigger Healthscan findings.While re...

Hello,As far as I know a Requester is defined as a user who can create, edit, and view their own requests.Now we often see requests to go further such as :- A manager should see all requests from his team- A user should see request from other users i...

Hello,We have a need where a catalog item should trigger a (work)flow involving a number of steps and users including non IT users.HR or legal users should be involved to perform some tasks or provide input at some stage. Obviously for that we would ...

Hello,Following similar discussion about Discovery here : https://www.servicenow.com/community/now-platform-forum/discovery-runing-in-production-is-advisable/m-p/2833318I wonder whether one should configure Services in dev or production instance ? (I...