What's new

Learn more about what's new and changed in webMethods Integration.

June 2026

Ingresses
A new Ingresses tab is introduced under Projects to enhance the visibility and organization of incoming connections. Ingress resources are now grouped under their respective client applications within a project, providing a clearer understanding of how external applications use project services. This enhancement improves navigation, streamlines troubleshooting, and enables more efficient management of ingress configurations. For more information, see Ingresses.
Private projects
Users can now create and manage projects privately. When a project is made private, only the project owner and collaborators explicitly granted with write access can view or modify its assets. This enhancement provides users with greater security, clearer ownership boundaries, and better governance over critical project content.

The Project Management APIs have also been enhanced to support project access control features. For more information, see Creating projects and Project APIs.

Support for mutual TLS (mTLS)
Users can now enable secure, certificate-based authentication between webMethods Integration and client applications. This enhancement allows both systems to verify each other’s identity, and ensure that only trusted clients can access APIs and exchange data securely. For more information, see Setting up secure connections with Mutual TLS (mTLS).
Support for custom domains
Custom domains that are configured at the platform-level are now supported in webMethods Integration. For more information, see Configuring custom domains.
Package enhancements
Adding packages
Users can now add packages to projects from webMethods Package Registry and Cloud Designtime in addition to the existing external Git repositories. This enhancement improves flexibility by enabling users to add packages from multiple sources directly within projects. For more information, see Adding packages from IBM webMethods Package Registry and Adding packages from Cloud Designtime.
Custom package assets in projects
Assets in the project or custom packages can be referenced in the deploy anywhere flow editor. You can view and utilize the reference data and document types of custom packages in the projects. Previously, reference data and document types from dependent or custom packages were not visible in the project configuration. The reference data and document types from custom packages were listed as a service in the package information. For more information, see Using custom package assets in projects.
Deploy anywhere flow service enhancements
Built-in security services
The deploy anywhere flow service editor supports security services such as signing, verification, encryption, or decryption of inputs and outputs. For more information, see Security services.
Built-in flow services
The invokeService is added to the built-in flow services, allowing you to run type of service. For more information, see invokeService.
Dynamic accounts
Dynamic accounts are now supported across all connectors in deploy anywhere flow services for custom actions. For more information, see Using connectors in deploy anywhere flow services.
Runtimes and virtual runtimes
Users can now view runtimes for a deploy anywhere flow service. The Runtimes feature is also enhanced to support filtering runtimes view by referenced service. Other improvements include clearer distinction between virtual runtimes and runtimes and their relations with the referenced services. For more information, seeRuntimes view associated with projects.
HTTP connector
HTTP connector is now supported in deploy anywhere flow services.
Custom REST connector enhancements

The Custom REST connector wizard now supports advanced connector properties, including Validate Schema and Exclude XML Declaration, to provide greater control over XML request handling and schema validation. These properties can be configured after connector creation by editing the connector.

For more information, see Custom REST connector wizard.

Flow editor enhancements
Flow service controls
The Repeat for Count step now supports a configurable repeat-on attribute with on success and on failure options. The Exit step now supports an Exit level attribute that specifies from where in the execution hierarchy the flow service should exit.

For more information, see Working with flow services.

Error message toasts
Error message toasts in the Integration and Flow editor UI can now be dismissed without losing visibility of the issue. Error message toasts now include a new Archive option that allows users to move the message to the Notifications panel for later reference.
REST and SOAP API access enhancements
Custom REST and SOAP APIs in webMethods Integration can be configured to allow both public and private access. From more information, see Creating REST APIs and Creating SOAP APIs.
Model Context Protocol (MCP) support enhancements
webMethods Integration now uses Stream able HTTP to communicate with the MCP server. Services that are exposed as MCP tools can now easily be disabled and re-enabled. For more information, see MCP Tools.
Connector enhancements
New connectors
  • FreshsalesCRM - FreshsalesCRM enables you to manage sales processes by creating, updating, and tracking contacts, accounts, deals, and activities within workflows.
  • Google Gemini - Google Gemini enables you to use multimodal AI models to generate, analyze, and process text, images, and documents within workflows.
  • Mistral AI - Mistral AI enables you to integrate powerful language models to generate, analyze, and moderate text within workflows.
  • Ollama - Ollama enables you to run and manage local large language models to generate and process text within workflows.
  • Hugging Face - Hugging Face enables you to use pre-trained AI models for tasks such as text generation, translation, summarization, and more within workflows.
