ServiceNow group provisioning bug

servicenow
known-issues

(Alex Maier) #1

If you’re running Enterprise ServiceNow 3.2.1, you may have run into an issue with group provisioning.

The problem is caused by a known bug in v.3.2.1 of the Enterprise ServiceNow integration app, but the solution is actually quite simple, and you can fix the problemby editing the PagerDutyProvisioning script include.

You can find the include under PagerDuty ► Configuration ► Configuration Files, in the Script Includes tab.

Once you have the script open, go to line 243. You should see lines 243 through 247 look like this:

var defaultUserID = gs.getProperty("x_pd_integration_x.default_user");
if (gs.nil(defaultUserID)) {
  gs.debug("{0} attempting to use default user property but it is empty, aborting group provisioning", me);
  return;
}

What you need to do is this:

  1. Remove the trailing _x in the table name in the call to gs.getProperty
  2. Add a new line at the end of it, userID = defaultUserID;

After you’re done, the code should look like this:

var defaultUserID = gs.getProperty("x_pd_integration.default_user");
if (gs.nil(defaultUserID)) {
  gs.debug("{0} attempting to use default user property but it is empty, aborting group provisioning", me);
  return;
}
userID = defaultUserID;

Now you can save the script include, and try to provision an assignment group.


(Sean Higgins) #2

For anyone that has encountered this bug, the new v3.5 integration includes a fix :slight_smile: You can install the latest version from the ServiceNow App Store here.


(system) #3