Hiya, we came across the same when we upgraded and updated the plugin. This is a bug confirmed by ServiceNow Support and it has to do with 2 ACLs, of type = ux_data_broker and operation = execute and these are:
e364ad62ff100210397cffffffffffa3
ab3c8a52ff500210397cffffffffff20
OOTB my understanding is that both ACLs should have snc_internal and snc_external. In our case we only had snc_external which is why we had the same issue as raised on this post.
The tricky part is that for us, both these ACLs are part of "now-list-commons" application which is ReadOnly so we cannot amend these ACLs as a client (not even with elevated admin role).
My suggestion in terms of next steps:
- try to repair the plugin sn_pw to see if the behaviour is corrected
- if it isn't see if these ACLs are editable for you to add both those roles mentioned above
- if you cannot do the changes, raise a case with SN Support but a piece of advice - ask them to apply these changes in an update set created on that application from the start so you can move the changes between environments (it's my current blocker now as they changed it in Default and cannot create an update set and move the changes into it due to the restriction at the application level)
Hope this helps, good luck 🙂
