173 - Time Saver

Hi there, eMagiz developers! In the last couple of weeks, we have worked on various main platform features. Sadly they are not yet ready enough to release to you guys. We did, however, improve the platform in different more minor ways. Among these improvements, we have improved the speed of handling error messages and creating models by hand. Furthermore, we have several more minor improvements and bug fixes for you. So let us dive into all that we have to offer this time around!

Save and Add Attributes

When adding multiple attributes by hand to a data model, you need to access the context menu, select the option Add attribute, add the attribute, Save the attribute and repeat that process for every single attribute. We have now introduced a new option when adding attributes to your data models and system messages to speed up this process. This way, you can save and add another attribute by pressing the “Save and add new” button. This way, you don't have to navigate via the context menu for every attribute you want to save.

Other Feedback items 

Apart from the hide/show tasks functionality, we have also solved other feedback items.

Make Flow Testing available for the new generation runtime
As of this release, the flow testing functionality is also made available for all processes that already run the new generation runtime (GEN3).

Bug Fixes

Being able to delete data model entities that are in use

Previously, it was possible to delete an entity on the data model level that was still in use in a transformation. This could lead to catastrophic problems when someone unintentionally deleted an essential entity for many transformations. As of this release, we have implemented a check that prevents you from deleting any entity still in use in a message or transformation.

Reserved property names

As of this release, we have defined various forbidden names for properties. One example is creating any property that starts with emagiz. This way, we prevent problems when starting up your solution.

When importing Store items the associated resource is not always provided to the user

Previously, you could import items from the store without receiving the associated resource rendering the import useless. With this release, we made sure that you also get the resource with it when importing the store item.

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:

• Is it possible to split a JSON message into multiple smaller messages and how is this possible?
• URI is not absolute
• JSON array is null

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!