Multidomain MDM
- Multidomain MDM 10.2.2 Service Pack 1
- All Products
Reference Number
| Description
|
---|---|
MDM-14928
| Occasionally, the Provisioning tool continuously tries to reload the Home page.
Workaround: Close and then reopen the browser. If required, restart the application server.
|
MDM-14749
| When you delete a base object in the Hub Console, the dependencies are not removed from the business entity configurations in the Provisioning tool.
Workaround: In the Provisioning tool, delete the dependencies on the base object.
|
MDM-14255
| When you configure an XML to Business Entity transformation, the parent node fields are not available for mapping in the cleanse transformation of a child node element.
Workaround: Manually enter the path to the parent element that you want to map. Use the Service Data Object (SDO) XPath expression, where
/ represents a root XML element. For example, in the transformation for the
address child node, to access the
dunsNumber parent element, use the path
/OrderCompanyProfileResult[1]/ServiceResult[1]/OrderProductResponseDetail[1]/InquiryDetail[1]/DUNSNumber[1] |
MDM-14528
| If you create a transformation with the same name as another transformation, a validation error message does not appear. An error appears only when you try to publish the changes.
|
MDM-14521
| When you use the Provisioning tool in the Chrome web browser, Chrome might become unresponsive.
|
MDM-14449
| If you make a field searchable in a reference entity that is referenced in two or more business entities, then the field is searchable for all the business entities.
Furthermore, if you make a field searchable in a reference entity that is not referenced in any business entity, then the field is not searchable.
Workaround: Make a field searchable in a reference entity that is referenced in only one business entity.
|
MDM-13754
| If a write lock is acquired in the Hub Console, the Provisioning tool does not work as expected.
|
MDM-8844
| When you publish configuration changes through the Provisioning tool, you can overwrite these changes if you generate a business entity schema through the IDD Configuration Manager.
|
MDM-8750
| When you configure a business entity model with a base object that has been configured as a entity base object for hierarchy management, the HIERARCHY_CODE column and REL_TYPE_CODE column are not automatically added to the business entity configuration.
Workaround: Manually add the HIERARCHY_CODE and REL_TYPE_CODE columns to the business entity configuration.
|
MDM-8668
| From the modeling page you can access and edit system columns.
Workaround: Avoiding editing system columns.
|
MDM-7219
| The Provisioning tool fails to launch when the last slash is omitted.
Workaround: Add a slash character to the end of the URL:
http:/host:port/provisioning/ |