Updated connectors
  • Wrike - The Wrike connector has been updated to support the latest API version, v4, which improves compatibility and reliability.

  • Stripe - The Get Recipients action has been removed in this release because the corresponding API has been deprecated.

    Impact: Existing integrations using this action must be updated or removed before upgrading to this release.

  • Amazon Simple Storage Service (S3) - The Amazon Simple Storage Service (S3) now supports IAM Assume Role authentication, enabling secure access to Amazon S3 resources using temporary credentials. You can configure role-based authentication in one of the following ways:
    • Provide the Role ARN, Role Session Name, and optional External ID. The connector automatically generates and manages temporary credential sessions.
    • Provide pre-generated temporary credentials obtained through the AWS CLI, SDK, or API.
    Note: Temporary credentials are valid for the configured duration of 3600 seconds by default.
Deprecated connectors
  • The following connector versions are deprecated and are no longer supported:

    Impact: Integration assets that reference these connector versions will fail at runtime with No connector found or Connector is null errors. These connector versions have been permanently removed and are no longer available for execution.

    Action: Review your existing integration assets and update them to use a supported connector version.

Multi-Threaded Kafka Listener Support

The Kafka connector now supports multi-threaded (parallel) Kafka listeners, enabling concurrent message processing across multiple Kafka partitions. You can configure a single listener with multiple worker threads, each with its own isolated consumer connection, to significantly increase message throughput without manually replicating listener nodes.

Imported Package Account Support

You can now select and use imported package accounts when configuring Database, SAP ERP, IBM MQ, IBM Power, and Kafka connections.

Concurrent messaging support for topics
Messaging topics now support concurrent messaging.

May 2026

Changes to editing Integration Agent‑created workflows
In the March 2026 release, the Integration Agent allowed you to edit workflows only within the agent and only when you made no manual changes. Starting with the May 2026 release, you can edit workflows that are created by the Integration Agent even after making simple changes outside the agent. Only workflows that are created by the Integration Agent are eligible. This update allows limited flexibility for making minor edits while maintaining safeguards that prevent potential issues.

When workflows are edited outside the Integration Agent, support is limited to the following changes.

  • Supported changes
    • Utility nodes: Loop, Logger, Switch
    • Connector nodes: Existing connector nodes can be modified, and new connector nodes can be added, provided they are recognized by the Integration Agent
  • Unsupported changes
    • Adding utilities outside the supported list
    • Existing mappings or lookup definitions, which may not be retained after editing
Workflows
Introducing correlation IDs

You can now set a custom correlation ID when you configure the Wait for Callback action. The system appends this correlation ID to the execution URL, and you can use it to resume the workflow. This provides an alternative to the existing execution ID, which the system also sets and appends to the execution URL used to resume the workflow. For more information, see correlation ID.

Enabling retry execution for actions

You can now configure individual workflow actions to automatically reexecute within the same workflow run if they fail during execution. Previously, you could reexecute only workflow from the point of failure. For more information, see enabling retry execution for actions.

Expanded project variable substitution support
Project variable substitution support has been expanded to connector accounts beyond Salesforce connectors that use credential-based authentication. You can now substitute project variables in additional account fields, except for transient fields and fields with predefined drop-down values. The new Substitute project variables icon makes inserting variables easier and more convenient.
Note: This feature is not supported for the SAP S/4HANA® Cloud, SAP S/4HANA Marketing Cloud, and Workday connectors.

For more information, see Using project variables in a connector account.

Connector enhancements
Updated connectors
  • MQTT - A new action, Publish Message, is introduced to publish messages to an MQTT broker or topic.
  • AMQP 1.0 - The AMQP 1.0 connector has been updated to version 3 (v3), adding support for topic-based (publish-subscribe) messaging in addition to the existing queue-based (point-to-point) messaging. It also supports wildcard topic subscriptions, depending on the capabilities of the AMQP broker being used (such as Amazon MQ, Solace, or ActiveMQ Artemis). This update is fully backward compatible, and no action is required for existing implementations.
Removed connectors

AS2 connector is removed in this release and is no longer available.

