194 - Big Leap
Hi there, eMagiz developers! In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
3rd generation improvements
Better feedback in error log when a corrupt stylesheet is encountered
We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
Better internal error handling to avoid unnecessary alerting and notifications
We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
Improved Manage Dashboard
This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes
When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
Improved process of deploy preparation
With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
Improved migration of Streaming container
When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
Add History to Notifications in Manage
To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
Improved Manage phase for Event Streaming
Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
Improved help text for network volumes
With this release we have improved the help text that explains network volumes and how to use them within our solution.
WS-Security on the 3rd generation runtime **
To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
State Generation **
With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
Feedback items
Removed OData as option for an API Gateway operation
With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
Changes in API Gateway operation paths is automatically updated in Create
When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
Bug fixes
Prevent endless loop in Deploy -> User Management
With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
Update error handling during migration to the 3rd generation runtime
As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
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:
- Access Spring ApplicationContext within Groovy Script
- Configuration problem: Failed to locate '$autoCreateChannelCandidates'
- 503 on SOAP Webservice hosted in eMagiz
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!