Skip to Content

In mid-May, Cloud Integration was updated to version 2.40:

That’s not really news, in and of itself; Cloud Integration gets updated on a monthly basis. This steady flow of improvements and new features is one of the reasons why it’s such a cool product. This particular version, however, contains a lot of new stuff.

The Cloud Integration release notes page lists many of the changes, and some of them are detailed further in blogs written by the Cloud Integration team:

It stands to reason, that major new capabilities and shiny new features get the most coverage and the most attention. Today, though, I’m not here to talk about them. Instead, I’m going to focus on what I like to call quality of life updates. These updates do not substantially affect the way you work with the product, nor do they change what you can build with it. They do, however, introduce small, focused improvements, that add up to a better developer experience.

In this blog, I’m going to cover two quality of life updates, that I was really happy to see introduced in Cloud Integration version 2.40.

No more script file clutter

Up until version 2.40, script steps behaved in the following way: You added a script step to your integration flow, and a template script file would automatically be created for you, and added to your integration flow’s resources. This meant, that even if you wanted to use only a single script, containing multiple functions, your resources would be cluttered up with script1, script2, script3, … files, which you would have to clean up manually.

Not anymore! In version 2.40, adding a script step no longer automatically creates a script file. Instead, you are given the option of either creating a new script file or assigning an existing one to the script step:

The script step now behaves much more sanely, and this will go a long way towards reducing script file clutter.

HTTPS endpoints at long last

The second quality of life update, I’d like to mention, has to do with endpoints. An endpoint is a URL exposed by a sender channel in an integration flow. Through an endpoint, a message can be pushed to your integration flow, triggering the processing you’ve configured.

Endpoints are listed on the Endpoints tab in the Manage Integration Content area of the operations view. However, up until version 2.40, HTTPS sender channel endpoints were not shown, for reasons unknown.

Since version 2.40, HTTPS endpoints (and AS2 endpoints, by the way) are listed, as they should be:

Before this update, you could still piece together the endpoint URL by hand, but the added convenience is very nice.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply