Hi, I'm Bolo!
What would you like to know?
ASK BOLOPreview
Please to access Bolo.

Table of Contents

Search

  1. Introduction
  2. Installation and Upgrade
  3. MDM Multidomain Edition Version 10.2 HotFix 2
  4. MDM Multidomain Edition Version 10.2 HotFix 1
  5. MDM Multidomain Edition Version 10.2
  6. Informatica Global Customer Support

Release Notes

Release Notes

Informatica Data Director Known Limitations

The following table describes known limitations:
Reference Number
Description
MDM-16018
For records loaded through a batch job, the History view does not show event details for relationships that were created through a many-to-many relationship table.
MDM-14411
In WebSphere environments, when you edit a task for the first time after you start a WebSphere profile, the Edit Task dialog takes longer than expected to open and an error is generated in
cmxserver.log
.
Workaround: You can safely ignore the error. The next time a task is edited, the dialog appears as expected without errors.
MDM-14193
In IBM DB2 environments, an error occurs when you try to import custom login provider files. The login provider files are not imported.
Workaround: Connect to the IBM DB2 database and run the following commands to increase the blob data size:
SET SCHEMA CMX_SYSTEM ALTER TABLE CMX_SYSTEM.C_REPOS_DS_LOGIN_SETTINGS ALTER COLUMN BLOB_DATA SET DATA TYPE BLOB(10240000) CALL SYSPROC.ADMIN_CMD( 'REORG TABLE CMX_SYSTEM.C_REPOS_DS_LOGIN_SETTINGS LONGLOBDATA' )
Where:
  • CMX_SYSTEM is the schema name
  • 10240000 is the blob size, in bytes. You can adjust this number to accommodate the login provider file size.
MDM-14154
If a task title in Task Manager is greater than 254 characters, an exception occurs when the task is approved.
MDM-13802
If you use the Provisioning tool to configure the Dashboard Reports View, in Informatica Data Director, the Jaspersoft reports do not display in a user-friendly layout.
MDM-13585
When you launch Informatica Data Director with smart search and the Entity 360 framework enabled, a null pointer error appears in the server logs.
Workaround: You can safely ignore the error.
MDM-11035
If you filter tasks by multiple task titles, Informatica Data Director does not return tasks correctly.
MDM-10986
In Internet Explorer, the Task Manager might not reflect changes to task titles and comments.
Workaround: Use another supported browser.
MDM-10813
In Firefox, the time bar is missing from the History view. The issue occurs when you open a business entity with multiple cross-reference records in the Business Entity view and then navigate to the History view.
Workaround: Use another supported browser.
MDM-10734
MDM-13472
When you log in, Informatica Data Director passes user credentials to Informatica Data Controls as part of the login URL. By default, the credentials are not encrypted.
MDM-9364
When a reviewer edits data and approves a task, the
Comments
dialog box appears before the validation process runs. The issue occurs when a user exit handles tasks.
MDM-8768
After you upgrade and then delete all the configuration files from the repository table c_repos_component_instance, tasks might not display in the Task Manager inbox for the first user who logs in to Informatica Data Director.
Workaround: Log out of Informatica Data Director and then log in again.
MDM-8551
Error messages from user exit validation checks appear after the Add Comments dialog box is closed.
MDM-7894
If the Task Manager contains a task type name that does not exist in IDD configuration, the Task Manager cannot display the task or any other tasks.
Workaround: Add all task types to the IDD configuration file.
MDM-7877
After you deploy an Informatica Data Director application, configure MDM Security Access Manager roles and users, and complete other configuration steps, new tasks do not appear in the task inbox or the Task Manager and an error is generated.
Workaround: Use the Repository Manager to validate the Operational Reference Store and then restart the application server.
MDM-7865
A user cannot log in to Informatica Data Director if their user name contains non-UTF symbols, such as accents.
Workaround: Add the following JVM option to the application server:
-Dfile.encoding=UTF
MDM-7735
When you use uppercase characters to enter a user name to log in to Informatica Data Director, your ActiveVOS tasks do not appear.
Workaround: Use lowercase characters to enter a user name to log in to Informatica Data Director.
MDM-6708
You cannot open a task for a business entity if you do not have permission to view child record.
MDM-5893
When you import the Informatica Data Director (IDD) configuration XML to use an MDM Hub sample Operational Reference Store (ORS) that was upgraded from version 9.5.1, the following fatal error is generated:
SIP-BV-11005: Invalid role(s) 'DataSteward' in task assignment configurationfor task type'ReviewNoApprove' in subject area 'Person.'
Also, after you import the IDD configuration XML, metadata validation for the MDM Hub sample ORS fails.
Workaround: In the Hub Console, connect to the MDM Hub sample ORS and access the Roles tool. Acquire a write lock and change the name of the Data Steward role to
DataSteward
.
MDM-4000
When you update a record from an approval task, some data is not promoted.
MDM-3800
HORA-49646
If you upgrade MDM Multidomain Edition, you cannot view the relationships for a record that is Hierarchy Manager-enabled and that existed before the upgrade. When you click the Relationships child tab, the following error appears:
Invalid column name 'ROWID_HIERARCHY'.
Workaround: In the Hub Console, re-create the package for the Hierarchy Manager relationship.
HORA-51906
Subject Area names cannot begin with a number.
HORA-43191
In Configuration Manager, when you edit a subject area configuration to set the edit style of a column to Checkbox but then cancel the change, a null pointer exception occurs when you open a new subject area entity form.
The views that are based on the Enitity 360 framework are designed to work with the business entity data model. To use these views, you need to upgrade IDD applications from the subject area data model to the business entity data model.
The following table describes known limitations:
Reference Number
Description
MDM-14958
In the Search box drop-down list, when the list exceeds the height of the browser window, you cannot scroll the list to see the items that are off screen.
Workaround: In the browser, switch to full screen mode. Increase the resolution until you can see the remainder of the list.
MDM-14952
In the History view, the timescale labels in the Options menu do not display correctly initially.
Workaround: Interact with the timescale for the timescale labels to display correctly.
MDM-14933
In the Hierarchy view, business entities in the
Relationships
tab of the history do not open in Business Entity view.
Workaround: Use the Search box to find the business entity, and then open the entity in a Business Entity view.
MDM-14932
In the Timeline view, you cannot open the relationship records that appear on the
Relationships
tab.
MDM-14920
In the Hierarchy view, in the Entity Details dialog box, when you click
More Details
, the dialog box closes without opening the selected business entity.
Workaround: Use the Search box to find the business entity, and then open the entity in a Business Entity view.
MDM-14919
In the Hierarchy view, the anchor entity
Actions
Open in New Tab
option does not open a new tab.
MDM-14918
In the Hierarchy view, the anchor entity
Actions
Edit
Edit Entity
option does not open the business entity.
Workaround: From the View list, select the Business Entity view.
MDM-14890
In Microsoft Internet Explorer 10, the
Log Out
button is not visible from the Business Entity view and details do not display correctly in the History view.
Workaround: Use another supported browser.
MDM-14781
In the Matching Records view, when you select a child record as the target record, the interface lets you select a record in the pending state. However, pending records cannot participate in a merge process, which means that the merge fails.
Workaround: Select a child record in the active state as the target record.
MDM-14460
If the time zone of the application server is different from the time zone of the client, the time of an event in the History view differs from the time in the event details panel.
MDM-14385
When you view the details of merge and unmerge operations, user names are sometimes prefixed with
e360
in the Updated By or Created By fields.
MDM-14327
If there are multiple pages of search results for business entity child records and you type in a page number beyond the range of pages displayed, subsequent attempts to view a page of search results fail and an error occurs.
MDM-11397
If you use the mdm_sample Operational Reference Store, you cannot add or update the phone number of a Person business entity.
Workaround: Before you add or update the phone number of a Person business entity, perform the following steps:
  1. In the Hub Console, start the
    Cleanse Functions
    tool, and then acquire a write lock.
  2. Click
    Custom
    Parse Phone Number - NA
    .
  3. Click the
    Details
    tab of the Parse Phone Number - NA function.
  4. Right-click on
    Condition
    and click
    Edit Condition
    .
  5. In the
    Edit Condition
    dialog box, for each case value, change the country code from
    +1
    to
    1
    .
  6. Save the changes and use the Repository Manager to validate the metadata.
