With the release of today, you are now able to create and manage your configurations in sets to increase reusability. The value? Using configuration sets will reduce the time spent on developing or configuring your action steps. By managing the configurations in just one place, you don’t have to worry about going through all actions and its action steps to manually set up all needed values.
Before we dive in, let’s do a quick recap of what configurations are. Configurations can be used for a variety of things within the platform. They can be seen as a 'global' variable of some sort. Configurations allow you to reuse a value in multiple places, like in multiple action steps.
When a value in for example an action step changes, using a configuration could be very handy. Instead of having to re-adjust that value manually in all those action steps, you can simply change the value of the configuration and it'll be changed in all the steps where you've used the configuration in. Configurations can also be used to store stuff like login details or API keys.
In Q2, we will add the functionality to enable developers to add configurations to their multi-entity blocks.
That was all for now, your feedback allows us to continuously improve our product. Please let us know what you think about it. Happy building! 😃
Relevant articles: