You cannot open a task at all if your user role does not allow you to see record values associated with another user role.

When you create relationships in the Hierarchy Manager, you cannot use the

Tab

button to navigate to the

End Date

field.

Informatica Data Director user sessions end unexpectedly.

If you try to open a record that has hidden pending relationships in the Hierarchy view, the following error message appears:

Multiple parents are not allowed for entity. Relationship was not added to the graph.

When you add the create date to a search query, Informatica Data Director shows incorrect values in the search result.

The task inbox sometimes sorts ActiveVOS tasks inconsistently.

When you add an effective date to a search query, Informatica Data Director shows incorrect search results.

You cannot sort records that appear in the

Potential Matches

window of Informatica Data Director.

In a WebLogic environment, if you use a password of greater than 16 characters to log in, you cannot view any tasks.

If you select a value for a lookup field and multiple dependent lookup fields, and then select a different value for the lookup field, Informatica Data Director clears only the first dependent lookup field.

In Hierarchy Manager, you cannot use a user exit to create multiple relationships.

If you use the Provisioning tool to set filters on numeric fields, a GET request fails.

If the screen resolution is lower than 1366 x 768, the

Export

button does not appear in the

Export Data

dialog box.

In the Matches view, users without merge privileges can add merge candidates.

When you generate a business entity schema, the Operational Reference Store validation process generates the following errors:

SIP-MV-17007 - The Transformation group root is incorrect

SIP-MV-13007 - Constraint is not valid

When you update a relationship record in the Hierarchy view, you can assign the relationship to a hierarchy to which it does not belong.

If you map a lookup column to a cleanse function when you generate a business entity schema, the metadata validation process generates errors.

In Hierarchy Manager explorer view, if a record has many entities, you cannot scroll the workspace to create a relationship between entities.

When you create a search query including a lookup from the

Search

tab, Informatica Data Director does not display lookup records that are very long.

If you belong to a user group that is assigned to a role in the Hub Console, ActiveVOS tasks do not appear in the task inbox.

If you search for and update a record and then send it for approval, some fields in the search results subsequently appear empty.

When you create a search query including a lookup from the

Search

tab, Informatica Data Director does not display lookup records that are very long.

If you use a user exit to handle tasks, the user exit ignores pending records.

In a WebLogic and Oracle environment, a smart search request does not find a recently created record.

In the Task Manager, you cannot use the Due Date or On Time filters to sort ActiveVOS tasks.

In the Task Manager, you cannot use the Due Date or Owner filters to sorts ActiveVOS tasks.

If you bind an Informatica Data Director application to multiple Operational Reference Stores, data security does not work as expected.

After you approve or reject a task, the environment becomes unresponsive.

If you do not have an administrative user role, you cannot create a subject area record.

If you do not enable

In Message

check box when you configure a message trigger, a Put call fails with a null pointer exception.

When the end date of a relationship is 9999/12/31, you cannot open the associated entity in the Hierarchy view.

The MDM Hub has security vulnerabilities related to Apache Commons Collections.

If you use the Siperian workflow engine, the tasks assigned to users do not appear in their task inbox.

If you have multiple Informatica Data Director applications that use different subject area names for the same Operational Reference Store, a null pointer exception occurs when you log in.

You can edit or complete a task that another user owns.

When you retrieve the history of relationships, a poorly described error message appears.

If you use custom SSO authentication, a null pointer exception is generated when you open tasks.

If you export a search result that contains many records, the performance of the export process is poor.

In Informatica MDM Cloud Edition environments, you cannot perform a search in the related records component.

When you click the

Find Duplicates

option, all the duplicate records might not appear.

The searchable lookup does not return any results, but a basic search with the same query returns results. Also, if you open multiple search pages, only the last page displays the correct search results.

If a subject area has multiple child subject areas with the attribute

expand="true"

and some with

expand="false"

, an error is generated when you try to open a record.

If a business entity has many relationship records in the Hierarchy view, the performance of the query to fetch the relationship count is poor.

If the screen resolution is lower than 1366 x 768, the

OK

button does not appear in the Search page.

