221 - Swift Shift
Hi there, eMagiz developers! This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.
Feedback Items
Q&A search
Search results are now persisted when pressing the back button after opening a question in the community Q & A.
Event catalog
For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
Attribute placements
Some improvements regarding the placement of attributes have been done:
- A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
- Moving an attribute in the datamodel is now directly shown in the tree structure as well.
- The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
Failover & grouping
Some improvements regarding the widgets for failover and grouping have been done:
- When executing a start/stop action on a group, the description of the step now contains the name of the group.
- When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
Bug Fixes
XSD import
When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
Container deletion
The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
Scope properties
We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
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:
Key Takeaways
Thanks to all who 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
- Keep making great integrations
Let's stay in touch and till next time!