If you set a timeout value or set the input and output connection ID value, importing an MLLP project from version 10.5.3 to MFT versions 10.5.0 or 10.4.0 fails. Also, if you set a timeout value for a project, importing the project from version 10.5.3 to version 10.5.0 or 10.4.0 fails.

After you upgrade MFT from version 10.2.2 to any later version, MFT doesn't connect to PowerCenter.

An internal error appears when you provide the category as part of the request body while listing projects using a Project List REST API.

After you upgrade MFT to version 10.5.3, the following log4j files are available in the

MFT/server/config

location:

log4j.xml
log4j2.xml

When you run the

Notify Consumer Task

from Managed File Transfer, the MFT

Completed Jobs

grid doesn't display the endpoint name.

After you upgrade MFT to version 10.5.3, the OEM projects are added to the following folder:

When you run a Password-Protected Excel project in Managed File Transfer, the project might fail.

When you update the web user password using the update web user REST API, a success message appears. However, the password isn't updated.

Managed File Transfer doesn't log an HTTP request in the debug logs with OKTA login.

B2B Data Exchange

displays an internal server error message when you access the Managed File Transfer dashboard from the B2B Data Exchange dashboard and then log out and log in from the same login page.

B2B Data Exchange

displays an error message when you unzip .jar files during startup.

In the B2B Data Exchange dashboard, select a partner and an associated account as the filter and apply it as the default setting. If you navigate to other pages and back to the dashboard, the reports don't reflect the default settings.

In the B2B Data Exchange dashboard, when you click a hyperlink in a panel, the hyperlink works as expected and navigates to the Event List page or the Authorization page. However, when you navigate back to the dashboard, the console does not display the blue color for the hyperlink, but the hyperlink works as expected.

In the B2B Data Exchange console, when you click the

Set as default

button after selecting the filters, a confirmation message is not displayed and the

Set as default

button is not disabled.

B2B Data Exchange generates a system error event when you process more than 100 files in a Windows High Availability environment.

If you start B2B Data Exchange and Informatica Managed File Transfer using Windows services with TLS version 1.3, the HTTPS pages for B2B Data Exchange and Informatica MFT fail to load. However, the HTTPS pages load when you start B2B Data Exchange and Informatica MFT from a command prompt.

Managed File Transfer doesn't consider the files in the subdirectories and folders for an SCP MGet task even if the

Recursive

option is set to

true

.

Users who don't have the View Events privilege can view the total number of events on the report displayed in the dashboard.

When you stop the

B2B Data Exchange

application on some Linux or AIX environments, the Active MQ service fails to stop and displays an error message.

When you run a scheduled MFT endpoint and import or export schedules simultaneously, Data Exchange fails to respond.

When you place a file which has the Informatica Intelligent Cloud Service profile associated with File receive endpointst, a IICS connection appears. If you replace the file in IICS after moving the docstore, the job fails.

During silent installation or upgrade, if you select to use a new metadata repository, you might receive the following message:

B2B Data Exchange

generates a system error event when you process more than 1000 files in Windows environment.

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

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.

The

B2B Data Exchange

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

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.

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

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.

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

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.