Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.18.7
API Replication service	1.27.0
Endpoint services	3.18.3

Issue Resolution	ID
Upgrades to CloudHub 2.0 applications no longer fail due to naming collisions across environments.	W-23687405
SFTP Java 17 endpoint templates now use SFTP Connector version 2.7.2 to prevent stale heartbeat connections from accumulating on servers.	W-23744879

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.18.7
API Replication service	1.27.0
Endpoint services	3.18.2

Issue Resolution	ID
PDF generation quality for AI summaries of B2B data payloads is improved.	W-21744792
AI summaries of B2B data payloads are improved to prevent text from being cut off.	W-21684725
AI summaries of B2B data payloads now generate correctly regardless of the user’s organization permissions.	W-22969312
Message flow links are now uniquely labeled per partner for screen readers.	W-15464206
The Activity page now prevents pagination inconsistencies by ensuring new messages and transmissions aren’t loaded unless you explicitly refresh the results.	W-21320963
Custom message attributes are now shown correctly for transmission scenarios that end in a failed state.	W-22242884
RTFs clusters associated with all environments are now listed in the selection dropdown.	W-21614334
Tracking updates are now reported correctly after a failure to sign an MDN response in certain compression scenarios.	W-21615522
The Repetition Separator option is now available when configuring EDI versions later than 4010.	W-21357023
Creating an EDI configuration with an ID that already exists now returns a `409 Conflict` response instead of a `500 Internal Server Error`.	W-22043583
Outbound message mapping errors are now displayed correctly even when the mapping doesn’t output the expected content type.	W-20984628
Adaptive compression now works correctly for CloudHub 2.0 inbound endpoints under certain conditions that previously caused failures.	W-22819794
Adaptive compression now compresses messages correctly when the message sent to the queue is large.	W-23018476
The Manage Deployments process now detects failures and reports issues correctly in migration rollback scenarios.	W-21525836
Large replay batches no longer trigger Anypoint MQ rate limits.	W-21764442
Connected app names for Anypoint MQ now include the environment ID, preventing naming collisions across environments.	W-21782746
Internal transmission reporting tasks are now recovered correctly in scenarios that previously caused them to hang.	W-20834743
New features that require a Mule runtime engine upgrade are now grayed out rather than hidden, so you can see what requires an upgrade.	W-22863183
Users with only the View Activity permission can now successfully navigate the Activity page.	W-21723489

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.17.0
API Replication service	1.26.0
Endpoint services	3.17.0

Issue Resolution	ID
The Document Processing Service (DPS) runtime application is no longer deleted during specific migration scenarios, ensuring the service remains active if a deployment fails.	W-21139063
The search filter on the Maps page now correctly shows all matching results.	W-21105459
The AS2 inbound application no longer redeploys unnecessarily during map changes, target endpoint updates, or when redeploying an outbound message flow whose expected acknowledgment uses an AS2 endpoint.	W-21195421
Updating environment settings no longer resets a remapped MQ region, preventing subsequent deployment failures.	W-21042258
The View Payload button in outbound transmission details now correctly opens the payload content when a Payload view URL is configured.	W-21313286
Audit log payloads are now reduced when creating entities.	W-21077016
Target payloads are no longer saved as compressed to content storage in CloudHub 2.0 environments.	W-21448452

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.16.1
API Replication service	1.25.0
Endpoint services	3.16.5

Issue Resolution	ID
Updating an X12 configuration in the UI no longer causes an error when the configuration was originally created via an API without a partner ID.	W-19135979
Renaming an inbound message flow using a third-party AS2 connection no longer causes an invalid flow configuration error during deployment.	W-20231427
The application ingress URL displayed on HTTP and AS2 endpoints in CloudHub 2.0 now matches the deployment URL in Runtime Manager.	W-19639638
Accessing a new environment without deployment settings in Partner Manager or Access Management no longer causes an internal server error.	W-20219817
Deploying a new inbound message flow using an existing third-party AS2 connection no longer causes the AS2 inbound application to redeploy unnecessarily.	W-20231483
Configuring an HTTPS endpoint with the default port 443 no longer results in an incorrect base path or a missing URL in the UI.	W-19768952
Messages with outbound delivery errors are now successfully stored in payload storage.	W-19639785
A mismatch between the content type and payload in outbound messages no longer causes the message to get stuck in a processing loop.	W-20091731
Detailed logs are now generated when custom EDI schema validation fails and the file is not written to disk.	W-19630808
Outbound templates for AS2, FTP, and SFTP now display specific failure reasons instead of generic error messages.	W-19581703
Partner Manager now preserves custom URL path rewrites configured in Runtime Manager when the Preserve Public URL option is selected.	W-20838447
Users with the appropriate role can now create endpoints that contain certificates.	W-20896207
Endpoint settings are now applied correctly and applications are recreated for all deployments, even when obsolete templates are present during upgrades or migrations.	W-20812761
Outbound message attributes are now shown when mapping errors occur.	W-19812476
When an SFTP server issues frequent connection resets, the CloudHub 2.0 outbound SFTP runtime application now reliably processes messages.	W-21077401

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.2
API Replication service	1.24.0
Endpoint services	3.15.2

Issue Resolution	ID
AS2 endpoints configured with the HTTP protocol now deploy correctly after CloudHub 1.0 to CloudHub 2.0 migration.	W-20391091
Navigating to messages related to a transmission now works as expected and no longer results in an `Unable to load the content` error.	W-20684714
The Host field for CloudHub 2.0 environment settings no longer includes options for CloudHub 1.0 domains.	W-19812847
Message flow deployments no longer fail when a large number of applications are present in CloudHub 2.0 environments.	W-20833834

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.2
API Replication service	1.24.0
Endpoint services	3.15.2

Issue Resolution	ID
Partner Manager now preserves user-defined public URLs for AS2 or HTTP inbound endpoints in CloudHub 2.0 via an endpoint option.	W-20017417
Custom message attributes for inbound transactions are now visible even when there is a mapping error.	W-19812476
The default search window for the Activity page is now set to the past three hours.	W-20517517

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.1
API Replication service	1.24.0
Endpoint services	3.15.2

Issue Resolution	ID
CloudHub 1.0 inbound templates are now working correctly with API Manager in Mule runtime 4.9.	W-20159059

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.1
API Replication service	1.24.0
Endpoint services	3.15.1

Issue Resolution	ID
Partner Manager no longer generates duplicate ISA and GS Control Numbers in CloudHub 2.0 deployments using multiple replicas.	W-20091679

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.0
API Replication service	1.24.0
Endpoint services	3.15.1

Issue Resolution	ID
FTP Connector is updated to version 2.0.1 and now ignores blank folder names for more stable processing.	W-19774360, W-19774360

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.15.0
API Replication service	1.24.0
Endpoint services	3.15.0

Issue Resolution	ID
Message flows now show as expected in the message flows popup.	W-19484400
You can now see the payload for failed transmission steps, which simplifies debugging and helps you pinpoint the exact cause of an error.	W-17487158
Outbound HTTP messages now show the failure reason at the message level.	W-19250288
Error messages are now clearer for payload storage configuration issues and other errors across Partner Manager.	W-19455311
Failed payloads are now logged and persisted when XML or JSON schema validation fails.	W-19438092
Transmission statuses now accurately update to Error and no longer get stuck in the Processing state after multiple inbound X12 or EDIFACT validation failures.	W-19312257
The trash can icon in the Schema field no longer hides the first character of the schema file name when configuring a JSON or XML Target at Host message.	W-18895852

Application or Service	Version
Mule	4.6.0 with Java 8, 4.9 with Java 17

Runtime service	Version
Document processing service	3.14.0
API Replication service	1.23.0
Endpoint services	3.14.2

Issue Resolution	ID
Paths can now be reused across HTTP inbound endpoints.	W-18722293
You can now change the deployment target from CloudHub 1.0 to CloudHub 2.0 for organizations created before Partner Manager version 2.18.0.	W-18715090
CloudHub 1.0 entitlements are no longer required for CloudHub 2.0 in Runtime Fabric settings.	W-18572633
CloudHub 2.0 vCore validation now works as expected during deployments.	W-18395858
The HTTPS option is now hidden in Partner Manager when creating AS2 Receive from Partners endpoints with CloudHub 2.0 because the option is now configured directly in CloudHub 2.0 instead of in Partner Manager.	W-18169399
Partner Manager no longer attempts to send data to the VM for recovery when Anypoint MQ returns a `413 - Payload Too Large` error.	W-16895010
`AccessGrant` is no longer removed when editing an inbound SFTP endpoint that uses Basic or Identity key authentication.	W-18811033
Deployments no longer time out under certain circumstances.	W-18507276

Application or Service	Version
Mule	4.6.0 with Java 8

Runtime service	Version
Document processing service	3.13.0
API Replication service	1.22.0
Endpoint services	3.13.5

Issue Resolution	ID
Partner Manager now allows you to create message flows with different custom schemas of the same EDI message type even if the message flows are configured with different third-party partners.	W-18892873

Application or Service	Version
Mule	4.6.0 with Java 8

Runtime service	Version
Document processing service	3.13.0
API Replication service	1.22.0
Endpoint services	3.13.5

