When a cleanse transformation is used with a business entity view to business entity transformation, the following issues occur:

After you create records, the records fail to appear in the business entity view.
You cannot open records from query results.

The record views that are configured for specific user roles cannot be accessed by LDAP users with the same roles.

When a child record with a one-to-many relationship in the parent business entity has a one-to-one relationship in a business entity view, the record does not appear in the

Business Entity

view. The same record appears in a

Record Preview

page that you open from the

Search Results

page.

The Related Records component that lists related records does not honor the direction of the relationship between records. The issue occurs only with record view layouts that use the Related Records (View Mode) component. To fix the issue, the component and it's properties were updated in the Provisioning tool. For more information, see the

Release Guide

and the

Provisioning Tool Guide

for the release.

After tasks are added, the task count in the Task Manager does not refresh automatically.

In the Business Entity view, the vertical scroll bar for the quick scroll panel does not align correctly.

When you create a record and click

Save

multiple times, the

Task Comment and Attachments

dialog box appears for each click.

In the

Matching Records

view, when you identify duplicate records that you want to merge with the target record, the following error might be generated:

java.math.BigDecimal cannot be cast to java.lang.String

When you open a merge task, the performance is slower than expected.

When you attach a file to a task, if the file name contains non-Latin characters, the file name is modified and the file cannot be downloaded.

The documents attached to a record in the Business Entity view are not visible when tasks related to the record are opened in the Task Manager.

When external calls are configured with localized messages for the Data Director application, the localized messages do not appear.

In the basic

Matching Records

view, columns such as

Merge Preview

might not be aligned correctly.

When you use a search query to find records, the query results do not include the values of dependent lookup fields.

When you customize the search results using the

Customize Search Columns

dialog box, tool tips for the

Add all

and

Remove all

icons do not disappear after the click.

In the task inbox, the Creation Date filter works only for a specific date.

In the localized applications, the

Overdue

option of the task inbox

Due Date

filter does not appear in the localized language.

If a cleanse transformation is used with a view to business entity transformation, updates to records might generate a validation error.

When you edit and save a record that contains Unicode characters, the Unicode characters are corrupted.

In the Business Entity view, long names are not formatted correctly as the label for the record.

Multibyte localization data does not appear correctly as field labels.

When you make a Cleanse SIF request, the Informatica Data Quality cleanse function does not return values.

In the Related Records component, the record count is incorrect.

The search and queries results do not show lookup values when the foreign key is set to ROWID_OBJECT.

In the Hierarchy view, when you click

Add to Canvas

, the dialog box that opens is small and not user-friendly for viewing the search results.

In the Task Manager, when you claim a task from the task panel, the panel does not automatically change to My Open Tasks.

When the search results contain records with integer and date fields, sorting on these fields is incorrect. Instead of numeric or date sorting, string sorting is applied.

When the search results page has a vertical scroll bar, you must scroll to the right to use the

Show preview

and

Open in a new window

icons.

With Internet Explorer, when you create a new record, the icons for the child entity are not visible. This issue can not be reproduced in this release.

When you use the

Form

view to add or edit a child record, the data is not cleansed and standardized.

The

Cross-reference Records

view has redundant blank spaces and a horizontal scroll bar.

In the Business Entity view, when you select an item on the quick scroll pane, all the items scroll off the screen.

Even though a default image is configured for the image field of a view, the default image does not appear when an image is not attached.

In the child record sections of the Business Entity view, the filter icon appears even though the sections have no records.

The task inbox has unnecessary horizontal scrolling.

When you configure an application so that only some business entities are visible, all business entities appear in the Search box in the application header.

Fixed a security issue.

When multiple levels of dependent lookup fields exist, the second and later levels of the lookup fields display all the items instead of displaying the items associated with the selected lookup field.

When lookup fields are configured as searchable, with ROWID_OBJECT as the display field, when you select the fields, the Search Results page does not appear.

