Sliderule supports importing workflow versions across environments. This lets you maintain separate Development and Production environments of Sliderule, with separate data source credentials and user accounts.
- Source Environment - the environment you’re pulling a version from. Typically your Development environment
- Destination Environment - the environment your importing a version into. Typically your Production environment
Pick a workflow in you Source Environment - we like to use the sample Withdraw Funds workflow that comes with your account. Make a few changes, and save your new version of the workflow. Give it a name and Deploy.
Now, in your Destination Environment, create a new Workflow (call it Test Import). Open your Workflow, and click on the triple dot menu in the top bar to access Workflow level settings. Then click Import Workflow.
Select the Source Environment from the dropdown, and pick the Workflow you’d like to import. For each workflow, you'll have the option to import its currently deployed version in the lower environment. For example if you're on your Production environment, you can import the currently deployed version of each workflow on your Development environment.
- If your workflow contains Subworkflows, you'll need to confirm where you'll be importing those subworkflows to in the destination environment. If you've imported a subworkflow before, Sliderule defaults to wherever it was imported to last time, otherwise it defaults to creating a new copy in a new worklow
- If your workflow uses Data Connectors, Sliderule will attempt to match Credentials in the Destination Environment with the Credentials required for each Logic Block in the Workflow you’re importing. If there are any Credentials we can’t find a good match for, you’ll see a red warning icon, and you'll need to pick a Credential to use before proceeding.
You can alter the Credentials from the automated suggestions, and once you have Credentials selected for each requirement, click the blue Import button.
That’s it! All done!
versions are not automatically Deployed after import. You’ll have to follow the standard Deploy process in the Destination Environment
imports will overwrite any changes you’ve made in your Destination Environment
Updated about 1 month ago