Using Multiple Environments in Chains
Looking for a way to organize your Chains or manage their development lifecycle? Chain Environments can help with that!
Within workspaces, Workiva users are set up with a default DEV environment in Chains. In addition to the standard DEV environment, you can set up multiple custom environments to fit the needs of your organization.
Environments are a great option to help manage the development lifecycle of Chains and can add in an extra layer of structure and security if needed as well.
For example, you can set up separate environments for different teams or projects if you need to have more organization within your workspace and assign permissions accordingly.
Additionally, you can build and test chains in a DEV environment, and then promote them to a PROD environment when ready. This allows you to have a sandbox-like environment while curating your Chains.
You can also specify values for Workspace variables based on environment. In this instance, when you run Chains the variable value passed through to the chain can be different for a Chain in the DEV environment vs the PROD environment (more information on that in this post).
Please note that you will need to enable Connections in each environment if you have multiple in your workspace.
Want to continue the conversation? Leave a comment below!
-
Is it also possible to:
1) Rearrange the environments (i.e., change the order of them on the top bar when in the Environments tab)?2) Set which environment should be the default environment to open?
0
Hi Sindre Sjoebakk, those are both great suggestions. At this time, there isn't a way to rearrange the order that the environments appear in.
For the default environment, Chains will typically reopen with the last environment you used. However, there isn't currently a setting to designate a specific environment as the default.
For these and other enhancement ideas, I recommend posting them in the Data Management Feedback section.
0댓글을 남기려면 로그인하세요.
댓글
댓글 2개