New APIs for Packages
A new set of public REST APIs are now available to help users to create and manage packages. Key capabilities include:
  • Pull or repull the main project package from its Git source.
  • Pull or repull all dependent system packages in a single operation.
  • Delete the package from the environment.
For more information, see Package APIs.
Support for recursive document expansion limit
Recursive document structures in package services now appear up to five levels in the Flow Editor. This fixed limit provides a consistent and manageable view of nested or repeating data. For more information, see Package services.
Built-in services

The following Pub JSON services are now available in the deploy anywhere flow editor:

  • pub.json:documentToJSON
  • pub.json:jsonToDocument
  • pub.json:closeArrayIterator
  • pub.json:getArrayIterator
  • pub.json:getNextBatch
  • pub.json:documentToJSONString
  • pub.json:jsonStreamToDocument

For more information, see JSON services.

March 2026

Integration Agent enhancements
Creating projects - The Integration Agent now enables automated project creation, providing a structured metadata framework to organize and manage integrations. Automating this process significantly enhances productivity by reducing manual setup steps and streamlining the workflow initiation process. When you request workflow creation, the agent confirms whether to use an existing project or create a new one. If you opt for a new project, the agent generates it automatically from your prompt and proceeds to workflow authoring. By embedding project creation into the AI-driven workflow, users gain a more intuitive and efficient integration experience. This approach enables the agent to handle key actions like project setup and workflow management, boosting productivity and supporting fully conversational integration development.
Creating custom actions - This Integration Agent now allows you to create custom workflow actions during workflow authoring. The agent automatically detects when a custom action is required and generates it, eliminating the need for manual pre-configuration. By analyzing workflow requirements, discovering available connectors and their capabilities, and prompting for account selection when needed, the agent creates and integrates the custom action into the workflow. This enhancement extends connectors beyond standard operations to support specific integration needs without manual setup. It reduces workflow creation time and lowers the technical barrier for users. It also improves authoring success rates, without interrupting workflows to manually configure custom operations.
Editing workflows - The Integration Agent now allows you to update workflows by using natural language prompts without manual editing. For example, you can now add, remove, or modify nodes, reorganize steps, and update workflow details through conversational commands. Before any changes are applied, you receive a confirmation summary to review and approve, which can ensure that you maintain full control over modifications. The review-before-apply approach improves accuracy and prevents unintended changes. The agent supports multiple modifications within a single session, which reduces editing time and streamlines the process of updating workflows. As a result, iterative refinement is faster and more intuitive than traditional manual editing. If a workflow is created by using the Integration Agent, it can be modified with the Integration Agent only if there are no manual changes.
Integration authoring with feedback loop - The Integration Agent now engages in interactive dialog during workflow authoring, asking targeted clarification questions when needed. The guided approach can ensure that workflows are accurate and aligned with your goals, while it allows you to add details such as account selection and configuration options as you go. Instead of stopping abruptly or showing generic errors, the agent enables natural back-and-forth interaction, making authoring more intuitive and flexible while you iteratively refine requirements without assumptions. The conversational approach improves accuracy and increases overall success rates, creating a more efficient workflow authoring experience.
Chat history - The Integration Agent now maintains an organized history of your chat interactions, allowing you to revisit previous integration generation sessions and continue from where you left off. To view the chat history, click the overflow menu icon that is located in the upper-left area of the agent. Each conversation is saved as a navigable chat with a title automatically generated from the first few words of the discussion. The title updates as the conversation progresses, helping create a structured record of your integration development work. You can return to any chat and resume the conversation in context, allowing the agent to continue processing the integration from the same point. Each chat has an options menu next to its title, providing actions to Pin to top, Rename, or Delete the conversation. These features let you manage your chat history by pinning important chats, renaming conversations, and deleting sessions. You can also search for conversations to quickly find specific chats. Chats are automatically sorted by last updated time, making it easy to access your most recent activity.
Data retention - To enhance privacy and support enterprise compliance, the Integration Agent retains conversation data for 30 days after which it is automatically deleted. During this period, you can access and manage your chat history to stay organized and revisit previous conversations.
Public APIs enhancement
Publishing projects - Starting with the 12.0.1 release, you can publish projects along with their valid assets to a target tenant. For more information, see Publishing projects.
Connector enhancements
Updated connectors

  • Salesforce® CRM - SOAP - The Salesforce trigger is renamed to Salesforce® CRM - SOAP to provide clearer identification. The trigger events in this connector remain available and unchanged.

    • Existing trigger configurations - No action is required. Existing triggers continue to operate without change.
    • New trigger configurations - Use Salesforce® CRM - SOAP when you create new triggers.
  • Connector namespace changes
    • Namespace updates are applied for connectors to align with product branding and improve consistency across the platform.
      • In existing projects or assets, two connectors with the same SaaS backend version may appear in the environment.
      • In new projects, only the updated connector version is available.
      Backward compatibility
      • The original connectors use the softwareag namespace.
      • The new connectors use the webmethods namespace and display a “.1” suffix (for example, Salesforce CRM REST‑version:60.1). This approach maintains backward compatibility while clearly distinguishing between namespace versions.
      Impact on integrations
      • Existing integrations require no immediate action and continue to function without changes.
      • New integrations should use connectors with the webmethods namespace, indicated by a “.1” suffix.

    • As part of the connector namespace updates, updated versions of the following connectors are now available for newly created projects:

      • Cloud Container
      • FTP
      • HTTP
      • JMS
      • Messaging
      • PGP
      • SFTP
      • SMTP

      These updated versions align with the new namespace conventions introduced across the platform.

      Impact on integrations
      • Existing accounts and projects will continue to display and use the earlier connector versions to maintain backward compatibility. There is no impact on existing integrations, and no changes are required for currently configured accounts or projects.
      • For newly created projects, only the updated connector versions that follow the new namespace conventions are available.
