Anypoint Partner Manager 2.x Release Notes

Anypoint Partner Manager (Partner Manager) allows Business-to-Business (B2B) message exchange using APIs and Electronic Data Interchange (EDI) formats.

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

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 ID

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

B2BSOLUT-6023

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

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 ID

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

B2BSOLUT-5983

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

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 ID

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

B2BSOLUT-5899

2.8.3

September 9, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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 ID

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

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

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 ID

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

B2BSOLUT-5899

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

August 13, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

  • Some outbound X12 Write operations failed due to object store issues.

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

August 12, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

  • 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

  • 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

  • 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

July 6, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

  • 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

  • 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

June 15, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

  • 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

  • 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

  • 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.6.2

April 13, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

None.

Fixed Issue

In some environments with older message flows, new message flows did not load. (SE-19795)

Known Issues

None.

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

March 31, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

None.

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

None.

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

March 25, 2021

Compatibility

Application or Service Version

Mule

4.3 and later

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

  • 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

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

None.

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

February 9, 2021

Compatibility

Application or Service Version

Mule

4.2.2 and later

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

None.

Fixed Issues

Message flow deployments no longer fail when the Payload Storage API configuration is modified and redeployed.

Known Issues

None.

Limitations

None.

2.5.2

December, 11 2020

Compatibility

Application or Service Version

Mule

4.2.2 and later

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

None.

Fixed Issues

Fixed the issue of XML/JSON schema-validation errors in standalone Mule runtime instances on Windows servers.

Known Issues

None.

Limitations

None.

2.5.1

November 25, 2020

Compatibility

Application or Service Version

Mule

4.2.2 and later

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

None.

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

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

None.

2.5.0

November 13, 2020

Compatibility

Application or Service Version

Mule

4.2.2 and later

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

  • 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

None.

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

  • 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

August 28, 2020

Compatibility

Application or Service Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later

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

None.

Fixed Issue

Fixed the issue that caused TA1 acknowledgment payloads to not be saved for message flows deployed in CloudHub.

Known Issues

None.

Limitations

None.

2.4.4

July 29, 2020

Compatibility

Application/Service Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later

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

None.

Fixed Issue

Fixed the Anypoint MQ region mapping for the EU Frankfurt region.

Known Issues

None.

Limitations

None.

2.4.3

July 15, 2020

Compatibility Information

Mule runtime engine 4.2.2 and later

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

  • 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

None.

Fixed Issues

None.

Known Issues

None.

Limitations

None.

2.4.2

June 25, 2020

Compatibility Information

Mule runtime engine 4.2.2 and later

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

None.

Fixed Issue

Updated the NodeJS version with the latest security patches (B2BSOLUT-4213).

Known Issues

None.

Limitations

None.

2.4.1

June 8, 2020

Compatibility Information

Mule runtime engine 4.2.2 and later

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

None.

Fixed Issue

Fixed runtime engine issues in the Document Processing Service that caused unnecessary retries of send tracking messages.

Known Issues

None.

Limitations

None.

2.4.0

May 28, 2020

Compatibility Information

Mule runtime engine 4.2.2 and later

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

  • 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

  • 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

None.

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

April 30, 2020

Compatibility Information

Mule runtime engine 4.2.2

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

  • 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

  • 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

None.

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

January 11, 2020

Compatibility Information

Mule runtime engine 4.2.2

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

  • 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

  • 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

  • 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

  • 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

December 20, 2019

New Features

None.

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

None.

Limitations

None.

2.1.2

December 17, 2019

New Features

None.

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

None.

Limitations

None.

2.1.1

December 13, 2019

New Features

None.

Fixed Issue

Updating the authentication type and its details in your payload storage API configuration in Anypoint Partner Manager resulted in an error. [B2BSOLUT-2996]

Known Issues

None.

Limitations

None.

2.1.0

December 7, 2019

Compatibility Information

Mule runtime engine 4.2.2

Browser Compatibility

  • Google Chrome 77 and later

  • Firefox 69 and later

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

  • 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

  • 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

  • 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

  • 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

November 9, 2019

New Features

None.

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.

Known Issues

None.

Limitations

None.

2.0.0

October 19, 2019

This release marks the general availability of 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

  • Partner Manager Console 2.0.0

  • B2B Integration Templates 2.0.0

Compatibility Information

Mule Runtime 4.2.1

Browser Compatibility

  • Google Chrome version 77 and later

  • Firefox version 69 and later

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

  • 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

  • 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.

Was this article helpful?

💙 Thanks for your feedback!