5.1.0
Release Notes 5.1.0
ConnectPlaza version 5.1.0 will contain the following important fixes, features and new components:
Fixes and Features
-
Email Listener default cron timer to every 15 minutes
-
Regex check removed from Email Listener to allow for more advanced filters
-
Fixed problem where json and ramlvalidator did not accept classpath: or file: as prefix for schema location.
-
Fixed problem with adding, changing and deleting ConnectMessage properties vs headers
-
Storechannel will no longer write files to filesystem (resource leak). It will still send notifications
-
Added ALL-JSON message part for prettyprint ConnectMessage in json format
-
Session property in Progress OpenEdge Gateway no longer dynamic.
-
Jetty upgrade to 10.0.25. This to resolve several issues with previous versions and existing CVE’s.
-
Fixed and improved component and flow metrics including totalDuration, max, total and standard deviation. Also renamed flow_duration to flow_processing_time.
-
Added possibility to set custom JVM options via SystemStartup Configuration in Agent Configuration in ConnectPlaza Deploy Frontend
-
Added value_type for fixed headers and xpath, json and regex headers
-
Fixed reverted headers after exception handling
-
Support for chmod in sftp components
-
Polling consumers will log a message when no messages are received during a poll. Set loglevel to FULL to see these messages.
-
Fixed support for mapped-http-request - and response headers in WebServiceListener.
-
All splitters copy sequence headers to ConnectMessage properties.
-
Analyze flow can be set to concurrent with "Set AnalyzeBackendChannel to concurrent" in SystemStartup configuration.
-
Fixes issue in OAuth2Gateway with resolve public certificates for Microsoft Graph.
-
New functionality will archive old wrapper-YYYYMMDD.log files to a subdirectory in the logs directory. A retention time can be set to delete all archived log files.
-
Fixed problem with agent symlink under windows
-
Fixed problem with retry options in MicrosoftMailSender when receiving 419 error from Microsoft.
-
Control - Global Enable for State metric in interface, flow and components is disabled.
New Components
MapForce Service V2
The mapforce service component is redesigned. Customers can now configure which messagepart of the incoming message has to be mapped on which argument of the mapforce service. This allows for easy mapping for desired messageparts to the corresponding Input in your multi-input mapping, instead of relying on ordering the messageparts and removing unnecessary parts. It is no longer necessary to remove messageparts which are not used in the mapping. The new V2 service will automatically detect which inputs exist on the Mapping and will help you in mapping these to the correct messageparts.
XML Streaming Parser Service
The XML Streaming Parser Service is a new component that allows for parsing XML documents in a streaming fashion. This is particularly useful for handling large XML files without loading the entire document into memory, thus improving performance and reducing memory usage. This new Service component will allow for efficiently splitting large XML documents into smaller documents based on a repeating element. The resulting splitted document can also be provided with a new root element and the size of the splitted document can be specified with a page size.
MCP Consumer
The MCP Consumer is a new component that allows for consuming messages from the MCP (Message Control Protocol) system. This component is designed to integrate with the MCP system, enabling seamless message processing and handling. MCP is a new protocol that is specifically designed for allow data-access to all kinds of datasources for AI Clients, Assistants or Chatbots. Using ConnectPlaza’s MCP Consumer it is now possible to expose any ConnectPlaza Flow as a MCP Tool that can be used by any AI Client that supports MCP. The MCP Consumer allows the user to specify a tool-name with optional tool-parameters which will be exposed tot the MCP Client which has access to it. The received tool request will be passed onto the flow as a JSON RPC document.