This documentation supports the 20.02 version of BMC Helix Platform. 
To view an earlier version, select 19.11 from the Product version menu.

Foundation data synchronization from Remedy ITSM Data Wizard to BMC Helix Platform

You can rename the Foundation data in Remedy IT Service Management (Remedy ITSM) by using the data wizard. The ITSM Sync utility synchronizes the data wizard changes to BMC Helix Platform.

Note

After you update the Foundation data in data wizard and synchronize the changes to BMC Helix Platform, you cannot revert the changes in the data wizard and re synchronize the update.

Before you rename the existing Remedy ITSM Foundation data in the data wizard, ensure that you understand the considerations in this topic for modifying Foundation data.

Supported Foundation name changes in Remedy ITSM

Only the rename made to the Foundation data by using the data wizard is supported. Any rename made to the Foundation data by altering the data through SQL queries or any backend changes is not supported. 

The following table lists the Foundation data that is supported for rename by using the data wizard:

Foundation dataDetails
Company Name

Rename is supported.

Notes:

  • Instances of the company name in the Company Name field is updated in BMC Helix Platform.
  • Any consuming application that leverages the company name is updated in BMC Helix Platform.
  • Instances of company name in any text fields are not updated.
Person NameRename is supported.
Login ID

Rename is supported.

Note: If the Login ID is used in the associated applications, the renamed Login ID is not updated in these applications after synchronization.

Operational CategorizationRename is supported in specific conditions. For more information, see supported rename of Foundation data and the limitations identified during the rename.
Product CategorizationRename is supported in specific conditions. For more information, see supported rename of Foundation data and the limitations identified during the rename.
Site NameRename is supported.
Site InformationRename is supported in specific conditions. For more information, see supported rename of Foundation data and the limitations identified during the rename.
Support GroupRename is supported in specific conditions. For more information, see supported rename of Foundation data and the limitations identified during the rename.

Supported rename of Operational Categorization, Product Categorization, or Support Group Foundation data 

The following table describes the scenarios where the rename of Operational Categorization, Product Categorization, or Support Group Foundation data in the data wizard is supported in BMC Helix Platform.

ScenarioDescription

Renaming only Tier 1 Operational Categorization, Product Categorization, or Support Group Foundation data without selecting any child tiers.

Renaming of Tier 1 is completely supported, only if you do not select Tier 2 and Tier 3 of Operational Categorization, Product Categorization, or Support Group Foundation data in the data wizard.

The renamed Foundation data value in Tier 1 is copied to BMC Helix Platform without creating any duplicate entries.

Renaming only Tier 2 (or Tier 1 and Tier 2) Operational Categorization, Product Categorization, or Support Group Foundation data without selecting any child tiers.

Renaming of Tier 2 is completely supported, only if you do not select Tier 3 of Operational Categorization, Product Categorization, or Support Group Foundation data in the data wizard.

The renamed Foundation data value in Tier 2 is copied to BMC Helix Platform without creating any duplicate entries

Renaming only Tier 3 Operational Categorization, Product Categorization, or Support Group Foundation data.

Renaming Tier 3 of Operational Categorization, Product Categorization, or Support Group Foundation data in the data wizard is completely supported.

The renamed Foundation data value in Tier 3 is copied to BMC Helix Platform without creating any duplicate entries.

Limitations during rename of Operational Categorization, Product Categorization, or Support Group Foundation data 

The following table describes the scenarios where the rename of Operational Categorization, Product Categorization, or Support Group Foundation data in the data wizard is supported with certain limitations in BMC Helix Platform.

ScenarioDescription

Renaming only Tier 1 Operational Categorization, Product Categorization, or Support Group Foundation data if the child tiers are selected.

Ensure that you do not rename Tier 1 when you have selected the child tiers.

If you rename Tier 1 when the child tiers are selected, the rename creates duplicate entries after the Foundation data is copied to BMC Helix Platform

 Details on the duplicate entries created after renaming Tier 1

For more information about supported rename of Tier 1, see Renaming only Tier 1 Operational Categorization, Product Categorization, or Support Group Foundation data without selecting any child tiers.

Renaming only Tier 2 (or Tier 1 and Tier 2) Operational Categorization, Product Categorization, or Support Group Foundation data if the child tiers are selected.

Ensure that you do not rename Tier 2 when you have selected the child tiers. 

If you rename Tier 2 when the child tiers are selected, the rename creates duplicate entries after the Foundation data is copied to BMC Helix Platform. 

 Details on the duplicate entries created after renaming Tier 2

For more information about supported rename of Tier 2, see Renaming only Tier 2 Operational Categorization, Product Categorization, or Support Group Foundation data without selecting any child tiers

Related topics

Foundation data load and synchronization considerations

Loading existing Foundation data from Remedy ITSM

Was this page helpful? Yes No Submitting... Thank you

Comments