191 - Fifty Fifty
Hi there, eMagiz developers! In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
Dynamic Alerts **
To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
We offer alerting on five types.
- Error message
- Log message
- Queue consumers
- Messages in queue
- Queue throughput
These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
Debugger ** *
As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for one specific flow per runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
Volume mapping - Network Share
This release will introduce an additional functionality within our volume mapping offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
Feedback items
We have also solved other feedback items besides the flow designer's critical updates.
Improved validation feedback on non-supported WSS4J interceptor
We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
Improve help text in flow testing on Java classes
We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
Improved readibility of notification when trying to delete a runtime
When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
Bug fixes
Keep selection when copying properties
We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
Check on security header improved for API Gateway
We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
Copy and paste default support objects
With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
Fix editability of properties when importing store items
With this release, you can once again change property names upon importing a store item.
Fancy Forum Answers
As always, this is a gentle reminder 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:
- Can I change my 2FA secret, eg. move to another authenticator?
- Webrequest header 'SOAPAction'
- XPathException on XPATH router
- Change property with new release in generation 3 runtimes
Key takeaways
Thanks to all that helped build and 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 productmanagement@emagiz.com
- 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!