Deprecated connectors

AS2 - The AS2 connector is deprecated and will become obsolete in the next release.

Workaround - Use webMethods B2B Integration to exchange documents over the AS2 channel.

Removed connectors
The following connectors are removed in this release and are no longer available:
  • Cumulocity IoT
  • Cumulocity IoT OEE
  • ARIS
  • ARIS Process Mining
  • AgileApps

Because these connectors are not IBM‑owned, they cannot be supported. Any integrations or configurations that depend on them stop functioning after the upgrade.

Recommended guidelines

  • Review integrations that use these connectors.
  • Identify supported alternatives and migrate where applicable.
Automatic custom REST connector creation enhancements
Users can now create REST connectors by using Swagger or OpenAPI files with hundreds of resources without the process stopping. Connector creation is split into two parts. The deployment happens synchronously, and predefined operations are generated asynchronously in the background. You receive notifications when operations get created and when they are complete. Until then, the connector cannot be edited. This update improves performance and provides a smoother experience for large specifications.

For more information, see Creating a custom REST connector from a URL.

FTP and SFTP connector support for deploy anywhere flow services
Users can now use FTP and SFTP connectors in deploy anywhere flow services.
Deployment wizard enhancements
The Deployment feature is enhanced to support the promotion of projects along with their configuration settings. Previously, even if users exported all project assets, configuration settings had to be manually re-created in the target environment. With this enhancement, users can now publish and deploy both project assets and configurations across environments, eliminating the need for manual reconfiguration after publishing. To support these changes, the layout of the Deployment wizard is updated. Also the configuration values that are entered during deployment are not saved until the deployment process is completed. This option is to make sure that only finalized configurations are applied, reducing the risk of partial or incorrect setups. For more information, see Deploying projects and Publishing and deploying deploy anywhere projects.
Bearer-token authentication type for GitHub repositories
The GitHub version control accounts now support the bearer-token authentication type for accessing GitHub repositories. This method provides a secure, standardized alternative to Personal Access Tokens (PAT) for accessing repositories. Existing connections that use PAT remain supported.

For more information, see Configuring Git accounts.

Customer actions
Find information on the actions that you need to perform before or after you upgrade to webMethods Integration.

December 2025

