Tenant and Project Variables
Learn how to create, update, delete, download, or upload tenant-level variables or project-level variables that can be used across flow services in a map set.
Pipeline substitution variables in flow service pipelines are only available within the current pipeline and cannot be reused across flow services or accounts. Alternatively, tenant and project level variables provide the flexibility to configure variables at either project level or tenant level for use across projects. This means that if a variable's value is changed at one point, it is available for use in all projects where the variable is used.
Flow services can now use either of the following variable types:
- Tenant-level variables
- Project-level variables
- Pipeline substitution variables
- First, webMethods Integration looks for variables in Pipeline substitution variables.
- If these are not found, it then checks Project-level variables.
- Finally, if neither pipeline nor project variables contain the variable, the system searches for it in Tenant-level variables.
Best practices
- To use project or tenant variables when publishing, deploying, exporting, or importing into another tenant, they must be configurable variables. Add dependency on these variables in the target Flow service or account to make them configurable.
- Cloning a Flow service across projects, does not copy the project variables to the target project. Configure these project variables in the target project, in such circumstances.
- Project variables can only be utilized with the Salesforce connector.
Use cases
You can use the Tenant and Project Variables feature for account configuration. In such use cases, values like passwords or host names are configured once in these variables and reused across accounts and flow services.