202 - New Equilibrium

Hi there, eMagiz developers! In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.

Release Properties

As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:

• The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
• Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
• When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
• A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.

 Manage - Next generation graphs improvements 

As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.

Feedback Items

Improved editability when testing in eMagiz wihout Edit rights in Create
Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.

Improved auditability on Deploy Architecture
To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).

Test your own exported work
We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.

Improved Audit Trail on several places
In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.

Removed the erroneous alert on message mapping when having a passthrough API
This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.

Bug Fixes

Avoid clicking on other components while deleting another
To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.

Improved validation feedback in migrating to the next-generation architecture
We have improved the validation feedback when migrating to the next-generation architecture.

Make sure that user credentials can be viewed with view rights
This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.

Refresh behavior within the deployment plan is fixed
This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.

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:

• Replacing Legacy eMagiz-Mendix Connector: Migration Plan
• Unknown character(s) does not create error message.
• Split gateway configuration for local GEN3 gateway

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!