flow designer - lookup of assignment group by sys_id not working

[JJ20]

flow designer

I am attempting to create a task and in the task select an assignment group.

In the step previous to the task assignment, I am able to identify the sys_id of the group I want (ET Monitoring)

However, in the next step, I can see the sys_id being assigned; however, when i bring the form up, the field is blank.

and in the runtime value section, i can see where assignment_group = sys_id

However, the field is blank in the incident.

Any thoughts as to why the assignment group isn't populating with the name corresponding to the sys_id (b3be0176dbc2f74049cd4b8b0b9619d1) ?

[K_ Scott Engstr]

It looks like you may have inadvertantly assigned the sys_id of the CI/Business Service into the output variable you named "group_sys_id" in step 2.1.1.4. 

Do you notice how the sys_id of your assignment_group is identical to the sys_id of your business_service in your raw text screen shot?  It seems highly unlikely they would both have the same sys_id value.

[JJ20]

I double checked with my admin, and yes, they have the same value.

One would think when the task gets created, it is looking against the sys_user_groups table.

[K_ Scott Engstr]

sys_id values are usually sufficiently long and complex enough to avoid duplication, but there is a finite number of possible values, so it can happen.  It could also happen if either the CI or the group was imported from another environment (e.g., from PROD down to sub-prod).  In order to avoid duplicate values, ServiceNow platform would need to check all other tables whenever a new record is creatyed, not just the groups table.  These two values in different tables having the same sys_id value but in different tables should not be causing any issues for you, I was just curious about it.

You should be able to solve this by adding a "Lookup Record" step before the "Create Task" step where you perform a lookup on the group using the sys_id, then use the retrieved record when you assign the group in the create task step instead of the sys_id string.

Good luck!

[Chandrashekar t]

Hi JJ, 

We created the catalog tasks by using the assignment group name instead of the sys_iD. It is working fantastic.  

Thanks 

Chandra