Explicit External ID Mapping

There may be situations where the populated data (CIs) will need to have a connector/adapter controlled ExternalId. Use the following mapping construct to do this:

In this case, the Root CI is populated with an ExternalId that was created at the connector level and placed on the Computer[‘external_id_obj’]. The creation of the ExternalId can also be done at the mapping level using a Groovy script.

Note The mechanism of explicitly creating an external ID overrides the target_entity type attribute. Thus, when creating an external ID either with the mapping script file or inside the connector, the type attribute is ignored, and the final UCMDB type of the populated CI will be the UCMDB type set in the ExternalId object.