Issue Resolution	ID
All supported X12 version 4030 message types now show in the Message type dropdown.	W-18347930
Inbound AS2 messages with signatures that contain a non-standard carriage return no longer fail.	W-18489908
Apply settings now work correctly for CloudHub 2.0 environments.	W-18438558
Environment upgrades no longer fail in the first attempt due to Anypoint MQ queues.	W-18367471
The replay and acknowledgment reconciliation task performance is improved.	W-18559313

Application or Service	Version
Mule	4.6.0 with Java 8

Runtime service	Version
Document processing service	3.13.0
API Replication service	1.22.0
Endpoint services	3.13.0

Issue Resolution	ID
Issues preventing deployments to some CloudHub 2.0 regions are now resolved.	W-18380406
Payload view now works as expected in EU control plane environments for newly created payload storage configurations.	W-18382545
The issue with creating AS2 and HTTPS send endpoints with port numbers from the partner profile page since the 2.22.0 release is now resolved.	W-18403689

Application or Service	Version
Mule	4.6.0 with Java 8

Runtime service	Version
Document processing service	3.13.0
API Replication service	1.22.0
Endpoint services	3.13.0

Issue Resolution	ID
You can now navigate to the messages list as expected when viewing transmission details for 997 acknowledgments.	W-17709667
Nonsearchable custom message attributes are no longer included in the Message attribute dropdown.	W-16799143
Inbound AS2 messages now deploy as expected for message flows with acknowledgments enabled.	W-17065605
The Date Range filter no longer fails to display all transmissions in the selected date range in some scenarios.	W-17395944
The Custom message attributes section no longer indicates there are no attributes when the section is collapsed, and attribute values are no longer truncated.	W-17654456
Messages no longer fail with message flow routing errors when associated message flows involving third-party connections are created via the Partner Manager platform API.	W-17114370
The API response performance for deployments is now improved.	W-17067909
Inbound flows for CSV Target at Host message types no longer add extra columns for items in a list that use non-comma separators.	W-18191895

Application or Service	Version
Mule	4.6.0

Runtime service	Version
Document processing service	3.12.2
API Replication service	1.21.1
Endpoint services	3.12.1

Application or Service	Version
Mule	4.6.0

Runtime service	Version
Document processing service	3.12.1
API Replication service	1.21.0
Endpoint services	3.12.0

page. For more information, see [FTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target). - AS2 inbound endpoints that are configured on a partner’s profile. For more information, see [AS2 インバウンドメッセージの受信設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/as2-encoding). For messages received via HTTP/s endpoints, the charset parameter in the HTTP request’s `Content-Type` header is now applied as the inbound document’s default encoding. - Custom application properties Custom application properties configured in Runtime Manager for applications deployed via Runtime Fabric are now retained when upgrading or redeploying. - Transaction updates performance The performance of transaction updates is improved. ### Fixed Issues

Issue Resolution ID

The Business Document Key field extracted from the reference mapping execution is now included in target files delivered to FTP and SFTP Target at host endpoints with a file name pattern containing the BusKey property.

W-13729500

You can no longer select latest when configuring the runtime version for Partner Manager in Access Management, but you can select a specific runtime version.

W-14497416

The value in the Custom message attribute field is now truncated after 199 characters.

W-14793863

When Custom X12 settings is selected in the X12 Settings section of an outbound message flow, Partner Manager now respects the value in the Substitution character field in the X12 Connector configuration. If the field is blank on the X12 Connector, then Partner Manager applies the substitution character configured on the partner profile.

W-14875596

You can no longer modify the CloudHub deployment region for environments that contain active message flow deployments.

W-14990783

The Runtime Fabric deployment settings in Access Management now show the same application size parameters that are configured in the Runtime Manager UI for Runtime Fabric deployments.

W-14406928

The Runtime Fabric deployment settings in Access Management now show only the Runtime Fabric targets that are available for the selected environment.

W-14794249

The Message flows page now loads successfully if the deployment settings for the environment in Access Management aren’t configured.

W-14970387

## [](#2-19-7)2.19.7 **June 14, 2024** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.3
API Replication service	1.19.0
Endpoint services	3.10.2

### [](#dependent-components-used-26)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

The ISA11 repetition separator in the outbound functional acknowledgment is now mapped from the original inbound X12 data payload.

W-15962484

## [](#2-19-6)2.19.6 **May 30, 2024** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.2
API Replication service	1.19.0
Endpoint services	3.10.2

### [](#dependent-components-used-27)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

Partner Manager now supports additional X12-ISA identifier qualifiers.

W-15762564

Styling changes are made to dropdown lists to improve the look and feel of long descriptions.

W-15804911

## [](#2-19-5)2.19.5 **May 16, 2024** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.2
API Replication service	1.19.0
Endpoint services	3.10.2

### [](#dependent-components-used-28)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

AS2 outbound messages no longer send an additional subject header with a null value.

W-15727463

## [](#2-19-4)2.19.4 **May 7, 2024** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.2
API Replication service	1.19.0
Endpoint services	3.10.1

### [](#dependent-components-used-29)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

The accessibility standards for screen readers in the Partner Manager interface are now improved.

W-15534717

## [](#2-19-3)2.19.3 **April 10, 2024** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.2
API Replication service	1.19.0
Endpoint services	3.10.1

### [](#dependent-components-used-30)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

Outbound EDI transmissions with multiple transactions now create multiple message records.

W-15270165

The acknowledgement reconciliation process now waits for 35 minutes instead of 6 minutes for the corresponding outbound transmission record to be created before failing.

W-15306986

## [](#2-19-2)2.19.2 **March 11, 2024** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Starting with this version, the runtime version configuration in the Access Management settings for Partner Manager is updated to Mule 4.4.0. This defaults all Partner Manager deployments to that runtime version.

Runtime service	Version
Document processing service	3.10.2
API Replication service	1.19.0
Endpoint services	3.10.1

### [](#dependent-components-used-31)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

The UI styles for the Select and View payload buttons are now fixed.

W-14746447

The batch reporting performance for outbound transmission messages is now improved.

W-14801233

Substitution characters configured in custom validation settings for outbound X12 message flows are now honored.

W-14875596

The Payload view now works when the storage API uses a self-signed certificate for the TLS context.

W-14921046

The handling of transmission recoveries for XML and JSON formats is now improved.

W-15159433

## [](#2-19-1)2.19.1 **February 6, 2024** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.1
API Replication service	1.19.0
Endpoint services	3.10.1

### [](#dependent-components-used-32)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution

The configuration for RTF application sizing is now consistent between Partner Manager and Runtime Manager.

W-14406928

RTF configuration settings now show only those Runtime Fabrics that are associated with the selected environment.

W-14659614

Editing SFTP endpoints that use Basic and Identity Key authentication now works as expected.

W-14838612

Searching Partner Manager public APIs by using spaces and date filtering now works as expected.

W-14872922

## [](#2-19-0)2.19.0 **January 25, 2024** ### What’s New You must upgrade the runtime templates of your environment to 2.19.0 before you can begin using the new features in this release. - Improved certificate management You can now select the type of certificate (private keypair, public certificate, or identity key) to add to the host, partner, or third-party connection profiles with a consistent experience. - SSH identity-key-based authentication for SFTP endpoints You can now select the additional authentication types identity key and basic + identity key, to connect with internal and external SFTP servers that require SSH-key-based authentication. Previously, Partner Manager supported only basic (username, password) authentication for SFTP endpoints. You can also update identity keys and trigger the redeployment of the endpoints that use them. - Improved TLS context for outbound AS2 endpoints You can now configure the TLS context in outbound AS2 endpoint configurations to use a self-signed SSL certificate or allow an insecure connection (recommended only for testing purposes). Previously, you could configure only CA-signed certificates for outbound AS2 endpoints. - Support for additional EDIFACT versions You can now configure EDIFACT message types with versions s93a, d16a, d16b, d17a, d17b, d18a, and d18b. - New **About** section for the host profile You can now add additional information such as your company’s logo, contact information, and more to your organization’s host profile. - Custom application properties configured in Runtime Manager for CloudHub-deployed applications are now retained during upgrades and redeployments. - You can now configure a substitution character in X12 **Send** settings to replace any characters in the outbound data payload that are used as other delimiter characters. - You can now have multiple SFTP send endpoints with the same host, credentials, and path, but with different file naming patterns. - Performance is improved for runtime applications deployed to Runtime Fabric. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.10.1
API Replication service	1.19.0
Endpoint services	3.10.1

### [](#dependent-components-used-33)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues

Issue Resolution ID

Deployment failures no longer occur due to an incorrect vCore balance check.

W-10551147

You can no longer delete endpoints that are used only in the X12 or EDIFACT acknowledgment settings in a partner profile. This change prevents data processing issues.

W-13833027

The transmissions search filter for the acknowledgment status Sent now shows matching search results.

W-13835609

Self-signed certificates associated with payload storage endpoint configurations no longer remain linked to the endpoint after the certificate type is changed to a CA-signed certificate or insecure connection.

W-13875923

The delete button is no longer enabled when search filters are applied in the Message Types section of the host profile.

W-14080953

Transmission recovery is no longer retried indefinitely when outbound AS2 transmissions fail.

W-14330423

Search filters on the host page now handle spaces correctly.

W-14397901

The management of basic authentication credentials for outbound AS2 endpoints on Anypoint Platform is now improved.

W-14575004

SFTP inbound endpoint polling no longer hangs when JMS (ActiveMQ) connectivity is lost.

