Partner Manager Connector Release Notes - Mule 3
6.7.0
July 2, 2018
Supported Mule Versions: 3.6.4, 3.7.3, 3.8.1, 3.8.2
New Features and Functionality
-
Reduced cache’s memory footprint.
-
Logging memory usage during cache refresh.
-
Added support for HTTP proxy.
-
Added ability to tolerate un-serializable objects while deep copying in asynchronous mode.
Fixed Issues
-
Solved an edge case in which an illegal nested resource transaction attempt could happen when in asynchronous mode.
-
Fixed an issue in which the cache could temporarily become inconsistent during Partner Manager deployments.
-
To prevent the disk from running out of space, cache export is now kept in-memory instead of temporarily saving it to the filesystem.
-
Saving AS2 and FTPS transmissions asynchronously when in asynchronous mode.
-
Preventing duplicate file persistence in case transaction creation failed when in asynchronous mode.
6.6.0
6.5.0
6.4.0
September 8, 2017
New Features and Functionality
-
Added optional queueName attribute to connector config.
-
Added numberOfThreads attribute to connector config.
Fixed Issues
-
Preventing runaway cache refresh thread after connector is stopped.
-
Fixed bug where the wrong environments ID is used when having multiple connector cache-enabled instances.
-
Fixed deserialization/serialization errors when a persistent queue manager is used for asynchronous mode.
-
Improved asynchronous mode performance.
-
Eliminated possible mutations to original Mule event when in asynchronous mode.
-
Supporting multiple configurations when asynchronousMode is enabled.
-
Fixed locking issue across cache instances while refreshing.
-
Improved caching performance.
6.3.0
6.2.0
July 24, 2017
New Features and Functionality
-
Added support for retries.
-
Skipping export download for cache refresh if no changes were made to configuration.
6.1.2
July 12, 2017
Fixed Issues
-
Fixed race condition which allowed duplicate refresh threads.
-
Fixed issue where inboundFormatOptions and outboundFormatOptions in documentDefinition is empty when caching is enabled.
-
Reduced garbage collection overhead when caching is enabled.
-
Searching error codes from Trading Partner Manager instead of Tracker.
-
Release status returned from evaluate-transaction-release-status can now be saved in any location and not just in b2bTransmissionSession.
6.1.0
6.0.1
6.0.0
May 4, 2017
New Features and Functionality
-
Re-written support for caching and exposed it as connector config option.
-
Added connectTimeout, connectionRequestTimeout, and socketTimeout to configuration.
5.3.0
April 10, 2017
New Features and Functionality
Added operations to:
-
Start errors notification.
-
End errors notification (that is, notification sent).
-
Start transactions release (when a transaction has been on-hold, this starts the process of returning the transaction to active processing).
-
End transactions release (that is, complete return to active processing).
-
Evaluate transaction release status.
5.2.0
March 22 2017
5.1.0
5.0.0
February 23, 2017
New Features and Functionality
-
Added support for asynchronous tracking.
-
Removed lastEventId entry from b2bTransmissionSession flow variable.
-
Added support for parent transactions.
-
Made toPartyIdentifier optional in resolve-routes operation.
-
Allowing the maximum number of HTTP connections to each Partner Manager service to be configurable.
-
Adding support for route filtering by properties.
4.0.0
December 13, 2016
New Features and Functionality
-
Added update-transaction-status operation.
-
Removed deprecated transportType attribute in resolve-routes operation.
-
Added harvest-endpoint-properties operation.
-
Added ability to track-document operation to harvest properties.
-
Added propagate-endpoint-properties operation.
-
Added lookup operation.
3.0.0
September 22, 2016
Migrating from Older Versions
-
Rename document attribute in track-document operation to document-ref.
-
Rename partnerIdentifier attribute in resolve-routes operation to fromPartyIdentifier.
-
Rename partnerIdentifierType attribute in resolve-routes operation to partyIdentifierType.
New Features and Functionality
-
Added document definition to list of resources that can be searched.
-
Added count, offset, orderBy, and descending attributes to search operation.
-
Added toPartyIdentifier attribute to resolve-routes operation.
Fixed Issues
-
Fixed issue where maps representing X12 and EDIFACT documents cannot be processed.
-
Fixed issue in resolve-routes operation where standard instead of version is passed to query parameter.
-
Propagating message properties to flow set in config-file-storage-custom config.
-
Ensuring HTTP connections are closed in instances where no content is returned.
-
Fixed issue where byte stream is mistakenly serialized to string when content is saved to custom file storage.
-
Removed test connectivity check on connector start up to make error message more friendly when testing the connection from Anypoint Studio.
2.0.0
July 8, 2016
New Features and Functionality
-
Renamed executionId in b2bTransmissionSession to transactionId.
-
Added support for reporting errors to Anypoint Partner Manager.
-
Added operation for searching.
-
Added operation for resolving routes.
-
Added operation for tracking documents.
-
Added operations for replaying transactions.
-
Including last event ID in b2bTransmissionSession flowVar.
-
Removed formatType and toPartyIdentifier attributes from track-transmission operation.
-
Renamed fromPartyIdentifier attribute to partnerIdentifier and content attribute to file in track-transmission operation.
-
Added transport attribute to track-transmission operation.