202 - New Equilibrium

Last modified by Carlijn Kokkeler on 2024/04/18 13:13

release-blog-intro.png

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 smaller feedback items 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, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable 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. As a result, you don't have to type them twice when working on an integration.
  • 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 an entirely new release in Test and promote it to the Production environment.
Information

For more information, please check out the following microlearnings:

Should you have any questions in advance, please get in touch with us at productmanagement@emagiz.com.

 Manage - 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 managed graphs as we retrieve and show less fine-grained information when zooming out.

202-release-blog--manage-graphs-zoomed-out.png

Feedback Items

Improved editability when testing in eMagiz without Edit rights in Create
Without editing 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 should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.

Improved auditability on Deploy Architecture
To improve the audibility of 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 store content
We have now allowed testing of your 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.

Information

In case the concept of the store is new for you, please check out this Fundamental

Improved comparison of flows in the releases overview
We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.

Bug Fixes

Improved validation on XPath header enricher
To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.

Cancel behavior on flow testing property overview fixed
We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.

Cancel behavior on flow fragment level when exporting store content
We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.

Adding numbers on containers in Deploy Architecture
With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.

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 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!

Information

* Indicates a Beta feature. If you would like to get access to this beta feature, please contact productmanagement@emagiz.com

** Indicates a next-generation-architecture only feature.