Known Issues and Limitations

[Population Adapter] Cannot populate deleted CIs in a full population.

While you run a full population, if there are CIs that have been deleted since the last job run in Service Manager, the deleted CIs in Service Manager will not be populated to UCMDB.

However, the data push feature first pushes deleted CIs while running a full push.

In UCMDB, manually delete all CIs that were populated from SM by using appropriate filter criteria and then run a full population.

Warning: You must be very careful when using this workaround.

NodeRole is case-sensitive when mapping Node's NodeRole in UCMDB to Node's Subtype in SM.

Steps to reproduce this issue:

1. Create a Node in UCMDB.
2. Set the Node's NodeRole property to "Printer".
3. Run a data push in UCMDB to push Node CIs.
4. Check the CI's attributes in SM.

Result: The CI's subtype is "Node", which should be "Net Printer".

When the NodeRole is "printer", the result is correct.

When you run a full population for the first time to synchronize a large amount of CIs, if some of the CIs have an invalid attribute value (for example, IP address), the population job will ignore such CIs and run to completion with a Failed status and with errors logged on the Job Errors tab; In addition, the last job execution time will not be logged because the job is run for the first time but fails.

As a result, after fixing the invalid attribute values in Service Manager, you will not have a chance to re-populate the failed CIs through a change (delta) population. This is because when you run a change population, a full population will be executed instead (because the last job execution time is null).

When “Run in Multi-Company Mode” is enabled in the System Information Record in Service Manager (SM), the UCMDB integration fails to create changes or incidents in SM because the configuration item data modification event fails. The following error occurs:

ERROR TypeError: lib.uCMDBConfiguration.isEnable is not a function at char 1

To solve this issue, manually update a JavaScript:

1. Log in to Service Manager as a system administrator.
2. Go to Tailoring > Script Library, and open the discoveryEvent script.
3. In this file, replace all instances of string lib.uCMDBConfiguration.isEnable with lib.uCMDBConfiguration.isEnabled.

   Note: You can find the string in lines 43, 86 and 405.

4. Click Compile to make sure the code is correct, and then click Save.
5. Log off and log back in.

Set the parameter to False to solve this issue.

• When you deploy the adapter on the UCMDB standalone server (which is defined as a global-id generator by default), globalId and ucmdbId are the same thing. For this reason, setting this parameter to false can meet all of your needs satisfied by setting the parameter to true.
• When you deploy the adapter on a non-standalone UCMDB (for example, BSM's RTSM), setting this parameter to true is not supported. In addition, we do not recommend integrating the non-standalone CMDB (for example, BSM's RTSM) with Service Manager.

The data length of CI relationship name in Service Manager is 40 characters, which is not sufficient for the integration. Installing this content pack does not automatically increase this data length in Service Manager.

If a CI relationship name exceeds the data length, either the relationship name is truncated after push or the relationship cannot be pushed to Service Manager due to a duplicate key error.

Manually increase the data length in Service Manager:

Open the cirelationship table in Database Dictionary, and increase the data length of the relationship.name field from 40 to an appropriate value (recommended value: 300).