W-14765379

### Known Issues

Known Issue

Workaround

You must reenter the password when editing an SFTP endpoint that has the basic and identity key authentication type. Saving the changes with the password field left blank results in a deployment failure.

None

W-14838612

## [](#2-18-7)2.18.7 **January 16, 2024** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.5
API Replication service	1.18.4
Endpoint services	3.9.2

### [](#dependent-components-used-34)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

The runtime service now has an extended timeout for Tracking API calls.

W-14801162

## [](#2-18-6)2.18.6 **December 11, 2023** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.5
API Replication service	1.18.3
Endpoint services	3.9.2

### [](#dependent-components-used-35)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

Outbound transmissions with multiple messages now process correctly when custom message attributes are defined in the message type.

W-14534597

## [](#2-18-5)2.18.5 **December 4, 2023** This version requires a runtime template update if you deploy Partner Manager runtime applications to Anypoint Runtime Fabric. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.3
API Replication service	1.18.3
Endpoint services	3.9.2

### [](#dependent-components-used-36)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

The Partner Manager runtime templates now use active-mq 5.15.16 because of security vulnerabilities with active-mq 5.15.15.

W-14495961

## [](#2-18-4)2.18.4 **November 6, 2023** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.2
API Replication service	1.18.1
Endpoint services	3.9.1

### [](#dependent-components-used-37)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

The Partner Manager upgrade process no longer erroneously starts unrelated applications based on certain naming conventions.

W-14315662

The Private port (when deploying to Anypoint VPC) checkbox now appears in the New Endpoint dialog when creating AS2, HTTP, and HTTPS receive endpoints. This issue was introduced accidentally in v2.18.2.

W-14426229

## [](#2-18-3)2.18.3 **November 1, 2023** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.2
API Replication service	1.18.1
Endpoint services	3.9.1

### [](#dependent-components-used-38)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

Message flow deployments that reference the same endpoints are no longer left in a locked state, which prevented them from being deployed.

W-14316022

Some organizations that were previously unable to access Partner Manager under MuleSoft’s new usage-based pricing and packaging can now access it.

W-14406061

## [](#2-18-2)2.18.2 **October 24, 2023** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.2
API Replication service	1.18.1
Endpoint services	3.9.1

### [](#dependent-components-used-39)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

Anypoint MQ regions are now set correctly when configuring new environments.

W-14352365

## [](#2-18-1)2.18.1 **October 17, 2023** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.2
API Replication service	1.18.1
Endpoint services	3.9.1

### [](#dependent-components-used-40)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

When saving environment-level deployment settings for older business groups, you no longer receive an error.

W-14286942

Partner Manager now applies custom EDI schemas to validations for messages sent to partners if the partners have multiple outbound message flows that use both custom and standard schemas.

W-14309676

## [](#2-18-0)2.18.0 **October 10, 2023** ### What’s New This version requires a runtime template update.

Starting with this version, on-premises standalone deployments are no longer supported.

### [](#enhanced-partner-manager-deployment-options)Enhanced Partner Manager Deployment Options This release contains enhanced Partner Manager deployment options. #### [](#runtime-fabric-deployment)Runtime Fabric Deployment You can now configure Anypoint Runtime Fabric as a deployment target for Partner Manager. This enables you to execute B2B transaction-processing workloads in a Kubernetes cluster that you create, configure, and manage. To leverage this new deployment option, you must set up an ActiveMQ messaging broker on your preferred infrastructure and configure the connection parameters in Partner Manager’s deployment settings. The Runtime Fabric deployment option was validated on Amazon Elastic Kubernetes Service (EKS). Deploying Partner Manager runtime applications on other Runtime Fabric infrastructure is currently not supported.

When deploying Partner Manager runtime applications to Anypoint Runtime Fabric, the length of the AS2 keystore can’t exceed 1024 characters, which limits the algorithm option to SHA1.

#### [](#environment-level-deployment-settings)Environment-level Deployment Settings You can now configure Partner Manager deployment settings such as the deployment target, runtime version, deployment region, and runtime capacity allocation at the individual environment level. In previous releases, you could configure deployment settings only at the business-group level. #### [](#new-ui-for-configuring-deployment-settings)New UI for Configuring Deployment Settings You now configure Partner Manager deployment settings in a new Access Management UI. #### [](#more-information)More Information For more information about Partner Manager deployment options, see [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/jp/partner-manager/latest/deploy-partner-manager). ### [](#other-enhancements)Other Enhancements - The deployment of each environment is now shown on the Partner Manager page. - You can now remove schema files that are attached to previously-configured JSON and XML message types if you don’t need schema validation on payloads. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.9.1
API Replication service	1.18.1
Endpoint services	3.9.1

### [](#dependent-components-used-41)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution ID

You can no longer use the same character for more than one purpose when configuring inbound CSV message types.

W-13577974

View payload links in the message details view are now easy to click, even when the corresponding file name is very long.

W-13695625

The error response code when Access Management authentication is down is now correct.

W-13806543

Partner Manager now applies schema validation to transactions in outbound message flows with JSON or XML as the target message format when a schema file is attached to the message type definition.

Because this type of validation did not happen in earlier releases, the transactions in existing message flows of this type might fail if the message payload fails during schema validation. If you believe that this could happen, consider removing the schema file association in the message type definition.

W-13915947

The outbound AS2 runtime application is now updated when you deploy a message flow after a host AS2 keystore update.

W-13968139

Functional Acknowledgements (997) generated in response to inbound EDI X12 interchanges with more than one functional group are no longer duplicated.

W-13993209

Outbound messages no longer get stuck in the Processing status after they are delivered successfully to the target endpoint.

W-14049820

## [](#2-17-0)2.17.0 **July 27, 2023** ### What’s New You must upgrade the runtime templates of your environment to 2.17.0 before you can begin using the new features in this release. These features are available only for CloudHub runtime deployments. ### [](#transmission-replay)Transmission replay - You can now replay failed or successfully-delivered B2B transmissions. When you replay a transmission, Partner Manager reprocesses the source payload as if it was received from the source again. The transmission goes through the validation, acknowledgement, transformation, and routing steps configured in the message flow at the time of replay. - Original transmissions that were replayed at least once and transmissions and messages that were created due to a transmission replay have indicators to help you understand the user actions performed on the transmissions. - You can navigate between the original transmission record and its associated replayed transmission records. - You can filter the transmission search results to show only the transmissions that contain at least one replay. - Platform administrators can see the history of user actions related to repalying transmissions in the Anypoint Access Management audit logs. ### [](#csv-delimited-file-support)CSV (Delimited) File Support - You can now configure CSV as the message format for all usage types: Receive from partners, Target at host, Source at host, and Send to partners. ### [](#acknowledgement-status-enhancements)Acknowledgement Status Enhancements - When a functional acknowledgement received from a partner contains the error code `E`, the corresponding outbound transmission’s ack status is set to `Accepted with errors`. - When a functional acknowledgement received from a partner contains the error code `P`, the corresponding outbound transmission’s ack status is set to `Partially accepted`. - When Partner Manager can’t deliver the functional acknowledgement for an inbound transmission, the ack status of the transmission is set to `Failed to send`. ### [](#other-enhancements-2)Other Enhancements - You can now configure hex codes as separator characters for outbound EDIFACT and X12 messages. You do this either from the partner’s profile or via custom settings in outbound message flows. - You can now configure JSON and XML message types without an associated schema. When processing message payloads for message types that don’t have an associated schema, no schema validation is performed. - Partner Manager now streams the data when it loads large message payloads to the payload view of the UI. - Partner certificate statuses and related color coding are improved. ### Compatibility

Application or Service

Version

Mule

4.4.0

Runtime service	Version
Document processing service	3.8.0
API Replication service	1.17.0
Endpoint services	3.8.0

### [](#dependent-components-used-42)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

The runtime template upgrade process no longer involves multiple redeployments of the same endpoint application. This results in faster upgrade completions.

W-10550475

You can no longer use spaces when configuring the base path of HTTP receive endpoints because the use of spaces in this context can cause errors.

W-12276497

Endpoints that were just edited no longer disappear from the current list view.

W-11866200

Partner Manager now validates the formatting of host names specified in SFTP and FTP endpoint configurations.

W-12731777

Partner Manager now persists a payload received via FTP as a failed transmission if the filename prefix doesn’t match a configured message type.

W-13081180

Partner Manager now compresses schema files when storing them in an object store. This enables the support of large schemas.

W-13536066

## [](#2-16-2)2.16.2 **July 5, 2023** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3.0, 4.4.0

Runtime service	Version
Document processing service	3.7.3
API Replication service	1.16.1
Endpoint services	3.7.0

### [](#dependent-components-used-43)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

Partner Manager now generates a valid functional acknowledgement for an EDI v003010 transaction.

W-12776825

## [](#2-16-1)2.16.1 **June 27, 2023** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3.0, 4.4.0

Runtime service	Version
Document processing service	3.7.2
API Replication service	1.16.1
Endpoint services	3.7.0

### [](#dependent-components-used-44)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues

Issue Resolution

When reconciling an inbound 997 functional acknowledgment, Partner Manager now uses the function group ID to match the corresponding outbound transaction.

W-12776539

When deploying an inbound message flow for a new partner with an AS2 receive endpoint, the AS2 inbound runtime application is now updated with the certificate of the partner or third-party connection.

