Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

Not able to select agents group in dispatcher workspace

Sneha KH
Giga Guru

Hi Community,

I am not able to select agents in dispatcher workspace though I have associated agents group and dispatcher group with suitable "type" field including with correct location for the group. So, what may be the issue, why am I not able to see agents group in dispatcher though I have given correct roles for group.

1 ACCEPTED SOLUTION

in our case - it was missing ootb, and my engineer just created a query_range ACL on mentioned table  - that fixed it

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/

View solution in original post

9 REPLIES 9

can you screenshot your 2 group configs? including "covered" and "roles"

- add the query range acl
- create a WOT in pending dispatch + populate the assignment group
- log in as a user with wm_dispatcher that is part of the dispatch group that covers the assignment group 
- test  if the available assignment group shows up in the filter  if there is a WOT in state pending dispatch

if none of that work (and you have latest version of the dispatcher workspace plugin), open a ticket

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/

Hello @Joshua Chen MTL ,
I have attached all screenshots

Sneha KH
Giga Guru

Adding to this question, whenever I try to work related to dispatching. I get this error mentioned below.
"Part of the query on sm_m2m_group_dependency has been ignored because of insufficient access for 'query_range' operation on sm_m2m_group_dependency.dispatch_group". 
I checked it and there is no ACL related issue.

in our case - it was missing ootb, and my engineer just created a query_range ACL on mentioned table  - that fixed it

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/

Hello @Joshua Chen MTL ,
I tried your solution by creating query_range ACL on mentioned table. It worked. Thank you so much