Assets Supported in Workflows
No subtopics in thissection
All assets that can be used with workflows and flow services can be cloned, exported, imported, published, and deployed. These functions are helpful when migrating, promoting, or copying the existing flows.
Clone - Allows you to create a new workflow or flow service that is identical but separate from the original workflow or flow service. You can clone the workflow or flow service to the same or different project but within a tenant.
Export and Import - Allows you to export or import a workflow or flow service. When you export a workflow or flow service a zip file is created containing all assets along with its dependencies used in that workflow or flow service. The zip file is saved to your local drive’s default download path and this zip file can be used to import those assets either in the same tenant or a different tenant. It can be in the different region as well.
Publish and Deploy - Allows you to promote assets across regions, cloud providers, and datacenters. It is possible to select multiple assets and publish them all at the same time. The project and assets are named the same. In case of redeploying, it updates the existing assets with the new data.
The following table lists the functions that are supported in the current product version for workflow:
Feature | Clone | Export and Import | Publish and Deploy |
---|---|---|---|
Workflow with Predefined connectors | Yes | Yes | Yes |
Workflow with Custom CLI app | Yes | No | No |
Workflow with Custom CloudStream connectors | Yes | Yes | Yes |
Workflow with REST connectors | Yes | Yes | Yes |
Workflow with SOAP connectors | Yes | Yes | Yes |
Workflow with OnPremises connectors | Yes | Yes | Yes |
Workflow with Adapters Note: SAP Adapter is yet to be supported by workflow. |
Yes | Yes | Yes |
Workflow with Flow services | Yes | Yes | Yes |
Workflow with Messaging | Yes | Yes | Yes |