W-13085911

The date picker now works in the Firefox browser.

W-13204965

The message type filtering on modal selections now works as expected.

W-13608847

The segment line ending field for an Edifact outbound configuration now works as expected.

W-13609095

## [](#2-16-0)2.16.0 **May 2, 2023** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3.0, 4.4.0

Runtime service	Version
Document processing service	3.7.0
API Replication service	1.16.1
Endpoint services	3.7.0

### [](#dependent-components-used-45)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New ### [](#search-filter-enhancements)Search Filter Enhancements - You can now search by either transmission ID or message ID in the messages search page. - You can now search by transmission ID in the transmissions search page. - You can now navigate from the transmissions list and transmission details pages to the messages list page to view the list of messages contained within the same transmission. ### [](#source-message-attributes)Source Message Attributes Attributes such as the source file name, protocol, size, and headers, along with the transmission ID and message ID are now available in a predefined variable named `b2bMessageContext`. The attributes in `b2bMessageContext` are accessible during the execution of the message type reference mapping and the transformation mapping within the message flow execution. ### [](#other-enhancements-3)Other Enhancements - The new **Associated reference identifier** field on the New Endpoint dialog enables you to associate a partner reference ID with SFTP and FTP Receive from Partners endpoints that receive non-EDI messages. If configured, the partner reference ID is available in the `b2bMessageContext` variable. Partner Manager uses the ID to route the message via the appropriate message flow when it executes the message type reference mapping. - The new **Associated message type** field on the New Endpoint dialog enables you to associate a static message type with SFTP and FTP Receive from Partners endpoints that receive non-EDI messages. Specifying an associated message type overrides the need to prefix the file names with the message type ID. All files received via the endpoint are treated as the configured message type, regardless of the file name prefix. - The activity search time period selection now has a new date-time picker. - The new **Retry interval** and **Maximum retry attempts** fields on the New Endpoint dialog enable you to configure the retry interval and count for HTTP and HTTPS Send to Partners endpoints. - The new **Acknowlege every transaction** field in the X12 receive settings on the partner page enables you to configure a validation rule that requires Partner Manager to generate detailed acknowledgements. These acknowledgements include a separate AK2/AK5 (997) segment for every received transaction set, even when all transactions are accepted. - The new `expandCustomAttributes` query parameter is now available to use when calling the Partner Manager Tracking API messages resource. Set the parameter to `true` to receive the custom message attributes within the API response. - Performance in JSON and XML message processing and schema validation steps is now improved. ### Fixed Issues

Issue Resolution ID

Sporadic JSON and XML schema validation errors no longer occur.

W-10735624

Partner Manager now creates message records when outbound transactions fail in validation.

W-11294561

The AS2 certificate expiry date is now enforced when processing inbound and outbound AS2 messages so that Partner Manager rejects transmissions after the certificates expire.

You can disable the Enforce AS2 certificate expiration date field in the global AS2 receive and send settings in the host profile if your organization doesn’t need to enforce the expiry date.

W-11764062

You can now select HTTPS send endpoints with self-signed SSL certificates when editing an existing message flow.

W-12214761

The Technical Acknowledgement (TA1) section no longer shows as Processing when there is no actual TA1 sent in response to inbound EDI X12 transactions.

W-12266629

Changes to certificate configurations in the payload storage API configuration now take effect in the runtime services.

W-12500180

The character encoding override in EDIFACT receive settings now enables the processing of inbound data payloads with certain non-printable characters.

W-12659240

The Receive from Partners endpoint name is now displayed even when there are errors processing the received data payload.

W-12685704

## [](#2-15-3)2.15.3 **April 13, 2023** This version does not require a runtime template update. ### [](#compatibility-46)Compatibility

Application or Service

Version

Mule

4.3, 4.4

Runtime service	Version
Document processing service	3.6.2
API Replication service	1.15.0
Endpoint services	3.6.2

### [](#dependent-components-used-46)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### Fixed Issues

Issue Resolution

The performance of tracking updates is improved.

W-12733721

The default connection timeout values for FTP and SFTP receive endpoints is increased.

W-13004882

## [](#2-15-2)2.15.2 **March 22, 2023** This version requires a runtime template update. ### [](#compatibility-47)Compatibility

Application or Service

Version

Mule

4.3, 4.4

Runtime service	Version
Document processing service	3.6.2
API Replication service	1.15.0
Endpoint services	3.6.2

### [](#dependent-components-used-47)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New - Fonts in the GUI are updated to improve legibility, localization, and site performance. ## [](#2-15-1)2.15.1 **March 6, 2023** This version requires a runtime template update. ### [](#compatibility-48)Compatibility

Application or Service

Version

Mule

4.3, 4.4

Runtime service	Version
Document processing service	3.6.2
API Replication service	1.15.0
Endpoint services	3.6.1

### [](#dependent-components-used-48)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### Fixed Issues

Issue Resolution

The Deploy button is no longer enabled for endpoints with no updates.

W-12450398

Upgrading from versions older than 2.15 no longer results in sporadic partner identification errors during the upgrade.

W-12461023

Translated payloads with SFTP, FTP, HTTP, and HTTPS target endpoints are now visible even when there are failures in delivering the files to the endpoint.

W-12486096

Changes in the certificate settings of the payload storage API configuration now get deployed to the runtime service when a message flow is deployed.

W-12500162, W-12500180

Clicking the browser’s Back button after switching from the Transmissions view to the Messages view no longer causes an error.

W-12556405

Changes made to the Deploy HTTP/AS2 apps to private port option on the Partner Manager Settings page in Access Management are now saved.

W-12588215

## [](#2-15-0)2.15.0 **January 24, 2023** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3, 4.4

Runtime service	Version
Document processing service	3.6.0
API Replication service	1.15.0
Endpoint services	3.6.0

### [](#dependent-components-used-49)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New - You can now update endpoint configurations and deploy the changes with simple steps. Note: Before making endpoint updates, you must upgrade your runtime templates to the latest version. - Inbound HTTP endpoint applications now return the unique Partner Manager transmission ID in the HTTP response header, `x-apm-trx-id`. - Partner Manager is now compatible with Mule runtime 4.4. Note: To deploy your applications with Mule runtime 4.4, you must explicitly select Mule runtime 4.4 in the **Use latest version** option in the Partner Manager Settings page. - Seconds are now shown in transmission and message views. - Improvements in overall UI and cache performance in runtime applications for environments with a high volume of partners. ### [](#upgrading-to-mule-runtime-4-4)Upgrading to Mule Runtime 4.4 Partner Manager 2.15.0 is compatible with Mule 4.4. To take advantage of the new features and fixed issues, upgrade to the latest Partner Manager templates, and deploy runtime applications with Mule 4.4: 1. In Access Management, go to **Partner Manager Settings** and select either **Use latest version** or **4.4.0**. 2. In Partner Manager, from a non-production environment, in the **Message Flows** page, click **Upgrade deployments** to upgrade to the latest templates. 3. Run the necessary validation tests for your apps. 4. Repeat Step 2 in the production environment to deploy your runtime apps to production. If you don’t want to move your apps to Mule 4.4 at this time, you can follow the previous steps 2-4 to upgrade the runtime templates only and stay on Mule 4.3. Then, when you are ready to deploy your apps on Mule 4.4: 1. In Runtime Manager, individually update each application to 4.4 in a non-production environment. 2. Run the necessary validation tests for your apps. 3. After the tests complete successfully, in Runtime Manager, individually update each runtime application to 4.4 in the production environment. 4. In Access Management, go to **Partner Manager Settings** and select either **Use latest version** or **4.4.0**. ### Fixed Issues

Issue Resolution ID

EDIFACT Write errors now display in the Activity view.

W-10979350

The HTTP outbound endpoint now sets the proper EDI content-type for acknowledgements.

W-11625856

DPS now successfully processes message flows for message types that contain many message flows.

W-12353584

API /endpoints operation now works as expected when sending the id field in the request body.

W-11762359

Pagination headers in endpoints are now forwarded as expected.

W-11836174

You can now open activities and endpoint details in orgs that contain many transmissions and endpoints.

W-12390876

New endpoints are now shown on the partners view without having to refresh the window.

W-12276355

Incremental numbers for keystore names are now displayed correctly.

W-12273189

Message types with empty mappings can no longer be created.

W-11989574

Granular permissions are now handled properly in the UI.

W-10728666 / W-10550424

## [](#2-14-3)2.14.3 **November 29, 2022** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

Runtime service	Version
Document processing service	3.5.2
API Replication service	1.14.0
Endpoint services	3.5.1

### [](#dependent-components-used-50)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues

Issue Resolution

When you select an AS2 receive endpoint for an inbound message flow, third-party names now load faster than previously.

W-10550219

The Partners and Message Flow pages now load faster than previously.

W-11954939

## [](#2-14-2)2.14.2 **October 17, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

Runtime service	Version
Document processing service	3.5.2
API Replication service	1.14.0
Endpoint services	3.5.1

### [](#dependent-components-used-51)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues

Issue ID

The View Host, Partners and Message Flows user permission now works as expected.

W-11801440

The performance of partner profile retrieval for AS2 endpoints has improved to prevent timeouts.

W-11810082

Inbound functional acknowledgements now get reconciled with the corresponding outbound messages.

W-11831508

