LOL, I actually don't mind XML, grew up on that stuff.

I typically like the way ServiceNow handles things but the action name thing can be a bit confusing. I'm surprised they don't use a standard list of action names with the ability to add custom action name. Some of the OOB actions names offer functionality that I wasn't aware of, for instance the cancel action name will ignore required fields.

Anyway, I'll get used to it. Thanks for the info.

Yeah, the sysverb_ stuff isn't documented very well (or at all that I can find.) Fortunately there aren't too many of them.

Interesting... I thought I had a best practice to always use the Action name field in UI actions somewhere in this collection: Technical Best Practices - ServiceNow Wiki

I don't see it. I know it was in the workshop slides.

Appears to be "Action Name". If one action is in global and one is on a specific table but both have the same name, the table specific version wins out.

Interesting pick, Aaron as I wrote the same thing (and referenced the same blog article by me) a few minutes earlier.