Deploy anywhere flow services

A deploy anywhere flow service is a flow service that is platform independent. You can develop integrations on any environment or platform, and then deploy that same integration to various target environments without major modifications.

Key points to consider for deploy anywhere flow services

  • Self-managed runtime selections are not shared across users or browsers. For example, if you create a deploy anywhere flow service using an edge runtime, the selection is stored in the user’s browser cache. When another user opens the same asset, the mapping defaults to Cloud Designtime. This is because the self-managed runtime selection applies only to the specific user and browser in which it was configured.
  • The Built-in Services that are not supported for deploy anywhere services are,
    • Document - findDocuments, removeNullFields
    • FlatFile
    • Flow - CountProcessedDocuments, getHTTPRequest, getLastError, getSessionInfo, logCustomMessage, Sleep
    • IO - streamToString, stringToStream
    • JSON - documentToJSONBytes, documentToJSONStream, jsonBytedToDocument, jsonStringToDocument
    • MIME
    • StorageServcies
    • String - fuzzyMatch
    • XML - DocumentToXMLBytes, DocumentToXMLStream, DocumentToXMLString, XMLBytesToDocument, XMLNodeToDocument, XMLStreamToDocument, XMLStringToDocument, XMLStringToXMLNode

    As a result, imported packages that rely on the mentioned services does not function properly without refactoring.

  • The warning message is not displayed when a deploy anywhere flow service is exported.
  • The Overview option is not available for deploy anywhere flow services.
  • The self-managed runtime linked to a deploy anywhere flow service does not get cloned and is reset to cloud runtime. Set the self-managed runtime and save the cloned deploy anywhere flow service.
  • When cloning a deploy anywhere flow service, the self-managed runtime details are not saved. By default, it is reset to Cloud Designtime.
  • Importing a workflow that uses the deploy anywhere flow service does not import those services. The service must be imported manually.
  • Deploy anywhere flow services cannot be created in the default project.
  • Deploy anywhere flow services does not support the following functions:
    • Debugging
    • Look-up transformers
  • Importing and exporting of deploy anywhere flow services for custom actions for connectors is not supported. When projects have other package dependencies, the import and export feature does not handle these dependencies. For utilizing custom actions, the dependencies must be configured manually when using import and export. Therefore, it is recommended to use publish and deploy to manage dependencies appropriately.
  • Predefined connectors
    • Only connectors from the Supported repository are available for use.
    • Only the latest version of the CloudStreams Connector provider packages is supported.
    • The default authorization is not supported when you configure accounts for connectors.
    • For configuring new connections, default values are pre-filled. You only need to update the fields to change the pre-filled values.
    • The connector account credentials are not validated during deploy anywhere flow services execution process. Make sure that you have entered the correct credentials. If authentication issues occur, test with a known valid credential set.
    • Before using connectors to link various applications and services, ensure that the runtime status is set to Ready. This is crucial for the proper functioning and integration of the connectors.
    • After synchronization, the connection date in Cloud Designtime matches the connection date in the remote runtime or self-managed runtime.
    • The following connectors are not supported.
      • WmOracleFSCMCloudProvider
      • WmAgileAppsProvider
      • WmAgileCRMProvider
      • WmAmazonRedshiftDataProvider
      • WmApi2PdfProvider
      • WmArisProcessMiningProvider
      • WmArisProvider
      • WmB2BProvider
      • WmCloudmersiveNLPProvider
      • WmCowinProvider
      • WmCumulocityOeeAppProvider
      • WmDataPoliceUkProvider
      • WmDocuwareProvider
      • WmGainsightNXTCSProvider
      • WmGainsightCSProvider
      • WmGoogleBillingProvider
      • WmGoogleAIPlatformProvider
      • WmKakaoDaumSearchProvider
      • WmMailgunProvider
      • WmSalesforceMarketingCloudProvider
      • WmMBCProvider
      • WmMelissaDataEmailVerifierProvider
      • WmOracleRetailMerchandiseProvider
      • WmPastebinProvider
      • WmRemovebgProvider
      • WmRobinProvider
      • WmRSSProvider
      • WmSalesforceB2CCommerceProvider
      • WmSAPCommerceCloudProvider
      • WmSAPS4HANAMarketingCloudProvider
      • WmShortLinkProvider
      • WmSitecoreXPProvider
      • WmTinyURLProvider
      • WmAppsProvider
      • WmCoreWmioProvider
      • WmYNABProvider

Best practices for structuring integration flows

Adhere to the following guidelines to make sure that the integration flows are well-structured and easy to maintain.

  • Keep a single integration flow to approximately 100 steps or less.
  • Split complex integration logic flow into smaller, more focused sub flows or child flows.