Integration Agent enhancements
  • The IBM webMethods Hybrid Integration platform agent and webMethods Integration capability agent are now unified for a seamless experience. You can start conversations at the platform level, and integration-specific prompts automatically route you to the webMethods Integration capability agent with full context.
  • You can now create workflows across multiple conversational turns, while the agent retains context and refines the authoring plan incrementally. You can update the workflow through prompts or the canvas, and it is finalized only after your confirmation, enabling a flexible, context-aware, collaborative experience.
  • The agent can now automatically generate the appropriate workflow trigger as it creates workflows from prompts. It configures polling triggers, clock triggers, and webhook triggers based on the workflow plan. In the Edit Plan window, you can review the generated trigger details and add any additional parameters as needed.
  • The agent now supports Switch Case and Loop in workflow creation, enabling faster and complete workflow development.
  • The agent now interprets source and target schemas and generates data mappings automatically. This update removes manual mapping, accelerates workflow creation, and helps to create accurate, schema-aware integrations. After deployment, the agent also prompts with Yes or Ignore to view the completed workflow, displaying it for review when Yes is selected.
  • You can now run documentation prompts for any capability to explore features, understand their benefits, and discover new capabilities to enable.

For more information, see Building workflows with AI.

Projects
The Projects page has been updated with a refreshed look and feel, clearer project card indicators, and a persistent dashboard view state to make navigation easier. For more information, see Creating projects.
Connectors
Added connectors
  • constructValidateInput: Creates the input signature for the validate operation.
  • validate: Validates messages in webMethods B2BwebMethods B2B Integration runtime.
Updated connectors
  • Atlassian Jira: The Atlassian Jira connector has been updated to enhance request handling by correcting the input signature for the deleteAndReplaceVersion operation.
  • Amazon Redshift: The Amazon Redshift connector has been updated with a numeric-type check to correctly handle and return decimal fields too in the response.
  • The following connectors have been updated to support the standardized error message format, which now includes summary, explanation, and action fields.
    • Asana
    • Microsoft SharePoint Online
    • GitHub
    • Slack
    • Microsoft OneNote
    • Microsoft OneDrive
    • Microsoft OneDrive for Business
    • Aha
    • Okta
    • Jotform
    • Microsoft Office 365
    • Weather Underground
    • Pipedrive
    • Todoist
    • DropboxSign
    • Wrike
    • Trello
    • PagerDuty
  • The following enhancements have been made to custom Node.js actions and Node.js based transform operations.
    • Removed the x12 package.
    • Upgraded the netlify package to version 13.3.5.

    For more information, see Supported modules and Supported transform operations.

Removed connectors

ShareThis: The ShareThis connector has been removed in this release.

Develop anywhere, deploy anywhere integrations

A new Runtimes option is available within a project. This enhancement provides a centralized location to manage all runtimes associated with the selected project. With the runtimes option, you can:

  • Add runtimes directly to the project.
  • Create virtual runtimes as placeholders for runtimes and map them to any runtime. The virtual runtimes simplifies the transition between development, testing, and production environments.
For more information, see Runtimes view associated with projects and Virtual runtimes.
Enhanced Smart Mapping

The Smart Mapping feature has been enhanced to leverage community-driven data for smarter, more accurate predictions. This enhancement integrates privacy-protected mapping insights from the webMethods Integration community, enabling the system to learn from real-world usage patterns while maintaining strict data privacy standards. For more information, see Using smart mapping.

Support for API tokens for Bitbucket version control accounts

Users can now use API tokens as a new authentication method for Bitbucket version control accounts. Bitbucket Cloud no longer supports App Passwords for authentication. This enhancement provides a secure and flexible alternative to App Passwords that complies with Bitbucket Cloud’s updated authentication standards. For more information, see Configuring Git accounts.

Customer action

Existing version control accounts that were set up with App Passwords will continue to function, but you must plan to migrate them to a supported method. For example, you can use API tokens before the App Passwords expire. To update the existing App Password version control accounts:

  1. Generate a token for those accounts.
  2. Update the version control account in webMethods Integration with the new token.
  3. Validate the connection by clicking the Validate button in the Add Git account dialog.

November 2025

Supported connectors for Private Links

You can establish secure outbound connections to your private VPC by using private links. The following connectors are certified on webMethods Integration:

Learn how to invoke workflows and flow services with Private links.

Updated Shopify connector

The Shopify connector is enhanced to support the following new triggers:

  • New Product
  • New Customer
  • New Order
  • Order Paid
  • Order Cancelled
  • Order Edited
  • Order Fulfilled
  • Order Updated

For more information, see Shopify.

October 2025

Projects

Notification settings enhancements: The Project management notification category is added under Notification settings > Subscriptions. By default, all users with access to a project are automatically subscribed to this category. The Project management category currently sends notifications about project deletion events and keeps users informed when a project is removed. For more information, see Managing notifications.