When smart search is enabled and the search results views are configured for an application, search results are not displayed for the Related Records component. The issue occurs only with the Related Records (View Mode) component.

In the

Matching Records

view, after you click

Merge

, the button is not disabled. You can click

Merge

again and a new merge process is initiated.

When the Home page displays the list of available tasks in the task inbox, you need to horizontally scroll through the task inbox to view all the details of a task.

The review panel of the Task Manager has multiple vertical scroll bars.

The History view has extra space around the page.

In the advanced

Matching Records

view, when you open a calendar, the calendar might hide the date field associated with it.

When the language of the user interface is French, the

Compare

button in the

Similar Records

component is misaligned.

In the

Task Manager

, the

Search

box for tasks does not display the complete field input hint.

When the user interface is set to some localized languages and you set a query as the default query, the

bad layout

error is generated.

In some of the localized languages of the user interface, when you try to view the history of a record in the Hierarchy view, the layout of the user interface is messed up.

In the localized versions of the application, some user interface elements of the task inbox are not localized.

In the

Cross-reference Records

view, users that do not have the privileges to view the cross-reference records of specific business entities, can view the associated child records in the navigation tree.

The dependent lookup fields of child records do not display correct values in the value list.

Verbose error message could potentially leak information.

In the

History

view, the record events that you select are not highlighted.

The

Cross Reference

page and the

Merge Preview

page have pagination issues.

When a user role does not include the create and read privileges for a business entity, users with this role can still view the tasks associated with the business entity.

If there are many comments associated with a task, the following error might occur:

Comments cannot exceed more than 3968 characters.

In the Business Entity view, child record fields are not aligned.

If you do not enable validation for a record though a validation check can be performed, the validation status is not set to null.

In the Business Entity view, the first record of each child node is highlighted.

When character data is entered in a numeric field, the following misleading error message appears:

Enter a Valid Pattern.

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.

When you approve tasks, you cannot attach files that have file names with special characters, such as

%

.

The promotion of a change list with the Data Director configuration fails.

You cannot delete a child subject area record and send it for approval.

When you open tasks, the following error might be generated:

java.math.BigDecimal cannot be cast to java.lang.String

When a record is opened in the Effective Periods View, tool tips for the timeline events do not show the configured timeline granularity.

When you create and save a basic query at the subject area group level and include relationship base object columns, an error occurs.

When you create a record or a query, the dependent lookup fields do not show correct values.

After records are merged, the UPDATED_BY column of the base object and the cross-reference record is null.

When you customize the query results to view specific fields, the customization is not preserved when you navigate away from the results page.

After you upgrade, the business entity schema generation might fail in the following scenarios:

If a subject area has duplicate default values and different roles configured, the business entity schema generation fails with the following error:
ERROR||Validation failed for some objects in the object tree|The bddApplication name must be set.
If subject areas have default values set to null or empty strings, the business entity schema generation fails with a null pointer exception.

When you view the history of a record, the history of child records does not appear.

When you open a record in the

XREF

view and click the

Details

tab to view child record data, an error occurs.

Even though the timeline granularity is set to seconds, you cannot open a record that is effective up to a specific time in seconds, because the

Open for Effective Date

dialog box does not allow you to specify time in seconds.

The task inbox does not display the task details icons beside the tasks.

The Hierarchy view takes a long time to display the history of records that have many relationships.

When you export the results of a query, the values of lookup columns that are not marked as lookups in a timeline enabled base object are not exported.

When a timeline enabled base object has lookup columns that are not marked as lookups, the Cross-reference Records view generates the following error:

SIP-10228: No record found for the specified RecordKey.

When a timeline enabled base object has lookup columns that are not marked as lookups, in the History view, you cannot view the cross-reference change details and the base object change details for events. An error occurs.

When subject areas and lookup tables have the same names, the business entity schemas are not generated correctly. The issue occurs even though the names have different character cases.