Message flows with HTTP Send endpoints no longer have issues deploying to the EU control plane.

W-11894143

## [](#2-14-1)2.14.1 **October 3, 2022** This version does not require a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

Runtime service	Version
Document processing service	3.5.1
API Replication service	1.14.0
Endpoint services	3.5.0

### [](#dependent-components-used-52)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues

Issue

The performance for retrieving message types in large environments is now improved.

W-11766796

## [](#2-14-0)2.14.0 **September 12, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

Runtime service	Version
Document processing service	3.5.1
API Replication service	1.14.0
Endpoint services	3.5.0

### [](#dependent-components-used-53)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New You can now use the following EDI versions when configuring partner message types: - **X12 UCS**: 003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS - **X12 VICS**: 003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS - **EDIFACT**: D96B ### Fixed Issues

Issue

Users can now use the greater-than sign character (>) as a data element separator.

W-11102644

Users can now consistently select values from the AS2 Sender drop-down menu.

W-11606268

## [](#2-13-1)2.13.1 **August 16, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-54)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues

Issue

You can now configure an EDIFACT identifier without an associated qualifier by selecting NONE: Not used in the Qualifier field.

W-11032400

The Content-Type header on an outbound HTTP call is now sent with the correct values.

W-11386502, W-11437993

Inbound EDIFACT messages received via FTP in on-premises runtimes are now processed correctly.

W-11529737

## [](#2-13-0)2.13.0 **July 20, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-55)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New You can now update your organization’s AS2 keystore with a new certificate and private key pair when the certificate is about to expire. ### Fixed Issues

Issue ID

The status of inbound EDI messages that fail to parse is now set to Failed.

W-10550091

Users can now create an outbound message flow when the message flow’s reference ID stops being used in another message flow. Partner Manager previously rejected outbound message flows under these circumstances.

W-10550390

In customer-hosted Mule runtimes, the content type is now sent on outbound HTTPS calls.

W-11330247

The status of outbound transmissions that failed due to connectivity issues no longer shows as Processing in the messages view.

W-11302565, W-11352396

Clicking Source payload and Target payload on the message details page now opens the payload in a separate browser tab when a payload view URL is configured in the payload storage settings.

W-11367736

## [](#2-12-0)2.12.0 **June 22, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-56)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New #### [](#custom-message-attributes)Custom Message Attributes You can extract key fields from messages processed by Partner Manager in Mule runtime engine and define them as custom message attributes that users can search. For example, you can extract order numbers and invoice numbers from transactions and define them as custom message attributes. You can upload a DataWeave file that maps custom attributes when defining the Receive from Partners and Source at Host message types. #### [](#messages-view)Messages View The **Activity** page now provides a message-level view that displays individual transactions contained within the same X12 or EDIFACT interchange as separate records in a tabular format. The message-level view enables you to view the post-translated payloads of the inbound messages in the message details page. The view includes a filter that enables you to search for a specific custom message attribute label and value, such as an order number or an invoice number. The search results include all of the messages that contain attributes that match the search criteria. ### Fixed Issues

Issue

Sporadic issues in which AS2 inbound messages fail in customer-hosted Mule runtimes no longer occur.

W-10936394

Selecting a valid value for the Test Indicator field in the EDIFACT send settings no longer causes transactions to fail in Mule runtime.

W-11019452

The load times of partners, message flows, and activity pages are now improved.

W-11208963

The activity status no longer shows an unknown error when every transaction in an incoming EDI interchange fails validation.

W-11233322

Sporadic issues when processing files from FTP receive endpoints in customer-hosted runtime environments no longer occur.

W-11308281

## [](#2-11-1)2.11.1 **May 23, 2022** This version requires a runtime template update for customer-hosted runtime environments. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-57)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues

Issue

XML messages received via HTTP endpoints in customer-hosted runtimes no longer fail in the schema validation step.

W-10962247 and W-11092812

## [](#2-11-0)2.11.0 **April 21, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-58)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New - You can now enable code set validations for inbound and outbound EDI X12 and EDIFACT messages exchanged with partners. - When viewing raw EDI message payloads without line breaks between segments, you can now wrap the payload by specifying the segment delimiter character. - You can now configure a segment line ending character to apply to the last segment of outbound X12 and EDIFACT payloads. - You can now change the number of results shown per page on the following pages: - Activity - Partners - Message flows - You can now use the **Back** button to navigate from the transmission details page back to the search results page without losing the search context. - The unique transmission ID of Partner Manager is now visible on the transmission details page. ### Fixed Issues

Issue

When calling the payload storage API from Mule runtime engine, local retries are now more reliable.

W-10883633

Improved navigation between pages in the transaction activity screen.

W-10550023

Original name of the reference mapping file in the message type definition is now retained.

W-10550162

Transaction activity search performance is now improved.

W-10809387

Transmission steps are now displayed in the correct order.

W-10550336

Security level configurations are now enforced when creating AS2 receive endpoints.

W-10550076

AS2 endpoint URLs are now consistent.

W-10550112

Message type names are now validated correctly.

W-10550396

Pagination under high load now works correctly.

W-10550023

## [](#2-10-4)2.10.4 **March 23, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-59)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues

Issue

Changes in Payload Storage API configurations now take effect when a message flow is deployed successfully.

B2BSOLUT-3940

Runtime applications are now redeployed only when the referenced AS2 endpoint has a dependency on a new certificate that is not in the runtime application. Previously, inbound and outbound AS2 runtime applications were redeployed with the deployment of every message flow that referenced AS2 endpoints.

B2BSOLUT-6050

Improved the ability of the message flow deployment service to detect possible issues with incomplete build files.

B2BSOLUT-6186

Validation errors that occur in the X12 Write operation are now shown in the Activity screen.

B2BSOLUT-6298

Endpoint names are now included in the runtime application logs for FTP Receive endpoints.

B2BSOLUT-6337

Filters no longer get lost when you navigate between pages in the Activity screen.

W-10782902

Functional acknowledgements (997) generated for inbound X12 messages now use the delimiter characters configured in the partner’s X12 send settings.

W-10842929

## [](#2-10-3)2.10.3 **February 16, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-60)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues

Issue

Sporadic issues no longer occur with transmission status updates in the control plane or with the API replication service when there are high message volumes.

W-10668852

## [](#2-10-2)2.10.2 **February 11, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-61)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues

Issue

Some MDNs with binary encoding failed to process and did not properly persist in payload storage.

B2BSOLUT-6345 and B2BSOLUT-6384

## [](#2-10-1)2.10.1 **January 7, 2022** This version requires a runtime template update. ### Compatibility

Application or Service

Version

Mule

4.3

### [](#dependent-components-used-62)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues

Issue

Partner-specific endpoints did not always appear in the endpoint selector window due to caching issues.

B2BSOLUT-6107

Binary message disposition notifications (MDNs) received by AS2 send endpoints were not persisted in payload storage.

B2BSOLUT-6199

SFTP and FTP send endpoint apps failed when writing files to the root directory.

B2BSOLUT-6295

When navigating to the Message flows page by clicking a message flow count link on the Partners page, the Message flows page listed the message flows for all partners. It should have only listed the message flows for the partner associated with the link.

B2BSOLUT-6304

Upgraded library dependencies for EDIFACT EDI Connector and the X12 EDI Connector.

B2BSOLUT-6315

## [](#2-10-0)2.10.0 **December 17, 2021** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-63)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### What’s New - Partner Manager now paginates lists on the following pages, making it easier to navigate across all transactions, partner configurations, and message flow configurations: - **Activity** page - **Partners** page - **Message flows** page - You can now configure basic (username and password) authentication on AS2 send endpoints to meet partner requirements. - You can now configure AS2 receive endpoints with the HTTP protocol for deploying to CloudHub. ### Fixed Issues

Issue

Improved the integration with Anypoint Security secrets manager for storing secured configurations and certificates.

B2BSOLUT-6146

Improved the circuit breaker mechanism in the API replication service template to support longer downtimes.

B2BSOLUT-6256

Improved the runtime templates for on-premises deployments.

## [](#2-9-2)2.9.2 **November 12, 2021** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-64)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues

Issue

In some cases, the X12 functional acknowledgement reconciliation used the interchange control number instead of a group control number to match outbound messages.

B2BSOLUT-5902

Partner Manager sent sync message disposition notifications (MDNS) and async MDNs when the sender explicitly requested async MDNs for AS2 inbound messages.

B2BSOLUT-6054

Partner Manager did not send EDIFACT CONTRL acknowledgements when received messages failed in validation.

B2BSOLUT-6106

AS2 outbound messages that did not request receipts expected MDNs in response.

B2BSOLUT-6151

Partner Manager did not set security level requirements for AS2 receive endpoints created prior to release 2.9.0.

B2BSOLUT-6212

The Activity page hung when selecting a From Date value seven days before the daylight savings time change date.

B2BSOLUT-6222

## [](#2-9-1)2.9.1 **November 2, 2021** This version requires a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-65)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues

Issue

Some partners were unable to process AS2 messages sent from Partner Manager.

B2BSOLUT-6194

