Changes for page 213 - Joyful Journeys

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

From 59.1 to 60.1 From 133.1 to 134.1

From version 60.1

edited by Erik Bakker
on 2023/01/18 09:30

Change comment: There is no comment for this version

To version 133.1

edited by Erik Bakker
on 2023/08/01 14:11

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--190 - Fast Forward
++202 - New Equilibrium

Content

@@ -2,109 +2,70 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
++**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.
--== **Queue Browser** ==
++== **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:
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++* 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.
--To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
++{{info}}For more information please check out the following microlearnings:
--To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
++* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
++* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
++* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
++{{/info}}
--After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
++== ** 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.
--* Delete the message from the queue (Explore option)
--  ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
--* Clear message from the wiretap queue (Wiretap option)
--  ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
--* Refresh messages list (both options)
--  ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
--* Save as test message
--  ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
--* Download
--  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
++[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++== **Feedback Items** ==
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
++//__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.
--== **Message Redelivery ** ==
++//__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).
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
++//__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.
--Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
++{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
--Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
++//__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.
--On top of that we have added some additional functionality.
++//__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.
--* Search option
--  ** Original queue name
--  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
++== **Bug Fixes** ==
--== **3rd generation runtime bolstering** ==
++//__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.
--This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
++//__Improved validation feedback in migrating to the next-generation architecture__//
++We have improved the validation feedback when migrating to the next-generation architecture.
--//__SOAP and REST web services migration, including splitting them__//
--With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
++//__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.
--//__Changing SSL settings for 3rd generation runtime models works__//
--As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
++//__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.
--//__Improved migration for JMS flows__//
--This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
--
--{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
--
--//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
--As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
--
--//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
--We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
--
--//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
--With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
--
--//__Added "Reset" functionality__//
--With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
--
--== **Feedback items ** ==
--
--We have also solved other feedback items besides the flow designer's critical updates.
--
--//__Improved naming convention on Store related pages__//
--We have improved various display names using the merge functionality within our store offering.
--
--//__Update security protocols for our internal architecture__//
--Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
--
--//__Improved read-only description for "if exists" constructions in Transformations__//
--To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
--
--
--== **Bug fixes ** ==
--
--//__Decent validation feedback when not filling in the property value__//
--We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
--
--//__Incorrect resource locations__//
--We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
--
--//__Apply to environment in User Management performance improvement__//
--We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
--
  == **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:
--* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
--* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
--* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
--* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
++* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
++* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
++* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
  == **Key takeaways** ==

Changes for page 213 - Joyful Journeys

Summary

Details

Navigation