When the number 0 is stored in the DB2 database with a scale of 3, such as 0.000, the scale is not preserved in the record views. The value appears as 0.

When a timeline enabled base object has lookup columns that are not marked as lookups, a search for records based on lookups generates the following error:

SIP-14150: Data access failure in searchQuery. ORA-00918: column ambiguously defined.

When you use a profile to export search results for a specific effective period, the exported data is not for the same effective period.

When you apply data masking on a column, the data is still visible on the History tab for base object change details and XREF change details.

You cannot send a task for approval because the business entity schema is generated incorrectly.

When the

Subject Areas

option is the only option in the

New

window, the

Subject Areas

option is not selected by default.

The Expand and Collapse icons appear incorrectly for the logical subject area groups.

The values of a dependent lookup with a subtype qualifier does not filter correctly.

When you use data security filters without state management, you cannot open records.

When you add a hyperlink that contains the @ character, Data Director parses the text incorrectly and saves an incorrect hyperlink.

Fixed a security issue.

When you run a query that is case insensitive and then try to sort the records, an error occurs.

Task actions are disabled for users with uppercase user names.

When a package contains a join to a second package, a query on the first package fails.

You can edit a child record and a grandchild record at the same time. If you apply the edit to the grandchild record, but cancel the edit for the child record, a NullPointerException is generated.

When you add values to dependent lookups that have no values and send the changes for approval, the approval task cannot be opened.

Child records do not display in the History view. The following error is logged in the

cmxserver.log

:

SIP-14159 "Data access error when trying to process SEARCH QUERY REQUEST" 

You cannot import queries from versions prior to 10.3.

When a package contains a join to a second package, any query on the first package fails.

Generating a business entity schema takes a long time.

When HAProxy is used with Multidomain MDM, a search for records in Data Director fails and the Data Director Configuration Manager does not launch. The

502 bad Gateway

error occurs.

If a subject area has security filters that include colons (:) in the definition, the business entity configuration generated by the MDM Hub causes the Operational Reference Store (ORS) metadata validation to fail.

SIP-MV-13042 Object name contains special
characters.

The getChangedChildren API returns incorrect results at the grandchild level.

Logical subject area groups with 2 levels do not work.

After upgrading from version 10.1, when you use the Data Director Configuration Manager to generate the business entity schema, misleading warnings and information messages appear.

When you validate applications in the Data Director Configuration Manager, if the validation messages run into multiple lines, the complete message is not visible.

Saved query columns use the package attribute for the column instead of the subject area attribute, which causes errors during search.

When you create a merge task and select a record to merge, the lower RowId Object value incorrectly appears in the Merge Preview.

After you open a task, you cannot see updated data.

In the Hierarchy Manager, when you manage a relationship and try to enter a value in the cust col field, the value reverts back to the default value.

When you use the Hierarchy Manager to create an entity, the entity does not display in the canvas.

When you create a record, potential matches do not appear.

You can edit a child record and a grandchild record at the same time. If you apply the edit to the grandchild record, but cancel the edit for the child record, a NullPointerException is generated.

In an Oracle database environment, when you open the event details from the

History

view, the following error occurs:

ORA-01722: invalid number

In the task inbox, you cannot filter tasks by the creation date.

In the

XREF

view, the search runs with administrator privileges instead of the logged in user privileges.

Merge task actions are disabled for users with uppercase user names.

In all the data views, white space is not preserved in the data fields.

If you exceed the maximum length of a text field, no validation error is displayed.

In the

History

view, when you try to view an event detail, an error might occur.

In applications with multiple subject areas, tasks assigned to a user do not appear in the task inbox.

When you run a search query with a specified effective date, the search results display incorrect values for records from a child subject area.

Users cannot open the tasks that are created by the secondary workflow engine.

When lookup columns from a child table are included in an advanced search query, the search result does not contain the values of the lookup field from the child table.

After you create a record, you cannot edit or save the record.

You cannot use a custom profile or multithreading to export search results.