Default project deprecated for new tenants: New tenants no longer have the Default project provisioned automatically. Users must create a project manually when they log in for the first time. Existing tenants retain their current Default project, which, as before, cannot be renamed or deleted. For more information, see Projects.

Project parameters: You can now mark project parameters as password-protected only during creation. This release removes the ability to mark or unmark parameters as password protected when updating them through the user interface or public API. For more information, see Updating project parameters through the user interface and Updating project parameters through the public API.

Self-service, goal oriented agentic integration authoring
You can use the self-service, goal-oriented agentic integration authoring feature to create integrations by describing your goals in natural language. The Integration Agent interprets the intent, generates a plan, and automatically builds and deploys the workflow. This self-service approach removes the need for deep technical or domain expertise, reducing dependency on integration specialists, and allowing them to focus on strategic priorities. The agent boosts productivity and agility by simplifying and accelerating the workflow creation process. For more information, see Building workflows with AI.
Workflows
Execution settings enhancements
  • The Save status of each successfully executed action and Maintain workflow execution logs when executed via webhook or trigger options are removed and replaced with two new options:
    • Enable workflow to be resumed: Allows the workflow to resume from the last successful action after a failure.
    • Enable workflow to be restarted: Allows the workflow to automatically restart from the beginning after a failure.
  • Log settings: Specifies the level of detail that is captured in workflow execution logs.

    For more information, see Execution settings.

Flow services

pub.date:stringiness: The pub.date:stringToDate service is added to built-in services, allowing conversion of string values into date objects. For more information, see Datetime services.

Time zone support for flow service scheduling: When you schedule a flow service, you can now specify the time zone to help ensure that the flow service execution occurs at the intended local time. The time zone setting applies to both one-time and recurring schedules. For more information, see Working with flow services.

Retention period for custom log messages: You can now configure the retention period of custom log messages for flow services by using the Modify Retention Period link in the execution details for the flow service. For more information, see Viewing flow service execution logs.

Develop anywhere, deploy anywhere

Support to import projects from external Git repositories: The Import project option is provided for deploy anywhere projects that allow users to restore deleted projects or import other projects from different environments into their current workspace. This enhancement simplifies project recovery and helps reduce downtime. Imported projects now include associated assets such as project variables, reference data, and document types, making them usable in both Flow services and Deploy Anywhere Flow services. For more information, see Importing deploy anywhere projects from external Git repositories. Currently, workflow, workflow parameters, APIs, and IC services are not included.

Support for predefined actions in connectors for deploy anywhere flow services: Few connectors that are used in deploy anywhere flow services are enhanced to support predefined actions, allowing for more streamlined and consistent integration across environments. These actions are built into the connectors and can be started without requiring custom logic or manual configuration. Using predefined actions in connectors enables faster development, consistent behavior across environments, reduced errors, and easy maintenance through standardized, reusable functions. For more information, see Using connectors in deploy anywhere flow services.

Improved package variable management: Package variables can be updated through configuration settings. These changes apply only within the project and do not sync with external repositories. If overridden from self-managed runtime, those values take priority. You can also revert to default package values or mark variables as password fields to secure sensitive data. For more information, see Updating package variables.

Enhanced package version management: The enhanced package version mechanism now supports version comparison and contextual messaging. When a package is added, the runtime replica checks if the same or a newer version exists. Based on this evaluation, it avoids redundant installations, allows upgrades when appropriate, and blocks downgrades to maintain consistency across shared projects. Previously, packages were reinstalled regardless of version, with only a generic message shown. This enhancement improves package lifecycle control, reduces unnecessary operations, and can ensure consistency across shared projects. For more information, see Updating packages.

Support for globalVariable:multivariable: Deploy anywhere flow services now support the globalVariable:getGlobalVariable service, enabling direct access to global variables within your flows. The service allows users to retrieve a global variable that is defined in their project package without requiring any custom wrapper services or more configuration. For more information, see globalVariable:getGlobalVariable.

Enhanced debugging support: New debugging options Step-in and Step-return are provided for users to step in and step out of services or loops. This option enables detailed inspection of logic and more efficient troubleshooting, directly within the editor. For more information, see Steps to debug flow services.