## [](#2-9-0)2.9.0 **October 28, 2021** This version requires a runtime template update. ### What’s New - Partner Manager now supports JSON and XML formats as Receive from partners and Send to partners message types. - You can now receive inbound B2B transactions from partners via HTTP and HTTPS endpoints. - You can now use API Manager to secure and govern Receive from partners and Source at host HTTP and HTTPS receive endpoints. - You can now specify security level requirements for AS2 receive endpoints so that Partner Manager rejects incoming messages that are not signed or encrypted. - The Content-Type header is now passed on payloads sent to AS2, HTTP, and HTTPS endpoints. - Inbound and outbound AS2 Message Disposition Notifications (MDNs) are now visible on the Activity page. - You can now configure a secondary payload storage API URL that you can use to view the payload on the Activity page if the payload storage API is restricted to your internal network. - Partner Manager now supports using a group control number as a property placeholder for send endpoint file naming patterns. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-66)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues

Issue

API key authentication was not enforced as configured in HTTP or HTTPS receive endpoints.

B2BSOLUT-5827

Configured AS2 outbound file name and subject headers were not sent to partner endpoints.

B2BSOLUT-5941

Runtime AS2 apps were not updated when new certificates were assigned in the partner profile.

B2BSOLUT-5989

The message flow runtime upgrade process was automatically triggered under some conditions.

B2BSOLUT-6013

## [](#2-8-6)2.8.6 **October 1, 2021** This version does not require a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-67)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues

Issue

Under certain conditions, Partner Manager left message flows in an inconsistent state.

B2BSOLUT-6023

## [](#2-8-5)2.8.5 **September 28, 2021** This version does not require a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-68)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues

Issue

The outbound AS2 service failed to parse the binary-encoded MDNs returned by partners.

B2BSOLUT-5983

## [](#2-8-4)2.8.4 **September 14, 2021** This version does not require a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-69)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues

Issue

Users could not upgrade earlier environments that contained references to inactive endpoints.

B2BSOLUT-5899

## [](#2-8-3)2.8.3 **September 9, 2021** ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-70)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues

Issue

Some inbound X12 transactions within batched interchanges were failing with a processing initialization failure.

B2BSOLUT-5886

Translated outbound EDI message payloads were not visible in the UI when unable to deliver data to partner AS2 endpoints.

B2BSOLUT-5876

CONTRL functional acknowledgments were not generated for some inbound EDIFACT messages.

B2BSOLUT-5923

997 functional acknowledgments were not generated for some inbound X12 messages.

SE-22607

The Transmission section was not shown in the Activity detail while retrying to deliver documents to SFTP, FTP, and HTTP target endpoints.

B2BSOLUT-5888

## [](#2-8-2)2.8.2 **August 18, 2021** This version does not require a runtime template update. ### Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-71)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues

Issue

Users could not log into Partner Manager from new business groups.

B2BSOLUT-5899

### [](#limitations)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-8-1)2.8.1 **August 13, 2021** ### [](#compatibility-72)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-72)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#fixed-issues-69)Fixed Issues - Some outbound X12 **Write** operations failed due to object store issues. ### [](#limitations-2)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-8-0)2.8.0 **August 12, 2021** ### [](#compatibility-73)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-73)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#new-features)New Features - A new partner type, 3rd party connection, enables you to configure and manage identifiers and endpoints for connecting with data aggregators such as 3PLs and VANs. - Improved X12 and EDIFACT message validation error reporting. - Enhanced auto-generated endpoint names. - Improved accessibility standards in the Partner Manager interface, including: - Colors with better contrast for button hover states, links to rate and review assets, and search fields - Typehead styles - Focus states for certain menus and buttons - Dropdown menu styles - Page title field styles ### [](#fixed-issues-70)Fixed Issues - Status of some transmissions remained as `Processing`, even though the messages processed successfully (B2BSOLUT-5521). - Some transactions within an inbound interchange intermittently failed to process with the error `Message processing initialization failed when processing inbound messages` (B2BSOLUT-5728). - Some outbound messages failed in the X12 **Write** operation due to an object store error (B2BSOLUT-5748). - Retry configurations for AS2 send endpoints were not honored (B2BSOLUT-5559). - Translated outbound EDI message payloads were not visible in the UI when unable to deliver the data to partner SFTP, FTP and HTTP(s) endpoints (B2BSOLUT-5757). - Translated inbound application message payloads were not stored in the payload storage (B2BSOLUT-5743). - File name patterns for send endpoints were not validated against allowed mask placeholders (B2BSOLUT-5877). - Optimized the retry attempts and intervals for SFTP and FTP send endpoints to avoid repeated retries for prolonged duration (B2BSOLUT-5719). - Could not use the value `0` for retry attempts in AS2 send endpoint configurations (B2BSOLUT-5798). - Unable to save the character set encoding ‘PLATFORM’ in X12 receive settings (B2BSOLUT-5817). - Unable to create EDI identifiers with two-character values (B2BSOLUT-5818). - Unable to add new AS2 identifiers from the AS2 send endpoint creation dialog (B2BSOLUT-5846). ### [](#limitations-3)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-7-1)2.7.1 **July 6, 2021** ### [](#compatibility-74)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-74)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#fixed-issues-71)Fixed Issues - Outbound message flows with custom EDI schemas did not apply custom EDIFACT schemas at runtime (B2BSOLUT-5689). - The host AS2 keystore was deleted when users deleted an AS2 endpoint (B2BSOLUT-5658). - Change log activity in the message flow details showed incorrect user names (B2BSOLUT-5298). - Transactions with non-fatal message validation errors showed as failed messages in activity reporting (B2BSOLUT-5596). - Caching issues occurred when receiving X12 and EDIFACT messages from the same partner concurrently (B2BSOLUT-5695). - Fixed issues with template runtime version upgrade behavior (B2BSOLUT-5699, B2BSOLUT-5740). - Partner Manager attempted to send functional acknowledgements (997) when processing inbound 997s if partner level acknowledgements were enabled in the X12 settings (B2BSOLUT-5520). - Inbound files with certain extension types did not process successfully in on-premises Mule runtime environments (B2BSOLUT-5423). - Minor UI fixes. ### [](#limitations-4)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-7-0)2.7.0 **June 15, 2021** ### [](#compatibility-75)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-75)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#new-features-2)New Features - Support for exchanging B2B transactions with trading partners in the UN/EDIFACT message format. - Functional acknowledgment (CONTRL) generation and reconciliation for EDIFACT messages. - Support for exchanging B2B transactions with trading partners via the FTP transport protocol. - You can now give custom EDI schema definitions user-defined names for easier reference and reuse in message flows (B2BSOLUT-5420). ### [](#fixed-issues-72)Fixed Issues - Outbound message flows with custom EDI schemas did not apply custom X12 schemas in runtime (B2BSOLUT-5421). - More than one outbound message flow for the same partner could not have custom X12 message validation settings (B2BSOLUT-5380). - Internal worker URLs of AS2/HTTP received endpoints deployed to private ports in CloudHub VPC (B2BSOLUT-5650). ### [](#limitations-5)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premise Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-2)2.6.2 **April 13, 2021** ### [](#compatibility-76)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-76)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-3)New Features None. ### [](#fixed-issue)Fixed Issue In some environments with older message flows, new message flows did not load. (SE-19795) ### [](#known-issues-5)Known Issues None. ### [](#limitations-6)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to an on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-1)2.6.1 **March 31, 2021** ### [](#compatibility-77)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-77)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-4)New Features None. ### [](#fixed-issues-73)Fixed Issues - Functional acknowledgements (997) are sent even when inbound transactions are rejected due to validation errors. (B2BSOLUT-5449) - Endpoints to send TA1 acknowledgements are deployed when inbound message flows are deployed. (B2BSOLUT-5414) - Message flow deployments no longer fail because of undeployed non-Partner Manager applications in the environment. (B2BSOLUT-5454) ### [](#known-issues-6)Known Issues None. ### [](#limitations-7)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-0)2.6.0 **March 25, 2021** ### [](#compatibility-78)Compatibility

Application or Service	Version
Mule	4.3 and later

### [](#dependent-components-used-78)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-5)New Features - New configuration to deploy AS2, HTTP, and HTTPS listener endpoints to a private port when deploying to CloudHub VPC. - Generic runtime applications for SFTP receive, SFTP send, HTTP send, and HTTPS send endpoints through dynamic configurations. - New filters for transactions in the **Activity** page: `Partner name`, `Partner message type`, `Host message type`, and `Message processing status`. - New file name pattern for SFTP receive endpoints. - Several minor bug fixes and improvements. ### [](#fixed-issues-74)Fixed Issues Users are no longer required to import the host organization’s AS2 certificate in each AS2 send endpoint configuration. You can now create an AS2 host keystore to save the host AS2 certificate and private key for reuse across different AS2 endpoints. ### [](#known-issues-7)Known Issues None. ### [](#limitations-8)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-5-3)2.5.3 **February 9, 2021** ### [](#compatibility-79)Compatibility

Application or Service	Version
Mule	4.2.2 and later

### [](#dependent-components-used-79)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-6)New Features None. ### [](#fixed-issues-75)Fixed Issues Message flow deployments no longer fail when the Payload Storage API configuration is modified and redeployed. ### [](#known-issues-8)Known Issues None. ### [](#limitations-9)Limitations None. ## [](#2-5-2)2.5.2 **December, 11 2020** ### [](#compatibility-80)Compatibility

Application or Service	Version
Mule	4.2.2 and later

