175 - Building Time
Hi there, eMagiz developers! e have fixed several minor feedback items in the last couple of weeks. On top of that, we have finished our work on the latest build number. This build number includes some most desired fixes for our community. Some fixes surrounding flow testing and JSON-related transformations are notable among the feedback items. So let us dive into all that we have to offer this time around!
Build number 61
This release also introduces build number .61 to our platform. With this release, some specific problems have been resolved. First, it contains a fix for high throughput in multi-threaded cases when dealing with calls to the AWS API. On top of that, it includes a fix that allows you to dynamically determine how many seconds in advance you want to refresh your access_token when calling an external endpoint secured through the OAuth2.0 protocol. This enables you to prevent errors when the external system has precise requirements on calling the token endpoint. Furthermore, it provides two other minor fixes. Please check out the release notes in the portal for all details to determine the impact on your solution.
Bug fixes
See below for all bug fixes that are solved with this release
Running a flow test on a flow with the 'old' debugger
Previously, when you tried to run a flow test in which a reference to an H2 database was available (i.e., the ‘old’ debugger construction), your flow test would run into an exception. We have made sure that these flows can now also be tested as part of the flow testing functionality with this release.
Running a flow test should be possible when referencing a resource
Previously, it was impossible to execute a proper flow test on a flow where you defined your reference to a resource (i.e., when referencing a groovy script). We have made sure that you can test these flows as part of the flow testing functionality with this release.
Feedback items
Apart from the key updates around functionality, we have also solved other feedback items.
Validate JSON String Array
With this release, we have made it possible to define on your system message in Create whether a particular part of the message needs to be validated as a String array. Note the help text when implementing this within eMagiz.
List output JSON
Previously, when you drew two lines to the same output list eMagiz would create two separate JSON arrays. With this release we have ensured that for each output list only one JSON array is created to prevent unexpected JSON output
Removal of unnecessary pages in Manage
With this release, we have removed several unnecessary pages in the Manage phase of eMagiz. The obsolete pages of Channel, Handler, and Cloud Statistics have been removed.
Fancy Forum Answers
As always, a gentle reminder to all to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
- OverlappingFileLockException
- Problem with synchronous exit connector without import mapping
- XML Message with content: “É” changes in ” “
- New Line in FTP File Placement
Key takeaways
Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
- If you have questions surrounding our Program Increment Planning, please get in touch with
- If you have feedback or ideas for us, talk to the Platypus
- Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
- Clear your browser cache (Ctrl + Shift + Del)
- Check out the release notes here
- Start thinking about how the license tracker can aid your development
- Start thinking about major, minor, and patch
- Upgrade to the latest build number
- Keep making great integrations
Let's stay in touch and till next time!