Changes for page 207 - Aligned State

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

From 80.1 to 81.1 From 136.1 to 137.1

From version 81.1

edited by Erik Bakker
on 2023/02/13 14:00

Change comment: There is no comment for this version

To version 136.1

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

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 @@
--192 - Small Step
++202 - New Equilibrium

Content

@@ -2,144 +2,70 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger 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.
--== **Start/Stop Flows** ~*~* ==
++== **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 depending on the alert this functionality will only work 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 options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
++{{info}}For more information please check out the following microlearnings:
--[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
++* [[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"]]
--
--{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
--
--
--  observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
++Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
++{{/info}}
--We offer alerting on five types.
++== ** 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.
--* Error message
--* Log message
--* Queue consumers
--* Messages in queue
--* Queue throughput
++[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
++== **Feedback Items** ==
--These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
++//__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).
--Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
++//__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@191-release-blog--dynamic-alert-trigger-output.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}}
--== **Debugger ** ~*~* ~* ==
++//__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.
--{{warning}}Note that this functionality only works when the following criteria are met.
--* Your JMS server is running on the 3rd generation runtime
--* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
--* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
++//__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.
--As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
++== **Bug Fixes** ==
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
++//__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@191-release-blog--debugger-action-failure.png]]
++//__Improved validation feedback in migrating to the next-generation architecture__//
++We have improved the validation feedback when migrating to the next-generation architecture.
--Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
++//__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.
--{{info}}Note the following limitations when working with the debugger.
--  * Your entire model needs to be migrated to the 3rd generation runtime
--  * Only **one** flow **per** runtime can be debugged **per** environment
--  * There is only **one** overview in which **all** debugged messages are shown
--  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
--  * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
--    ** After five minutes the debug functionality will be shutdown automatically under water.
--    ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
--
--== **Volume mapping - Network Share** ==
--
--This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
--
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
--
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
--
--== **Feedback items ** ==
--
--We have also solved other feedback items besides the flow designer's critical updates.
--
--//__Show status on machine level under Deploy Architecture__//
--With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
--
--//__Improved validation feedback on non-supported WSS4J interceptor __//
--We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
--
--//__Improve help text in flow testing on Java classes__//
--We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
--
--//__Improved readibility of notification when trying to delete a runtime__//
--When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
--
--//__Improved sorting of missing properties overview__//
--We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
--
--//__Improved notification when error message cannot be found__//
--We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
--
--//__Additional lifecycle management overview__//
--We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
--
--//__Improved feedback when memory settings are negative__//
--We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
--
--//__Auto upgrade for a cloud template default to "ON"__//
--For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
--
--//__Removed an irrelevant refresh button on a flow designer component__//
--We have removed an irrelevant refresh button on the standard filter component.
--
--//__Notification list shows all notifications on default__//
--When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
--
--== **Bug fixes ** ==
--
--//__Keep selection when copying properties__//
--We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
--
--//__Check on security header improved for API Gateway__//
--We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
--
--//__Don't show systems with only "external" flows in Design__//
--We fixed a bug that caused systems to appear in Design in cases where there should be none.
--
--//__Fix styling of mendix login in some occurences__//
--When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
--
--//__Change timing of wake-up of cloud slots on Friday__//
--To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
--
--//__Fixed a typo in the Topic statistics overview__//
--We fixed a typo in the topic statistics overview.
--
--//__Fixed a typo in the HTTP statistics overview__//
--We fixed a typo in the HTTP statistics overview.
--
--//__Activatation of release history when executing a deployment__//
--We ensured that the release history is activated when executing a deployment.
--
  == **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:
--* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
--* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
--* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||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 207 - Aligned State

Summary

Details

Navigation