Workflow Sections
Workflow Definition & Details
The workflow definition contains the core identifying information about your workflow:
Name & Description: The workflow name and its description provide quick context on what this workflow is for.
Attributes: Displays the organization that created the workflow, as well as the date and time of the last update.
Child Organizations: Lists all child organizations in your Swantide account that currently have access to this workflow.
Tip: Click directly into the list if you need to update which organizations have access.Published State: Indicates whether the workflow is published. Published workflows are available for deployment to any organization with access, in the Workflow Library. Unpublished workflows can be considered "Drafts."
Versioning: Shows the current workflow version. A new version is automatically created whenever a workflow is published or republished after edits.
Deployment Availability: Specifies whether the workflow can be deployed once (single deployment) or multiple times. For more details, see the Creating a Workflow help article.
Below the header, you’ll see additional workflow definition information such as:
Swantide Package Categorization
Integration Types (e.g., Salesforce)
Help URL
Workflow Tags
You can edit any of these attributes at any time by selecting Edit Workflow Definition.
Metadata Components
Located in the middle-left section, Metadata Components define what Salesforce metadata is being created or updated by the workflow.
For example, you may include metadata that create new flows or update existing pick-list field values. Metadata Components are the structural foundation of your workflow.
Variable Inputs
On the middle-right, Variable Inputs define the customizations to your metadata deployments. A variable allows users to select inputs based on the org they are deploying to in order to customize the solutions. For many Workflows, this is the special sauce that make Workflows so dynamic, and elevate them from copy/paste functionality.
Variable inputs allow you to variablize workflows and capture user-defined selections that affect metadata during deployment
Workflows that act as templates that "copy/paste" metadata components may not require variable inputs
Examples: imagine you are a salesforce consultant looking to package up some of your solutions into reusable assets by creating your own Swantide Workflow library.
Workflow with Variables:
Simple: let's say you have a validation rule or a series of validation rules that you want to deploy to each of your customer environments. The Validation rule only references standard Salesforce fields and formulas, so the formula does not need variables, but you want to rename the validation rule to have the specific customer's name prepended on deploy. For example CUSTOMERA_No_Edits_After_Close. This is a good example of a simple variable to simply type in the name of the customer on deploy that will be injected into the API name of the Validation rule as it is created, and all you have to do is click deploy.
Advanced: when working with clients, you frequently create custom objects to track a specific field's value changes, along with a flow to create records on the associated object when the field is updated. To achieve this with a Swantide Workflow, you will create the metadata components for the object, its corresponding fields, and a flow. You also need the ability for the deployer to select any pick-list field in their Salesforce to create the automation for. This represents a variable. Once defined, the variable entry will be injected into the defined metadata components so that the user's selection customizes the automation on deploy, so that the flow now triggers off of the selected pick-list field, and the custom object & fields are named after it as well.
Workflow without Variables:
When you work with new customers you frequently build the same set of fields in your customer orgs. You want to create a Workflow that automatically deploys these fields to Salesforce, with no customizations on deploy. This would be an example with no variables needed, just the field metadata components
Deployment Conditions
Deployment Conditions let you create rules for when a workflow becomes available for deployment.
Example:
If Workflow A must be deployed before Workflow B can be deployed, you can define this dependency in the Deployment Conditions.
This ensures workflows are deployed in the correct order and respects any necessary dependencies.
Workflow Test Deployments
The Workflow Test Deployments section tracks your test records once you begin testing Swantide Workflows.
This helps validate your metadata components and variable inputs before deploying to production. It’s a safe way to ensure your workflow behaves as expected.