Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Set Assignment Group for Specific Tasks within the Child Playbook

AfrozaHassan001
Tera Contributor

Hi All!!
For playbook there's a lane under which I have a few activates/tasks. For a few tasks I want the to set the assignment group to something else. My approach is to go directly to the specific activity definition and set the assignment group there as shown in the screenshot attached. (For SS I have left it blank), but it's not working. The activity is picking up the assignment group which I assign to the case on creation of it. 

 

Please help me out as to what other approach I can follow to achieve it. 

AfrozaHassan001_0-1672816034755.png

 

3 REPLIES 3

Community Alums
Not applicable

You need to do the following:

  1. Click on the 'Automation' tab
  2. Click 'Show additional options' 
  3. Scroll down and click on 'Add Field' 
  4. Select Assignment Group
  5. An additional field will be displayed, this is the field you need to populate with the Assignment Group. You can dot-walk here using PAD flow data or select a group directly.
     BrettIshmael_0-1719608113407.png

 

Daniel_san
Tera Guru

Did you find any solution?

I have the same issue. If I set the "assignment group" to "Trigger > sc_task Record > assignment group", only the group that initially received the task can work on the activity. If the task is reassigned to another group, the new group's members still can't edit it.

yaronguez
ServiceNow Employee
ServiceNow Employee

@Daniel_san , unfortunately input pills are only evaluated when the record is created. The assignment group of the Trigger sc_task record is used to create the new task record. The newly created record is not automatically updated if the trigger record's assignment group then changes. Your best bet might be to create a custom Activity Definition that uses a record in a table with a reference to your sc_task table instead of the default Flow Data record. You can then write an ACL that restricts access to users in the Assigned To or Assignment Group fields of the parent sc_task. Or you could write a business rule / flow that updates the child assigned to / assignment group fields whenever the parent changes.