Operation > Data Flow Management > Integrations > Integration Studio > Limitations

Limitations – Integration Studio

This section describes certain limitations on the Integration Studio functionality.

ClosedLimitations on Population Integrations
  1. When configuring a population job between two CMDBs, verify that the synchronized CITs are the same in the two CMDBs.
  2. When modifying a TQL query that is used in a population job, it is recommended to run a differential synchronization before modifying the TQL and a full synchronization after modifying the TQL. The differential synchronization removes any data that is no longer necessary as a result of the updated query, and the full synchronization creates new baseline data on the target system.

  3. After a job runs successfully, its status remains Succeeded even after the job definition is changed (for example, selecting another TQL query or enabling deletion) and saved.

ClosedLimitations on Federation Integrations

  1. When a virtual link exists between two data repositories, Universal CMDB supports mapping in the following cases only:

    • The UCMDB integration point lies at one end of the link and multiple data repositories lie at the other end. The Cartesian product is calculated for A’s data repository (UCMDB) and B’s data repositories (UCMDB, d2, d3).

    • The same data repositories lie at both ends of the link. The link is an internal link of each data repository and no mapping is required.

  2. When changes are made in the Modeling Studio and these changes affect the results of a TQL query, federated CIs in the view are not updated. This is because federated TQL queries are calculated ad hoc only and are not updated when a view is recalculated. To update the federated CIs, select the view in the CI Selector and click the Refresh CIs Tree button. (Note that the recalculation may take a long time.) For details, see Browse Views Mode.

  3. You cannot edit the values of attributes that are configured to be retrieved from both an external data repository and UCMDB during federation.

ClosedLimitations on Data Push Integrations
  1. After modifying a TQL query that is used in a data push job, it is recommended to run a differential synchronization before modifying the TQL and a full synchronization after modifying the TQL. The differential synchronization removes any data that is no longer necessary as a result of the updated query, and the full synchronization creates new baseline data on the target system.

  2. The Universal CMDB cannot push static attributes.