Release Notes 5.3.0

Analyze 2.0 builds business entities with pipelines. You design a pipeline in the pipeline editor in the studio, test it on a real message, and the agent picks it up automatically. Pipelines need agent version 5.3.0

When you test a pipeline in the pipeline editor, the result shows which node failed and why. The parts of the pipeline that do not depend on that node still show their business entities

An Analyze pipeline now reads a message part that holds bytes, such as the body from an HTTP Listener with the default Expected Content Type. Before, every rule on such a part failed and the pipeline created no business entities

In Analyze, the message details of each step now show the information of that step’s own Analyze Wiretap, such as the correlation ID. Before, a step could show the information of the previous Analyze Wiretap

You can filter the Business Entities Overview on the columns of the business entity definition. Numbers compare as numbers, and the like operator finds the text anywhere in the value, ignores case and accepts * and ? as wildcards

You can sort the Business Entities Overview on every column, including the columns of the business entity definition. Before, sorting on such a column showed no data, and sorting on Name did not change the order

In the Analyze traces overview, First Step and Latest Step show the first and the last step in time. Before, they could show the wrong flow when a trace passed through more than one flow or interface

The JMS Listener has a new JMS Transaction Mode option for queues, so a message is not lost when the flow fails. With flow_transacted the flow commits the message at the end or rolls it back on an error. With session_transacted the new JMS Acknowledgement and JMS Rollback components do this: every path must end in one of them, or the message is rolled back after 5 minutes. A rolled-back message is delivered again until the broker moves it to the dead letter queue

The new AI Agent Service component sends a prompt to an AI model (OpenAI or Anthropic) and stores the reply in a message part. With Input Mapping you fill values from the message into the System Prompt and the User Prompt

The HTTP Gateway, Webservice Gateway and TCP Gateway have a new Enable TLS Verification option, which is on by default. Turn it off only for a server whose certificate cannot be checked, such as a self-signed certificate in a test environment: the connection stays encrypted, but the server is not checked

An MCP Server Listener or MCP Proxy Listener with Authentication Scheme OAUTH2_OIDC_ISSUER_URI or OAUTH2_OIDC_JWK_SET_URI now checks the token of every MCP call. Before, it answered MCP calls without a token; BASIC, BASIC_JDBC and LDAP were not affected

The MCP Proxy Listener, and the MCP Gateway Service with Transport Type STREAMABLE, now call the MCP server URL with its path, such as /orders. Before, they always called /mcp on that host

The HTTP Gateway has a new Suppress HTTP Error Status option. When it is on, an error response with a standard status code (400 to 599) goes to the next step with its status in the http_statusCode property, instead of to error handling

The Salesforce components have two new fields, Access Token URI and Audience, so they can log in to another Salesforce host, such as a sandbox. API calls go to the address that Salesforce returns at login, so you no longer have to change the Salesforce Instance field

The UNZIP Service has two new options: Split into multiple messages (on by default; off gives one message with one message part per file) and Apply Sequence (off by default), which adds sequence information for an Aggregator. Files come out in the order of the ZIP, folders no longer create empty files, and file_name is always filled

A ZIP Service or UNZIP Service with ZIP Type GZIP and a password is now refused when you install the adapter. GZIP has no encryption, and before, the component made or read a ZIP file instead

The MQTT Listener and MQTT Sender work again. Before, every interface with one of them failed to start. The Keep alive interval is in seconds and its default is now 60. Check existing components: an old default of 5000 now means 5000 seconds, so change it to 60

The User-defined Marshalling Transformer and User-defined UnMarshalling Transformer work again. Before, they failed every message with the error "Target Flow must not be null"

The Logger no longer hangs when the Log Text refers to a header that the message does not have. The text is logged as written, and the message continues

The Amazon SQS Service now starts behind any consumer, also behind a JMS Listener or a REST Listener. With Action RECEIVE it always asks SQS for one message; before, it could use the Max Messages Per Poll of the consumer and hide the extra messages until their visibility timeout ended

The FTP Command Service with Command mv, a Move Target Directory and Remote Filename from Header now installs. Remote Filename Pattern and Remote Filename Regex now work together with Remote from directory from header

The Windows installer checks the rights of the installing account and of the service account, including the right to create symbolic links, and stops with a clear message when a right is missing. A zip installation runs the same check at first start, and from the first update after 5.3.0 the updater skips an update that fails it and reports why; the environment variable CONNECTPLAZA_PREFLIGHT_MODE=false switches the updater check off

HTTPS servers whose certificate chain uses a cross-signed public root, such as api.openai.com, are accepted without importing the certificate into the truststore

The agent now uses ActiveMQ Classic 5.19.7 for its libraries and its built-in broker. You do not need to change your flows