Multidomain MDM
- Multidomain MDM 10.3 HotFix 1
- All Products
Reference Number
| Description
|
---|---|
MDM-20884
| Fixed a security issue.
|
MDM-19678
| A Promote API call updates all fields in a record instead of updating only the fields in a pending cross-reference record specified in the SIF request.
To specify that the MDM Hub only applies BVT calculation to fields that are part of the SIF request, set the
cmx.server.selective.bvt.enabled property to
true in the
cmxserver.properties file.
|
MDM-19677
| An ExecuteBatchAutoMatchandMerge API call does not return an error message even though errors are logged in the Hub Server log.
|
MDM-19653
| In a JBoss environment, when you use the Services Integration Framework (SIF) to run the MDM Hub operations, an out of memory error might occur.
|
MDM-19639
| A CleansePut API call does not update a child foreign key with the correct cross-reference record.
|
MDM-19635
| A SIF API call that runs a multimerge batch job fails with the following error:
SIP-23038: Internal error. The SQL statement generated the SQL error ORA-12899: value too large for column
|
MDM-18539
| If you make an API call for versioning-enabled base objects that use XREF and base object tables, the request fails and generates an error.
|
MDM-18238
| A Cleanse function call fails with an error.
|
MDM-18165
| In a PromotePendingXrefs API call, when the ROWID_XREF value is used as the record identifier, the child subject area records are not promoted.
|
MDM-18154
| When you use the CleansePut API call to add records, you cannot find the records using search.
|