MDM-8606
In the Matching Records view, when you merge records, the system can appear unresponsive.
Workaround: Wait until the merge job finishes.
MDM-7597
If you delete a record and then search for the record, the ROWID of the deleted record still displays.
MDM-4710
In the Business Entity view, when you add data to a business entity and then click
Apply
, the Hub Server does not clean and correctly format the data.
Workaround: For your data to appear in the correct format in Business Entity view, click the
Save
button.
MDM-5715
On Internet Explorer 9 and 10, if you group search results by type, you cannot then expand the search results.
Workaround: Use Internet Explorer 11 or alternative browsers such as Chrome, Safari, or Firefox.
MDM-2699
In calendars, you cannot set a date before January 1, 1000.
MDM-2584
In the Task Manager, you are unable to sort tasks by Task ID, Task Type or Task Status.
MDM-2574
In the Task Inbox, setting the Owner filter to
Unclaimed
does not return the list of unclaimed tasks.
HORA-52227
If you restart the application server while logged in to the Business Entity view (formerly Entity 360 view), you cannot log back in after you refresh the page.
Workaround: Enter a valid Entity 360 view URL in your browser.
HORA-51951
In WebLogic environments, after you log in to the Business Entity view (formerly Entity 360 view) and then clear your browser cache, you cannot log in to the Entity 360 view again.
Workaround: Clear the cookies from your browser.
HORA-51879
The GetOneHop component displays entity label data that comes from the cross-reference table instead of the base object.
HORA-51869
Entity 360 access control depends on the base object of the root composite object, not on Subject Area permissions.
HORA-51864
The GetOneHop component does not sort related entities.
HORA-50581
The Matches component does not display null values correctly.
HORA-50578
The Twitter component loads more slowly than expected.
The legacy views are based on the subject area data model. These views are available to customers who upgraded from Informatica MDM Multidomain Edition Version 10.1.x and earlier.
The following table describes known limitations:
Reference Number
Description
MDM-14872
In the Matches view, users can add a record as a merge candidate that has already been selected to merge with another record. When the record is added as a merge candidate, an error occurs.
MDM-14767
If you unmerge a root node in the legacy XREF view, when the unmerge task is processed an error occurs and the record is not unmerged.
Workaround: Do not unmerge the root record of a business entity.
MDM-13787
In the XREF view, you can select a cross-reference record to unmerge when an unmerge task already exists for that record. An error occurs when the duplicate unmerge task is processed.
MDM-10625
In the Hierarchy view, the history of a record does not display as expected.
MDM-9796
In the Hierarchy view, when you disable an entity type in the
Filters
tab, you cannot create relationships with those entities.
Workaround: Before you create relationships, open the
Filters
tab, and select the entity types that you want to use in the relationship.

0 COMMENTS

We’d like to hear from you!