### [](#dependent-components-used-80)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-7)New Features None. ### [](#fixed-issues-76)Fixed Issues Fixed the issue of XML/JSON schema-validation errors in standalone Mule runtime instances on Windows servers. ### [](#known-issues-9)Known Issues None. ### [](#limitations-10)Limitations None. ## [](#2-5-1)2.5.1 **November 25, 2020** ### [](#compatibility-81)Compatibility

Application or Service	Version
Mule	4.2.2 and later

### [](#dependent-components-used-81)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-8)New Features None. ### [](#fixed-issues-77)Fixed Issues - When no outbound transaction matches the control numbers specified in the 997 functional acknowledgments received from trading partners, the transform process now ignores the EDI Acknowledgement. - If an outbound message flow for a specific partner and message type exists, you can now create a different outbound message flow for the same partner and message type using a different host-reference identifier. - When viewing identifiers in the **Message Flow** page, issues no longer occur. - When the payload storage API configuration is modified, the template upgrade deployment process now leverages an API replication service to push the selected configuration changes to the application runtime. - When connecting to your trading partner’s AS2 endpoint configurations to transmit AS2 messages, connection timeouts are now used in the runtime. ### [](#known-issue)Known Issue When connecting to your trading partner’s AS2 endpoints to transmit AS2 messages, the runtime limits connection retry attempts to 20 every two minutes. ### [](#limitations-11)Limitations None. ## [](#2-5-0)2.5.0 **November 13, 2020** ### [](#compatibility-82)Compatibility

Application or Service	Version
Mule	4.2.2 and later

### [](#dependent-components-used-82)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-9)New Features - X12 outbound messaging You can now exchange B2B transactions bidirectionally with your trading partner ecosystem: - Receive inbound EDI transactions and integrate with your backend systems as JSON or XML application messages. - Receive JSON or XML application messages from your backend systems and send to your trading partners as EDI X12 transactions. - Acknowledgement reconciliation Partner Manager reconciles the inbound functional acknowledgements received from trading partners and updates the corresponding outbound transaction’s acknowledgment status. - Support for XML message format for backend integrations You can now use XML as the target message format in inbound flows and source message format in outbound flows for integration with your backend systems. - Deployment upgrades You can easily upgrade your deployed message flows to take advantage of new features in the latest Mule release. - X12 Conditional relationship validation You can configure the X12 message validation settings to enable and disable X12 conditional relationship validation on inbound and outbound transactions to improve X12 compliance in the EDI messages you are exchanging with your trading partners. - Improved transaction search with additional search filters for: - Direction type of the transmission - From Date timestamp - To Date timestamp - Acknowledgement status of the transmission - Improved X12 error reporting Reporting of validation errors is now at the segment and element levels. - Improved configuration management for endpoints and message types Message types configured in Partner Manager are categorized based on usage. They are available for reuse across message flows for all trading partners. You can assign ownership to endpoint configurations for controlled reuse. - Dynamic file name patterns for send endpoints You can configure the file name pattern on send endpoints based on the requirements of your backend systems or your trading partners. ### [](#fixed-issues-78)Fixed Issues None. ### [](#known-issue-2)Known Issue When connecting to your trading partner’s AS2 endpoints to transmit AS2 messages, the runtime limits you to three connection retry attempts every 10 seconds. Additionally, each connection retry attempt times out after 10 seconds. ### [](#limitations-12)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule instances. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments. ## [](#2-4-5)2.4.5 **August 28, 2020** ### [](#compatibility-83)Compatibility

Application or Service

Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later

### [](#dependent-components-used-83)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-10)New Features None. ### [](#fixed-issue-2)Fixed Issue Fixed the issue that caused TA1 acknowledgment payloads to not be saved for message flows deployed in CloudHub. ### [](#known-issues-10)Known Issues None. ### [](#limitations-13)Limitations None. ## [](#2-4-4)2.4.4 **July 29, 2020** ### [](#compatibility-84)Compatibility

Application/Service

Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later

