Skip to main content

Version 1.18.1.2

Release Date: September 4, 2026 Release Type: Stable Previously published as: 1.18.7 (image tag staging-1.18.7)

More reliable SFTP polling with a per-poll file cap and a selectable undeploy behaviour, shared credentials for RFC destinations, OFTP2 NERP support, an AI Connections page and a reorganized Operations page, together with XI, WSDL and database connection fixes.

Backend Server​

New Features​

  • OFTP2 NERP support: The OFTP2 connector now supports NERP (Negative End Response) messages, and the reason a partner reports for a failure is carried through to Monitoring.
  • RFC destinations can log on with a shared credential: An RFC destination can now reference a BASIC credential from the shared credential pool instead of carrying its own user and password. The referenced credential takes precedence, and the user and password stored on the destination remain as the fallback when no credential is attached. A destination whose referenced credential no longer exists is not registered, rather than logging on with outdated values, and a missing mandatory field is now reported by name.
  • SFTP polling in bounded rounds, with a selectable undeploy behaviour: The SFTP sender now pulls files in rounds limited by Max Files Per Poll (default 50, between 1 and 1000) and starts the next round at once, so throughput is unchanged while memory use stays bounded. Each file is deleted or archived as soon as it has been handed over, instead of at the end of the whole run. The new Undeploy Behaviour setting decides what happens to a poll in progress when the flow is undeployed: Drain (default) lets the files already pulled finish, while Immediate aborts the poll, leaves the pulled files on the server and discards that flow's queued messages.

Bug Fixes​

  • SFTP polling no longer re-downloads files, loses archived copies or exhausts memory: Source files used to stay in place until the whole poll run had ended, so the same file could be downloaded many times within one run. In Archive/Delete mode this could destroy the archived copy of a file, and a large run could run out of memory. Files are now completed one by one. In addition, undeploying a flow now really stops a poll that is in progress; previously the running poll kept pulling and processing files.
  • Failed XI messages are visible and retriggerable right away: An inbound XI message whose flow failed could stay in PROCESSING indefinitely and silently block its whole EOIO queue. Such messages now always leave PROCESSING, and a flow-execution failure is set to ERROR immediately instead of being retried repeatedly, so it can be retriggered at once; infrastructure errors still use the retry budget. The final error writes to Monitoring are retried as well, so a record no longer stays in DELIVERING and later turns into a generic 504 with the original fault text lost.
  • File-transfer flows no longer fail on a stale database connection: Flows that receive files only rarely (SFTP, FTP, File) could fail a poll with "This connection has been closed" after the database connection used for duplicate-file tracking had sat idle and was dropped by the database, a firewall or a NAT device. No data was lost, but each occurrence wasted a poll and raised an alert. Idle connections are now verified and recycled. Installations that added -Dc3p0.* JVM options as a workaround can remove them.

Frontend Server​

New Features​

  • Shared credentials for RFC destinations, with automatic migration: An RFC destination now stores a reference to a BASIC credential. A destination needs either a usable credential or a user and password, and a referenced credential must exist and be of type BASIC. Deleting a credential that an RFC destination still uses is refused with a message naming that destination. At startup, existing destinations that still hold their own user and password automatically get a BASIC credential created and attached; destinations sharing the same user and password are attached to one credential, and the original values are kept as a fallback.
  • SFTP poll cap and undeploy behaviour are stored with the flow: The two new SFTP settings are saved with the flow and passed on to the backend unchanged, where the defaults are applied.

Bug Fixes​

  • Served WSDLs declare elementFormDefault when the uploaded WSDL omits it: The WSDL served for a deployed integration now declares elementFormDefault="qualified" on inline schemas that do not state it, consistent with the WSDLs produced by the WSDL designer; previously consumers fell back to the XSD default (unqualified). A schema that already declares a value keeps it, and the stored WSDL resource is not modified.

Frontend Web​

New Features​

  • Credential selection on RFC destinations: The Create and Update RFC Destination forms gain a Credential (BASIC) select over the shared credentials, with an inline "New credential" option that creates a credential and selects it. The User and Password inputs are removed: a credential is required and a password is no longer typed into this form. Destinations created earlier keep working and are moved onto shared credentials automatically.
  • Max Files Per Poll and Undeploy Behaviour on the SFTP connector: The Advanced tab of the SFTP Start connector gains two settings. Max Files Per Poll caps how many files a single poll round pulls (1 to 1000; blank uses the default of 50), and the remainder is picked up in the next round immediately. Undeploy Behaviour chooses between Drain (files already pulled are processed to completion) and Immediate (the poll aborts, pulled files stay on the server, queued messages are discarded and the batch is read again on redeploy). Existing flows keep the Drain behaviour without any change, and both settings are labeled in the activity log.
  • Operations page reorganized into tabbed pages: Alert Configurations is now a tab under System Health, DB Analysis & Backup a tab under Database Management, and System Log Settings a tab under System Logs. The standalone cards are removed from the Operations page, the previous URLs redirect to the new tabs, each tab can be linked directly, and the tabs remain available to admins only.
  • AI Connections page: The MCP Servers card on the Operations page becomes AI Connections, a tabbed page with the unchanged MCP Servers tab (default) and a new AI Engine tab. On the AI Engine tab a Developer or Admin enters the AI provider API key and picks the model used by the AI Flow chat from a searchable list; the remaining credit of the key is shown when the provider reports it. The previous MCP Servers URL keeps working. The AI Engine tab prepares an upcoming capability: in this version AI Flow generation does not use these settings unless it is explicitly enabled for the installation.

Bug Fixes​

  • Re-uploaded WSDLs are picked up in the XI panels: After a WSDL resource is re-uploaded or edited, the XI start and receiver panels now re-derive the selected interface from the new content. Previously the panels kept showing the stale interface, and a deploy wrote the stale routing key until the resource was removed and selected again. If the resource no longer exists the selection is cleared so that a new one must be chosen, and manually entered values are preserved when the WSDL cannot be fully parsed.

1.18.1.2 is a stable release. Previous: 1.18.1.1