question Re: Lack of Duplicate UI Actions in Developer forum

Lack of Duplicate UI Actions

raprohaska — Wed, 27 Jul 2016 17:03:57 GMT

Attached are two UI Actions. One is global and one is for a specific table. Both are active and in at least one scenario, both conditions can evaluate to true.

I would expect that when both conditions evaluate to true, since the table specific action does NOT override the global, that duplicate buttons would be visible on the form. Yet this is not the case. If I disable either action individually, the other button will display on the form. If I disable them both, then no button will display on the form. Even still when both are active and both evaluate to true, only one button appears.

What attribute is causing this functionality? Since these are both out of the box, I would have expected the table specific button to override the global button.

Thanks for the insight in advance,

Re: Lack of Duplicate UI Actions

Chuck Tomasi — Wed, 27 Jul 2016 17:06:42 GMT

The reason both don't appear is because they both have the same action name (sysverb_update). Your "private" UI action for the table is acting as an override as designed.

This might help.

UI Action Overrides

Thanks for the chance to read XML.

Re: Lack of Duplicate UI Actions

Abhinay Erra — Wed, 27 Jul 2016 17:09:24 GMT

When you create a Ui action with same action name, it will override the global one.

UI Action Overrides

Re: Lack of Duplicate UI Actions

raprohaska — Wed, 27 Jul 2016 17:21:24 GMT

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.

Re: Lack of Duplicate UI Actions

Chuck Tomasi — Wed, 27 Jul 2016 17:23:16 GMT

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

Re: Lack of Duplicate UI Actions

Abhinay Erra — Wed, 27 Jul 2016 17:24:37 GMT

Well, let this poor guy get few points

Re: Lack of Duplicate UI Actions

Chuck Tomasi — Wed, 27 Jul 2016 17:28:21 GMT

"poor guy", that's good.

13th place and moving up quickly!

Re: Lack of Duplicate UI Actions

Chuck Tomasi — Wed, 27 Jul 2016 17:43:22 GMT

Hi Aaron, regardless of our friendly banter above, I am glad you got your answer resolved. Thank you for participating in the community.

Re: Lack of Duplicate UI Actions

raprohaska — Wed, 27 Jul 2016 17:45:37 GMT

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.

Re: Lack of Duplicate UI Actions

Chuck Tomasi — Wed, 27 Jul 2016 17:49:57 GMT

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.