Improved sync experience in deploy anywhere flow service: The sync operation is improved and users can edit flow services while synchronization is in progress. Also, notifications now indicate when the sync process begins and ends. For more information, see Downloading sync reports.

Update the account information for connectors: Users can now update the account information for the connectors that are used in deploy anywhere integrations from the Connectors > Deploy anywhere page. The edit option is displayed when a user hovers over the account. For more information, see Editing connections in deploy anywhere integrations.

Support for deploy anywhere flow services in REST APIs: Users can now use deploy anywhere flow services to create REST APIs, and publish and deploy them. For more information, see Using deploy anywhere integrations in REST APIs.

Improved error display in deploy anywhere flow services
  • Errors related to any connector connectivity issues are shown on the Results page. Users no longer need to go to specific steps to view these errors. This enhancement makes the troubleshooting quicker and more efficient.
  • The Throw Exception on Error option is available for deploy anywhere flow services when creating custom actions. If enabled, any exceptions that occur during the running of a custom action are forwarded to the deploy anywhere flow service. Users no longer need to go to specific steps to view these errors. This enhancement makes the troubleshooting quicker and more efficient.

    For more information, see Using connectors in deploy anywhere flow services.

Enhancements to deploy anywhere integrations in workflows
  • Timeout settings for package services: Users can now configure a timeout for Package Service invocations in workflows using the Timeout in seconds option in the Settings dialog. A timeout exception occurs if the service runs longer than the defined limit. This limit must be lesser than the timeout limit specified for workflows.
  • Enhanced runtime traceability in workflows and monitoring: The workflow canvas and monitoring pages now include details that indicate the runtime on which the deploy anywhere flow service is run.

    For more information, see Using deploy anywhere integrations in workflows.

Auto commit enhancements: Administrators can now enable the auto commit feature from the Preferences tab. If enabled, the changes are automatically committed to the repository when they save the changes. If an error occurs, you can fix it and commit the changes manually. For more information, see Auto commit Git actions.

Pipeline view enhancements
  • Users can now hover over the Set Value field to view the configured values, without needing to click or open the field box.
  • Users can resize the pipeline view window to better suit their preferred layout.

    For more information, see Pipeline.

Git account details for packages: Users can now update Git account details for a package. With this enhancement, a dedicated Git account can now be associated directly with a package. This account is associated with the package and is created within the project. The user who created the package owns and manages it. The Git account can be configured and edited from both the Package View and the Version Control pages, giving package owners full control over access and management. For more information, see Updating packages.

Shared Git accounts: Users can now share their Git accounts with others to facilitate collaboration. Shared accounts allow users to pull the recent changes from a repository into their workspace. Shared Git accounts are read-only. They cannot be used to commit changes or create new projects. For more information, see Configuring Git accounts.

Viewing and running package services: Users can now explore flow service assets in more detail. By selecting a flow service, they can open it in the flow editor to view its steps in read-only mode. Editing remains disabled. Users can also run the services and inspect their input and output signatures. Previously, users were able to view only a list of assets available in package services.

Syntax update for deploy anywhere flow services: Syntax update is done to several controls within the deploy anywhere flow services. This update helps ensure a consistent editing experience across both the flow editor and the IBM webMethods Designer. It enhances alignment between tools and improves compatibility across various development environments.

Automated variable sync in Cloud Design time: Newly added project variables are now automatically synced with the Cloud Design time, which was not so earlier. If the variable values are not in sync with the Cloud Design time, a warning icon is displayed next to the variable name. Users can update these values and make sure that the project variables are in sync with the runtime environment. Also, the Sync Variables option is provided to sync all variables. For more information, see Syncing project variables.

Cloud messaging
Clear queued messages for suspended subscribers: Clear option is added, which enables administrators to remove pending messages from suspended subscribers. It helps prevent message backlog, reduce resource usage, avoid processing delays, and ensures smooth reactivation without overwhelming the subscriber. Previously, it was not possible to delete messages from a suspended destination. As a result, after the configured limit was reached, older messages were dropped and lost due to insufficient space for new ones. For more information, see Creating messaging destinations.
APIs

Enhancements to REST API response codes: Users can define other response codes for successful responses as needed. Previously, only the default success response code (200) might be defined and it was non editable. Also, users can update and delete the existing success response code. However, if only one response code is available, then that code cannot be deleted. For more information, see Creating REST APIs.

