Changes for page 204 - Found It

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

From 70.1 to 71.1 From 133.1 to 134.1

From version 71.1

edited by Erik Bakker
on 2023/01/18 11:11

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,117 +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 and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including 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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
++{{info}}For more information please check out the following microlearnings:
--To do so, we offer two options within this functionality. First, 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 the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press 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 inadvertently put many messages on a queue.
--* Clear message from the wiretap queue (Wiretap option)
--  ** Once you are done with the analysis of a specific 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 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 your 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.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
++{{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}}
--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 under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
++//__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.
--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.
++//__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.
--On top of that, we have added some additional functionality.
++== **Bug Fixes** ==
--* Search option
--  ** Original queue name
--  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
--* Save as test message
--  ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
--* Download
--  ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
++//__Improved validation feedback in migrating to the next-generation architecture__//
++We have improved the validation feedback when migrating to the next-generation architecture.
--== **3rd generation runtime bolstering** ==
++//__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.
--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.
++//__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.
--//__Define memory settings for on-premise runtimes from Deploy Architecture__//
--With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
--
--//__Empty runtime feedback when deploying a release (or setting the release as active)__//
--To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
--
--//__Auto-fill namespaces for SOAP hosted webservices__//
--Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
--
--//__Updated H2 database setting__//
--As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
--
--{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
--
--//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
--As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
--
--//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
--With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
--
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
--
--== **Feedback items ** ==
--
--We have also solved other feedback items besides the flow designer's critical updates.
--
--//__Sensitive information stored in properties is masked __//
--We have made how we display sensitive information across the portal similar for various parts of the portal.
--
--//__Importing "Private" store content to which you do not have access__//
--We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
--
--
--== **Bug fixes ** ==
--
--//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
--We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
--
--//__Synchronization of Event Streaming topic states__//
--We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
--
--//__Copy and paste default support objects__//
--With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
--
--//__Fix editability of properties when importing store items__//
--With this release, you can once again change property names upon importing a store item.
--
  == **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:
--* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
--* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
--* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
--* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||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 204 - Found It

Summary

Details

Navigation