Service-Now UI Actions

So, I was programming today and we found a little bug on the Service-Now implementation that we are doing.  We created a UI Action (javascript) to make a copy of many of the details in our Change Request record into a brand new Change Task record and this appears to work without any issues.

What I am noticing is that, on the "New" button task, after I fill in all of the details, I have a business rule (for both sides) that should be assigning an approval to requested for the resource identified in the Change Task.  Again this works for our custom action (though this is running as a business rule in the before update status).

If I put in debugging code, I can see that it is supposed to be hitting all of the major components of the add approval code and is passing in the right parameters.  When I do this from other processes that kick off this business rule, it works without error ...

Any thoughts?

Glide Records and addQuery

Alright, we are having fun programming again and writing business rules in Service-Now logic ...  It's a beautiful thing and I have been building some complex business rules that are way better than the work flow allows us to get to.

Right now, I am working on a really sweet Risk Calculator to automatically calculate our level of risk for a specific change.

Should be fun ...

Back to building my addQuery scripts.