It’s been quite a while since we issued our last feature alert, but we wanted to wait until we finished this one special new feature. Now it is high time we introduce you to the integration flows versioning.
Changing integration flows has become fail-safe
Up until now, there have been a few ways to introduce changes in an active integration flow on our platform. However, all of them had certain limitations depending on the flow and/or the integration scenario.
The new integration flows versioning feature allows you to make changes to an integration flow while it is still running by first prompting you to create a draft of the active flow. Thanks to this, you can now tweak the flow configuration and test each change as much as you want to without affecting the original integration flow in any way. Only when you are absolutely sure that you have introduced the correct changes and tested them successfully – then you can publish the draft. This step will deactivate the original flow and active the draft as a new version of it.
This new way of introducing changes to integration flows has a few massive benefits in it. First of all, from now on you can roll back the changes in case they were not quite successful. (For that, you need to republish the original flow, which will then run as yet another version). Secondly, in the case when several people are working on one and the same integration flow, you can now see who exactly made the changes and when.
The introduction of the new feature has also brought some changes in the UI with it. You can read up on it as well as on the specifics of the integration flows versioning in our documentation LINK.
PLEASE NOTE: Since creating versions of an integration flow is a much safer way of introducing changes, we have disabled the option of changing the configuration in already existing flows, regardless of whether they are active and running or has been stopped altogether.
You can find some more specifics and details on this dedicated documentation page.
Further enhancements of the elastic.io UI/UX
Earlier this month we rolled out a cleaner and more uniform design of several sections in the dashboard of the elastic.io iPaaS. For example, this is how a Developers Team’s page looks like now:
(In case you never paid attention, here you can find a few pics how this page used to look like in the not so distant past, although some elements did change over the last year) You can find screenshots of other sections with the new look in our support documentation here.
Furthermore, now you can add a description for each integration flow – for yourself, for your teammates or for any other person who needs to know more about a certain flow than just its name. Or maybe you will use it to comment on the flow? Who knows 😉 Anyways, here is how it goes (pretty straightforward):
Last but not least, we have added a step summary section in the integration flow designer in case you need to look up some information specifically about the step, e.g. its description (yes, each step has now a description field, too).
What to expect in the coming weeks:
With the integration flows versioning feature we have reached a big milestone, but it only marks the beginning of our work on something more significant than simply allowing to make safe changes to integration flows. Now we have officially moved one step closer towards introducing a state-of-the-art lifecycle management functionality with the support for development-testing-production deployment pipeline – something that many of our users have been asking for.
Our goal is to provide the users of our integration platform not only with a safe way to change already working integration flows. More importanlty, we want to give them – or you, dear reader – a safe environment to develop, test and play around integration scenarios as long as needed until you are absolutely certain that your integration flows can be
set free put to production.
Apart from that, there are quite a few things to look forward to in the next weeks. We are planning on ending the beta phase of local agents very soon and will be working on a billing engine in order to provide billing KPIs for the users of the white-labelled elastic.io iPaaS. And we are particularly excited about the soon-to-come update of the platform’s dashboard, which will then provide better analytics on what is happening within the integration flows, allow for faster error debugging, give better logs, and so much more.
Stay tuned for more info!
In the meantime, why don’t you check out the integration flows versioning feature… and maybe add some flow descriptions for your colleagues 😉