If you have multiple search forms open and you double-click a search result row on the uppermost search form, the other search forms close and an incorrect value might be selected for a target field.

If a hierarchy has many levels and each level in turn has many relationships, the Hierarchy view takes a long time to open.

After you upgrade, even if the primary object is not ready, the

Send for Approval

button appears.

In a WebLogic clustered environment, IDD might fail to launch with the following error:

ClassNotFoundException: Failed to load class weblogic.rmi.cluster.BasicReplicaList

After applying 10.1 HF2 EBF3 or EBF4, when users try to log in, the login fails with the following error:

AbstractMethodError

When you create a query on a subject area with a column that has a relationship type

Part of Primary

, an error occurs.

If you create a record with a NULL value in a column that has NULL to NULL matching enabled, the record saves without any warning message about potential duplicates.

A user exit implementation to add multiple child records generates an error.

In a clustered environment, after a database update, the last update date of the database might not be synchronized across the cluster nodes and can generate an SDO exception.

When you update a subject area field, the potential matches that appear misidentify the updated record as a new record.

If you have multiple search forms open and you double-click a search result row on the uppermost search form, the other search forms close and an incorrect value might be selected for a target field.

If you try to open a record from a search-only subject area, you cannot open the record later from any subject area.

Users that do not have the privilege to merge entities can create merge tasks.

After you import a data template into an IDD application, the application does not display the template from the

Import Master Data

option.

In IBM DB2 environments, if you increase the size of the SSA_DATA column in the match key table to 2000 characters, metadata validation errors occur.

In the Hierarchy Manager, when you add an entity to the canvas, a

NullPointerException

error is generated.

When you select the

Not a Match

option for merge tasks, the following error message appears:

There was a possible Flex security issue in some SFW files that are packaged with IDD.

The records from the relationship table are not shown in the child subject area when the values in ROWID_XREF and ROWID_OBJECT do not match.

When the C_REPOS_TASK_ASSIGNMENT table contains a huge number of tasks, the Task Administration window takes longer than expected to open.

When you make multiple searchQuery calls, the calls can intermittently generate a

ConcurrentModificationExeception

.

When you create a relationship between two timeline-enabled base objects, an exception occurs.

If you send an ActiveVOS task for approval and then change your password in the Hub Console, the task remains in a pending state after approval and the MDM Hub generates an exception.

When two Informatica Data Director applications are created for the same Operational Reference Store (ORS), you cannot have the same task type for both applications. When you edit the task configuration, the task configuration for the other ORS is overwritten.

After a base object is indexed, you cannot search, filter, or facet the system fields of the base object.

In an application that contains a large number of subject areas, when you run a smart search on all subject areas, the search fails.

When you fetch tasks from ActiveVOS, the action sometimes fails with the following exception:

java.sql.SQLException: You cannot commit during a managed transaction
				

After you update data using a custom user exit that is called through a custom action, the data in the view is not refreshed.

In environments with single sign-on authentication for the Hub Console and IDD, the tasks the user creates do not appear in the Task Manager.

When you update an ActiveVOS task, the action sometimes fails and an error occurs.

If you approve a task without providing a comment, a null pointer exception is generated.

When you set the

credentialsAutofillDisabled

property, the IDD login page does not set the

autocomplete

attribute for the Username and Password input fields.

When a package includes columns from a cross-reference table, the Query Builder window displays these columns only for administrative users. These columns are hidden when other types of users are logged in.

After you log in to an IDD application with user credentials that are validated through LDAP, a smart search fails with errors.

After you change the name of a task type, the task type is shown as unavailable in the

Task assignment

tab. Before modifying the task type in the IDD configuration page, ensure that there are no tasks in IDD Tasks dashboard.

When you have tasks with a mixture of

On Time

and

Overdue

statuses, if you filter the inbox to show only the tasks that are on time, the inbox does the opposite and shows only the tasks that are overdue. As part of the fix, you must update the MDM workflows.

In the Hierarchy view, when you end date a relationship and the relationship record is from a different source system than the IDD SMOS system, the existing relationship record is deleted.

When you use a Siperian workflow for tasks, a user with administrative rights cannot reassign tasks that belong to other users.