Group sysids are not syncing between instances, causing problems with approval group in workflow.

[Jonathan29]

I have 3 environments Dev, Test, and Prod. Typically when we created a new AD group, it would sync to all 3 with the same sysID. For some reason, I just added a new group, and all 3 instances have a different sysIDs for the group. I added this group to AD, and let the LDAP sync pull them in like I normally do. I don't know if we just got lucky with the other groups that it just created the same sysID across all instances.

I have created a new workflow and catalog item that requires an approval from someone within this new group that I created; however, when I import the update set to my Test environment, it does not go to that group for approval. When I look at the workflow in the test environment is show the sysID of the group from the Dev environment instead of the Test environment.

Is there something I am doing wrong with the group, or do I have to manually adjust the group selection when updating to the next instance?

[Pradeep Sharma · Accepted solution]

Hi Jonathan,

I can confirm that sys_id's will never be the same across the instance except when cloned or Manually/Automatically imported. Ideally, you would create a scheduled job and then sync the required information to other environments like dev, QA so that sys_id's are same across the instance. In this case please make sure to deactivate the job on DEV and QA instance.

Also note, for any new group that you manually created on dev, you will have to export and import the XML to QA and prod instance so that sys_id's are in sync. 

https://docs.servicenow.com/bundle/london-platform-administration/page/administer/import-sets/concept/c_XMLImportSets.html

To Schedule: https://docs.servicenow.com/bundle/london-platform-administration/page/administer/import-sets/task/t_ScheduleADataImport.html

-Pradeep Sharma

[Jonathan29]

That worked! I had to tweak the instructions a bit, but I was able to figure it out. 

[Pradeep Sharma]

You are very welcome Jonathan. Thanks for participating in the community!

-Pradeep Sharma