Assets supported in workflows
Workflows support cloning, exporting, importing, publishing, and deploying to manage and migrate assets across projects, tenants, and regions efficiently.
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
- 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
- Export or import a workflow or flow service. When you export a workflow or flow service, a compressed file is created containing all assets along with its dependencies that are used in that workflow or flow service. The compressed file is saved to your local drive's default download path. The compressed 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
- Promote assets across regions, cloud providers, and data centers. It is possible to select multiple assets and publish them all at the same time. The project and assets are named the same. When redeploying, it updates the existing assets with the new data.
The following table lists the functions that are supported for workflows.
| Feature | Clone | Export and Import | Public and Deploy |
|---|---|---|---|
| Workflow with Predefined connectors | Yes | Yes | Yes |
| Workflow with Custom CLI app | Yes | No | No |
| Workflow with Custom CloudStreams connectors | Yes | Yes | Yes |
| Workflow with REST connectors | Yes | Yes | Yes |
| Workflow with SOAP connectors | Yes | Yes | Yes |
| Workflow with On-Premises connectors | Yes | Yes | Yes |
| Workflow with Adapters- Workflow is yet to support SAP adapter. | Yes | Yes | Yes |
| Workflow with Flow services | Yes | Yes | Yes |
| Workflow with Messaging | Yes | Yes | Yes |
Note: If a workflow contains a flow service that uses either a webMethods B2B connector or
a Flat File connector, then all operations work, and dependencies are retrieved, created, and
deployed.