Bulk Assign To Me not working on Service Opeation Workspace list

[saint]

When I try to update bulk tickets the Assign to me button does not work, this is OOB on task table and does not pop-up any errors as well.

How should I test this?

I checked, it's not a UI action in the table, seems like something coming from the UI builder, but i'm unable to find the configuration settings of this to test and fix

[Sarthak Kashyap · Accepted solution]

Hi @saint ,

This button is coming from Declarative Action - List Action 

Table Name for reference - sys_declarative_action_assignment_list

This is OOTB button from ServiceNow , please check if you have mandatory field so be filled.

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak

[saint]

Thank you sm Sarthak, found em.

Now the weird part is, i tested it in few ways, like changing the order, and deactivating it one by one to see which one's present on the list i see. When I deactivate all 3 on the top, the button seems to be working, so i tried deactivating a combination and end up finiding these 2, when deactivated the finctionality starts working, else nothing happens when i click the button.

The problem is that, this is OOB and nobdy has updated these buttons ever, we did upgrade to zurich a month ago but the issue started 4 days ago, till then it was working, no patch fixes or anything that i know of.

I'm trying to figure out if i do end up deactivating the 2 buttons as part of my solution what will be the overall impact on the SOW, because these buttons will definitely being used somewhere else.

Just putting the entire scenario out for whats happened so far. Not sure what's the way forward yet.

[Sarthak Kashyap]

Hi @saint ,

So out of 3 Assigned To Me button  you want to deactivate 2 record, but I'll suggest don't deactivate that records, bcoz maybe they are using in other workspaces, and I checked out of 3 Declarative action 2 have same script which is below

current.assigned_to = gs.getUserID();

current.update();

Which is just assigning to logged in user. 

And other action is just doing the script assigns the current record to the logged-in user after validating permissions and group membership. It first checks if the record is active and whether the user can update the Assigned to field. If the record already has an assignment group, the user must be a member of it. When no group exists, it determines the user’s group automatically—using the primary group if multiple memberships exist. Finally, it sets the Assigned to field and updates the record.

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak

[saint]

Yes, I'm gonna test each one to figure out which page/list it actually affects. So far, I've found one on the list view. Still unsure of how exactly it stopped working all of a sudden with no updates to any related scripts or ui actions.

Thank you so much for the detailed explaination and helping me find the correct navigation for the buttons. Really appreciate it.