The

B2B Data Exchange

Dashboard does not launch when you log in with a password that contains special characters.

When you import an MFT endpoint and choose not to import the system-generated workflows for the endpoint, the import operation succeeds. However, if you import an endpoint with no associated workflows, the import causes inconsistencies in the

B2B Data Exchange

repository.

For an Informatica Intelligent Cloud Services mapping that is created to integrate with a

B2B Data Exchange

endpoint, the tab delimiter formatting option does not work.

For an Informatica Intelligent Cloud Services mapping that is created to integrate with a

B2B Data Exchange

endpoint, the fixed width formatting option does not work.

For an Informatica Intelligent Cloud Services mapping that is created to integrate with a

B2B Data Exchange

endpoint, the escape character formatting option does not work.

When you try to test an SMTP test connection in

B2B Data Exchange

, the test fails when the

From Name

field contains spaces.

If you change the value of the system property

dx.iics.runtime.environment

during runtime, the change does not apply as

B2B Data Exchange

creates connection with the previous runtime environment value.

The

B2B Data Exchange

Archive Accelerator deletes data from the

DX_CORRELATION

table when

DX_CORRELATION.OPENING_EVENT_ID = EVENT.EVENT_ID

for data that has met the default selection criterion and business rules. However there is no validation check on the

CLOSING_EVENT_ID

parameter in the

DX_CORRELATION

table.

The

B2B Data Exchange

migration tool cannot retrieve a Local Listener Certificate when the

Override Local Listener Certificate

property is not configured.

For an MFT Receive endpoint with a regular expression pattern, if you select the

Regular Expression Partial Match

option, clear the regular expression, and then try to save the endpoint, you receive an error message.

When you try to download a large directory (20 GB and up) with the Informatica File Transfer Portal Secure Folder download, it might fail.

You cannot delete an MFT Connection in the

B2B Data Exchange

Operation Console if you are not assigned the Edit Endpoint privilege.

If you create two portal parameters and one is dependent on the other, both might display as disabled in a profile, rather than just the dependent parameter.

When you open the

B2B Data Exchange

Operation Console in the Edge browser, you cannot scroll to the last line of the

Details

section of the

Event List

page.

When you apply an endpoint file pattern regular expression in Windows with "/" in the file path, files for that endpoint will not be taken.

If you create a File Event event type rather than a File Level Event event type, you cannot reprocess the resulting File Event events.

When you create a new portal user and click

Save and Send Invitation

and then

Save

, the link in the invitation email displays an error.

If you exported all DX entities and then imported them after upgrade to this release, the obsolete SFE scheduler is added and displayed with DX schedules.

When you delete a partner or account with the

B2B Data Exchange

Operation Console and then import a partner or account which has same name, the Operational Data Store Event Loader might fail.

When you define an Managed File Transfer endpoint with the

B2B Data Exchange

Operation Console in a Chrome browser, the Managed File Transfer browser might not work correctly.

When you view the

B2B Data Exchange

Partners Portal with a Microsoft Internet Explorer version 10 and version 11 browser in compatibility mode, the content is not shown.

When you view the

B2B Data Exchange

Dashboard component with a Microsoft Internet Explorer version 10 and version 11 browser in compatibility mode, and then try to filter the content, the filtering might not work.

The

B2B Data Exchange

Operation Console lists event-types that are relevant for Data Integration Hub.

When you use

B2B Data Exchange

with Informatica platform authentication, user synchronization fails if you change the case of a user name in the Informatica domain. For example, if you changed the user name from

JohnSmith

to

johnsmith

, the Informatica domain handles the updated user name as a new user account. However,

B2B Data Exchange

handles the updated user name as a duplicate user account.

To change the

B2B Data Exchange

server RMI port number on a Windows operating system, you must change the port number in both copies of the dx-configuration.properties file and in the wrapper.conf file. For more information about changing default port numbers, see the

B2B Data Exchange

Installation and Configuration Guide

.

When you import a partner to the Operation Console and choose not to import profiles, the import process imports associated schedules for the profiles.

B2B Data Exchange

stores operational data store JDBC connection properties in the dx-configuration.properties file in addition to

B2B Data Exchange

system properties.

You cannot change the category management mode for a partner or a profile with the Web Service API.

In the

Tasks

panel of the Dashboard, users without access to all categories cannot view pending approval requests for partners without categories. Pending requests for accounts without categories are accessible by users with access to the related partner categories.

In the

Unresolved Errors

panel of the Dashboard, if you enter a value lower than 1 in the time frame field, the panel displays the value as a negative number.

If you log in to

B2B Data Exchange

with Informatica domain authentication, a NotSerializableException error may appear instead of a Login Failure error.

You cannot use an opening parenthesis character in the file name pattern for Managed File Transfer endpoints.

You cannot use control characters with values lower than

ASCII 0x20

in partner and in account properties.

If you delete one or more event attributes from a workflow, delayed processing rules for associated profiles still contain the deleted event attributes.

If you create a delayed processing rule for a profile that contains event properties with incorrect or incomplete default values, B2B Data Exchange might enable the

Delay All Events

processing rule.

If you use Managed File Transfer and you move the

B2B Data Exchange

repository to a different machine, Managed File Transfer does not replace the database connection.

The operational data store event loader does not load events that

B2B Data Exchange

processed during the last hour before daylight savings time begins.

You cannot use the DX_Aggregate transformation in a PowerCenter session with multiple partitions.

When you reprocess an event created with a default source document that was dropped into an endpoint configured for Pass by Reference, extra characters are appended to the source file name in the Input Message Log.

When you install

B2B Data Exchange

with Managed File Transfer on a Linux or UNIX platform and you select HTTPS as the protocol, the Managed File Transfer process does not terminate when the installer terminates.

When the developer uses the Profile Parameters custom transformation to define a workflow parameter that starts with "DX", the output port for this parameter is always null and the transformations fail.

When you install

B2B Data Exchange

with SQL server and use both the instance name and the port,

B2B Data Exchange

fails and the following error message appears in the log:

In you search for a monitor for a specific partner using the advanced search, in the next search you will not see all the existing partners.

If you attempt to reprocess or resend an empty file, you receive an unclear error message.

If a document is passed by reference to an outbound endpoint, selecting a different file to resend fails.

When you preform an advanced search on an on-boarding checklist, if you select a Status and select OR as the operation, the search does not work.

When configuring the file endpoint to wait for file stabilization, if a file with the same name and size is added with a long time to wait,

B2B Data Exchange

might not wait for the file to finish.

If a file cannot be read and the option to wait for the file size to stabilize is on, there is no error event.

B2B Data Exchange

fails to route files if two endpoints use the same account but only one is enabled.