### [](#dependent-components-used-84)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-11)New Features None. ### [](#fixed-issue-3)Fixed Issue Fixed the Anypoint MQ region mapping for the EU Frankfurt region. ### [](#known-issues-11)Known Issues None. ### [](#limitations-14)Limitations None. ## [](#2-4-3)2.4.3 **July 15, 2020** ### [](#compatibility-information)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-support-for-anypoint-partner-manager)Browser Support for Anypoint Partner Manager Use Anypoint Partner Manager with the latest version of any of the supported browsers: - Microsoft Edge with Chromium - Microsoft Edge without Chromium (supported through December 31, 2020) - Google Chrome - Mozilla Firefox - Safari Browser support for Anypoint Platform follows the Salesforce Lightning Experience Policy. ### [](#dependent-components-used-85)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-12)New Features None. ### [](#fixed-issues-79)Fixed Issues None. ### [](#known-issues-12)Known Issues None. ### [](#limitations-15)Limitations None. ## [](#2-4-2)2.4.2 **June 25, 2020** ### [](#compatibility-information-2)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-86)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-13)New Features None. ### [](#fixed-issue-4)Fixed Issue Updated the NodeJS version with the latest security patches (B2BSOLUT-4213). ### [](#known-issues-13)Known Issues None. ### [](#limitations-16)Limitations None. ## [](#2-4-1)2.4.1 **June 8, 2020** ### [](#compatibility-information-3)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility-2)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-87)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-14)New Features None. ### [](#fixed-issue-5)Fixed Issue Fixed runtime engine issues in the Document Processing Service that caused unnecessary retries of send tracking messages. ### [](#known-issues-14)Known Issues None. ### [](#limitations-17)Limitations None. ## [](#2-4-0)2.4.0 **May 28, 2020** ### [](#compatibility-information-4)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility-3)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-88)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-15)New Features - Enhanced security with granular role-based access control with permissions - Ability to set the CloudHub deployment region for Partner Manager - Ability to select and view endpoint details from the endpoints list ### [](#fixed-issues-80)Fixed Issues - Functional acknowledgements are now generated when all the transaction sets in the Functional Group are rejected. - AK2 and AK5 segments are now included when returning a functional acknowledgment for an unsupported transaction set. ### [](#known-issues-15)Known Issues None. ### [](#limitations-18)Limitations - Sending outbound B2B messages to trading partners is not supported. - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used during routing to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to an on-premise instance of Mule. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments from Partner Manager. ## [](#2-3-0)2.3.0 **April 30, 2020** ### [](#compatibility-information-5)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-4)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-89)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-16)New Features - Deployment to CloudHub You can now deploy your B2B message flows to the MuleSoft-hosted CloudHub platform. You can select the deployment target for your business group (CloudHub or your own hosted Mule runtime) by navigating to the Partner Manager settings page in Access Management. - Enhanced AS2 protocol support Added support for additional signing and encryption algorithms for secured B2B transmissions with your trading partners over the AS2 transport protocol. - Support for additional X12 versions Added support for X12 versions 006010, 006030, 006040, 006050, 007010, 007020, 007030, 007040, and 007050. ### [](#fixed-issues-81)Fixed Issues - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment continues to completion. (B2BSOLUT-2682) - Special characters can now be used in the search bar. (B2BSOLUT-3118) ### [](#known-issues-16)Known Issues None. ### [](#limitations-19)Limitations - Sending Outbound B2B messages to trading partners is not supported. - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premise Mule. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments from Partner Manager. ## [](#2-2-0)2.2.0 **January 11, 2020** ### [](#compatibility-information-6)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-5)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-90)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.11 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.2 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#new-features-17)New Features - View and search for endpoints You can now view a list of endpoints from both the host and partner profile pages. The endpoints are searchable by: - The name of the endpoint - The transport protocol used, such as SFTP or AS2 - Details associated with the URL for the endpoint, such as the path - Delete endpoints You can now delete an endpoint that is not used in any message flow configuration. If an endpoint is used in a message flow, you must dissociate the endpoint, update the message flow, and then delete the endpoint. - Delete certificates You can now delete certificates from both the host and partner profile pages. - View and download maps You can now view maps that are part of message flow configurations. You can also download these maps and reuse them. - The B2B integration apps now leverage a circuit breaker pattern to detect failures and prevent failures from continually recurring. ### [](#fixed-issues-82)Fixed Issues - Replaced the third-party Jackson library that was used to serialize and deserialize Java objects to JSON, with the more secure GSON library (B2BSOLUT-2309) - Implemented stricter length and character validations for the message flow and the message type names (B2BSOLUT-2692) - Custom names provided via the UI are now recognized when creating a new HTTP or HTTPs endpoint. (B2BSOLUT-2940) - A timestamp is now added when the flow undeployment completes. (B2BSOLUT-2980) - The archival path is now an optional field when configuring an SFTP endpoint to receive an inbound file. (B2BSOLUT-2984) - After a message flow is deleted, its reference now appears without a hyperlink on the related transmission activities details page. (B2BSOLUT-2994) ### [](#known-issues-17)Known Issues - Using special characters while searching leads to an error. - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment terminates. ### [](#limitations-20)Limitations - Outbound/Send flows are not supported. - DataWeave maps must be created in Anypoint Studio. - Routing of X12 files are based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is presently not used while routing to message flows. ## [](#2-1-3)2.1.3 **December 20, 2019** ### [](#new-features-18)New Features None. ### [](#fixed-issues-83)Fixed Issues - The latest deployment activity was overriding previous recent deployment activity from the deployment activity section in Message flow details. (B2BSOLUT-2970, B2BSOLUT-2982) - The undeployment action details were not showing up correctly in the message flows list. (B2BSOLUT-3011) ### [](#known-issues-18)Known Issues None. ### [](#limitations-21)Limitations None. ## [](#2-1-2)2.1.2 **December 17, 2019** ### [](#new-features-19)New Features None. ### [](#fixed-issue-6)Fixed Issue Deployed message flows were failing to deliver acknowledgments and marking the transmission as "failed" when using identical endpoint configurations of a previously deployed endpoint. \[B2BSOLUT-2979\] ### [](#known-issues-19)Known Issues None. ### [](#limitations-22)Limitations None. ## [](#2-1-1)2.1.1 **December 13, 2019** ### [](#new-features-20)New Features None. ### [](#fixed-issue-7)Fixed Issue Updating the authentication type and its details in your [payload storage API configuration](https://docs.mulesoft.com/jp/partner-manager/latest/setup-payload-storage-API) in Anypoint Partner Manager resulted in an error. \[B2BSOLUT-2996\] ### [](#known-issues-20)Known Issues None. ### [](#limitations-23)Limitations None. ## [](#2-1-0)2.1.0 **December 7, 2019** ### [](#compatibility-information-7)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-6)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-91)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.11 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.3 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#new-features-21)New Features - Undeploy Message Flows Users can now undeploy message flows to remove the associated message flow configuration and the B2B integration applications from Mule. Undeploying a flow stops further processing of any messages associated with that flow. - Delete Identifiers Users can now delete all X12 ISA identifiers, X12 GS identifiers, and DUNS identifiers. Every partner must have at least one identifier. - Delete Message Flows Users can now delete a message flow. A message flow must be undeployed before attempting to delete it. - Delete Trading Partners Users can now delete trading partners. Deleting a trading partner deletes the information associated with that partner, such as identifiers, certificates, endpoints, and message flows. Activities for the partner that occurred before the partner was deleted are not deleted, although the **Activities** page shows that the partner has since been deleted. ### [](#fixed-issues-84)Fixed Issues - On the **Activities** page, using certain special characters caused the backend API to respond with an HTTP 400 error. \[B2BSOLUT-2350\] - An uncaught error when creating a new message type is resolved. \[B2BSOLUT-2491\] - If the name of a message flow is changed, the details about routing after sending files show "missing message flow" on the **Activities** page. \[B2BSOLUT-2531\] - Upgraded `commons-codec` to v1.13 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2539\] - Upgraded `react.dom` to v16.12.0 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2548\] - Users were unable to reuse a path in several different endpoints. \[B2BSOLUT-2651\] - Resolved a fatal error when using a dash (-) when deploying an SFTP to an HTTPS message flow. \[B2BSOLUT-2673\] - The API now validates a valid email address when defining an AS2 endpoint. \[B2BSOLUT-2675\] - Links were previously shown with an invalid color in Firefox. \[B2BSOLUT-2676\] - Users were unable to create a new partner with an X12 ISA/SCAC qualifier when the identifier value used the maximum permissible length. \[B2BSOLUT-2684\] - Upgraded `netty-code-http` to v4.1.7 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2708\] - Creating long names with AS2 identifiers raised errors. \[B2BSOLUT-2711\] - The transmission data patch was occasionally missed, leaving reported activities in an incomplete state. \[B2BSOLUT-2733\] - Sending the same type of EDI files simultaneously to multiple partners caused transactions for one of the partners to fail. \[B2BSOLUT-2746\] - Upgraded `jquery` to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2791\] - Clicking the Partner Manager logo and name now reloads the page. \[B2BSOLUT-2849\] - After changing the name of a deployed message flow, the old name showed up in the activities title. \[B2BSOLUT-2850\] - Uploading a custom JSON schema failed. \[B2BSOLUT-2879\] - The View payload feature failed in the backend service. \[B2BSOLUT-2903\] ### [](#known-issues-21)Known Issues - Using special characters in the search bars leads to an error in subsequent search operations. - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment terminates. - The number of message flows using an acknowledgment endpoint incorrectly appears as 0, even when the endpoint is in use. ### [](#limitations-24)Limitations - AS2 identifiers, certificates, and endpoints cannot be deleted. - Outbound - Send flows are not supported. - The ability to test endpoint configurations via the UI for AS2, SFTP, HTTP, and HTTPS before deploying them in Mule is not supported. - DataWeave maps must be created in Anypoint Studio prior to using Anypoint Partner Manager. - Routing of X12 files is based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is not leveraged while routing to message flows. ## [](#2-0-1)2.0.1 **November 9, 2019** ### [](#new-features-22)New Features None. ### [](#fixed-issue-8)Fixed Issue Transmission data attributes were not being shown for failed transmissions. These attributes include partners involved in the transmission, EDI format and metadata for the interchange. All new deployments use the latest version of the `DocumentProcessingService` application. If you have any message flows deployed with Partner Manager 2.0.0, use Anypoint Runtime Manager to remove the existing `DocumentProcessingService` application. To get latest version of `DocumentProcessingService`, use the Deploy button to redeploy any message flow from Anypoint Partner Manager. Removing the `DocumentProcessingService` application pauses transaction processing until you deploy these message flows again. For information about deleting applications, refer to [Managing Applications on Your Own Servers](https://docs.mulesoft.com/runtime-manager/managing-applications-on-your-own-servers#deleting-applications). ### [](#known-issues-22)Known Issues None. ### [](#limitations-25)Limitations None. ## [](#2-0-0)2.0.0 **October 19, 2019** This release marks the general availability of Anypoint Partner Manager 2.0 ### [](#whats-new-in-anypoint-partner-manager-2-0)What’s new in Anypoint Partner Manager 2.0 - Based on Mule runtime engine 4.x Anypoint Partner Manager 2.0 enables developers to accomplish B2B integration tasks with fewer steps. Anypoint Partner Manager 2.0 delivers templatized B2B integration flows that can be configured via the Partner Manager management console. The templatized flows leverage the power of the Mule runtime engine 4.x, Dataweave transformations, and connectors such as the X12, SFTP, AS2, and HTTP connector. - Simplified, wizard-driven configuration of B2B flows Anypoint Partner Manager 2.0 introduces a message flow wizard that enables users to easily set up B2B integration flow components such as endpoints, messages, maps, and acknowledgments. Furthermore, the solution enables the reuse of the building blocks of a B2B integration flow thereby speeding up trading partner technical onboarding. You can use Anypoint Partner Manager v2 to setup inbound - receive flows with your trading partners using protocols such as SFTP and AS2. - Support for hybrid deployments With this release of Anypoint Partner Manager 2.0, users are able to leverage the cloud-based Partner Manager management console to configure and manage their B2B flows, while the corresponding B2B integration flows based on the packaged templates provided by the Anypoint Partner Manager 2.0 solution, processes workloads on Mule runtime engine 4.x which can be hosted on-premise in your data centers or in public clouds of your preference. - Tracking of B2B transaction activity Anypoint Partner Manager 2.0 provides a detailed view into the B2B integration transactions processed on your Mule runtime engine. The solution allows you to monitor trading partner transmission activity via a set of end-to-end events related to transmission metadata, messages, and errors. The information includes: - The received EDI payload that can be viewed and downloaded - Acknowledgements (such as TA1 and/or 997/999) that are sent back to the partner - A view into the transformed payload - A detailed view of errors including error messages, error codes, and identification of segments that contain errors ### [](#components-released)Components Released - Partner Manager Console 2.0.0 - B2B Integration Templates 2.0.0 ### [](#compatibility-information-8)Compatibility Information Mule Runtime 4.2.1 ### [](#browser-compatibility-7)Browser Compatibility - Google Chrome version 77 and later - Firefox version 69 and later ### [](#dependent-components-used-92)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.0.7 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.9 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.2 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#known-issues-23)Known Issues - Using special characters in the search bars leads to an error in subsequent search operations. - Using special characters in the name of the organization leads to an error in the creation of the host partner. - If a user logs out of the Anypoint Platform session while a B2B message flow deployment is in progress, the deployment is terminated. ### [](#limitations-26)Limitations - Assets such as identifiers, certificates, endpoints, partners, and message flows cannot be deleted. - Outbound - Send flows are not supported. - The ability to test endpoint configurations via the UI for AS2, SFTP, HTTP and HTTPS before deploying them onto the Mule runtime, is not supported. - The DataWeave maps must be created in Anypoint Studio prior to using Anypoint Partner Manager. - Routing of X12 files is based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is not leveraged while routing to message flows. ## [](#see-also)See Also - [Partner Manager Documentation](https://docs.mulesoft.com/jp/partner-manager/latest/) - [Anypoint Partner Manager のトラブルシューティング](https://docs.mulesoft.com/jp/partner-manager/latest/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues)

Runtime service	Version
Document processing service	3.11.9
API Replication service	1.20.3
Endpoint services	3.11.8

Runtime service	Version
Document processing service	3.11.5
API Replication service	1.20.0
Endpoint services	3.11.2

Runtime service	Version
Document processing service	3.11.6
API Replication service	1.20.0
Endpoint services	3.11.4

Runtime service	Version
Document processing service	3.11.1
API Replication service	1.20.0
Endpoint services	3.11.1