Known limitations

The following points highlight additional information that you need to know to work with webMethods Integration.

webMethods Integration

Connectivity

Google connectors require a custom authentication scheme.

Programmatic token refresh is not supported for Salesforce v60 and Microsoft Dynamics 365 CRM connectors.

You cannot use Project Variable substitution for the following providers:
  • SAP S/4HANA® Cloud
  • SAP S/4HANA Marketing Cloud
  • Workday

Integration Agent

Prompts

See the prompt guidelines for details.

Workflows
  • All conditional statements must use Switch Case constructs.
  • Multi-node (action) workflows are supported only in a sequential manner. A sequential workflow follows a step-by-step order. (For example, When a New Event is created in Google Calendar, first create an event in Microsoft 365, and then post a message to the channel in Slack.) Parallel workflows are not supported. (For example, When a New Event is created in Google Calendar, create an event in Microsoft 365, and at the same time, post a message to a Slack channel.)
  • Multiple switch cases are not supported within the same workflow.
  • Nested or complex lookup structures in if-else conditions are not supported.
  • If workflows are modified outside the Integration Agent, existing mappings or lookup definitions may not be retained after editing.
Custom actions and utilities
  • Not all custom actions work consistently.
  • The Loop, Logger, and Switch utilities are supported, while other utilities are not.
  • Smart mapper suggestions are limited and might not work consistently.
Triggers
  • Only one trigger per workflow is supported. For example, Clock and Messaging are not supported for multi-trigger workflows because the Create New Trigger function is not available.
Other limitations
  • Within a project, workflows always use the most recently created account for a service.
  • The Load More option is not available in lookups.