Integration APIs available in webMethods Developer Portal: All webMethods Integration APIs are now accessible through the webMethods Developer Portal, making it easy for developers to discover, explore, and use APIs for building integrations. For more information, see Developer Portal.

New set of APIs
  • Project configurations

    A new set of public REST APIs is now available to help users to promote projects. Previously, while users were able to export all project assets, they had to manually re-create configuration settings. With the new APIs, users can export and import the project configurations across environments, without the need for any manual reconfiguration after project import.

    APIs are provided for managing configurations based on the following categories:
    • Certificates
    • Schedules
    • Alert rules
    • Project parameters
    • Project variables
    • Vault variables
    • Connections
    • Project configurations
    • Git version control accounts

      For more information, see Public APIs.

  • Workflows
    • Fetch execution payloads: Retrieve the original payload that triggered a workflow execution.
    • Restart workflows: Restart a previously run workflow that failed, been stopped, or timed out.
    • Configure retry mechanism: Enable automatic retries for failed workflow actions by setting retry intervals and maximum attempts.
    • Fetch detailed execution logs: Retrieve comprehensive logs for workflow executions.

    For more information, see Workflow APIs.

  • Flow services
    • Restart flow services: Restart a specific flow service execution instance

    For more information, see Restarting flow services.

Usage Analytics
All metrics that are defined in IBM webMethods Hybrid Integration contracts are now converted to resource units and submitted to the IBM SaaS Console. This enables users to view resource-unit usage.
Connectors
  • IBM watsonx.ai: IBM watsonx.ai is a component of IBM's AI and data platform that enables you to work with both generative AI and traditional machine learning models. It provides tools to create, customize, and fine-tune models to meet your specific needs. The platform supports a wide range of options, including IBM-developed models, open source models, and the flexibility to integrate your own.
  • DocuWare: The DocuWare connector has been updated with the following enhancements:
    • The connector is upgraded to version 7.
    • A new and more secure authentication method, OAuth 2.0, is implemented. Starting with version 7, only OAuth 2.0 is supported, and basic authentication is no longer available.
  • Microsoft 365 and Microsoft Dynamics 365 CRM: The Microsoft 365 and Microsoft Dynamics 365 CRM connectors are updated to support refresh token rotation to help ensure enhanced security, and more secure authentication.
  • NetSuite: The NetSuite SOAP connector is updated to the 2024_2 version, where SOAP headers can now be edited and managed within the pipeline.
  • Sitecore Experience Platform and Microsoft Dynamics Business Central: The Sitecore Experience Platform and Microsoft Dynamics Business Central connectors now comply with the latest security updates by using the newest secure versions of their underlying JAR files.
  • The following connectors are enhanced to improve log security by redacting sensitive data:
    • Miro
    • Microsoft Azure Data Lake
    • Salesforce CRM – SOAP
    • Sitecore Experience Platform
    • OData V4.0
  • The following connectors are enhanced with improved error handling mechanisms:
    • NetSuite
    • Salesforce CRM - SOAP
    • Marketo
  • SAP S/4HANA: The SAP S/4HANA connector is updated to support a new operation, Create with Deep Insert to help you create a single entity or a single entity with deep insert, along with related child entities, in one request.
  • AMQP 1.0: AMQP 1.0 connector enhancements:
    • Use the Reject Unauthorized field to disable SSL/TLS certificate validation by setting it to false.
    • Support for custom key-value pairs with specified data types to enable more flexible configurations.
  • File: The Decrypt PGP File action of the File connector is updated to use the openpgp npm library, version 6.1.1. The Decrypt PGP File action of the File connector is updated to v2, which uses the latest openpgp npm library, due to security vulnerabilities in the previous version (v1). Use the Decrypt PGP v2 to help ensure that it uses the latest and more secure version of the library.
  • Campaign Monitor and ActiveCampaign: Campaign Monitor and ActiveCampaign connectors have been updated to use the axios npm library, as the previously used request npm package is now deprecated.
  • Webmaster Tools: The HTML Validator action of the Webmaster Tools connector is updated to support the w3c-html-validator npm library, version 1.8.3, in both version 1 and version 2.
  • SuccessFactors HCM: Added support for a query parameter in the query operation of SuccessFactors HCM. This enhancement applies to all business objects and enables users to filter records more effectively by providing query parameter values in the connector.