Changes for page 204 - Found It

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

From 75.1 to 76.1 From 131.1 to 132.1

From version 76.1

edited by Erik Bakker
on 2023/01/31 13:02

Change comment: There is no comment for this version

To version 131.1

edited by Erik Bakker
on 2023/08/01 13:48

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 @@
--191 - Fifty Fifty
++202 - New Equilibrium

Content

@@ -2,102 +2,68 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. 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.
--== **Dynamic Alerts** ~*~* ==
++== **Release Properties** ==
++As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
--{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
++{{info}}For more information please check out the following microlearnings:
--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 "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.
++*
++*
++*
--We offer alerting on five types.
++Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
++{{/info}}
--* Error message
--* Log message
--* Queue consumers
--* Messages in queue
--* Queue throughput
++== ** Deploy Architecture - Apply To Environment improvements ** ==
++As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
++[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
--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.
++== ** Breadcrumb navigation in eMagiz ** ==
++This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
++[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
--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.
++== **Feedback Items** ==
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
++//__Improved layout of catalog page in Design__//
++We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
--== **Debugger ** ~*~* ~* ==
++//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
++Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
--{{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
--* The beta image is activated
--* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
++//__Additional help texts on Design Architecture__//
++We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
--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.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
++//__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.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
++== **Bug Fixes** ==
--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.
++//__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-output-queue-browser.png]]
++//__Improved validation feedback in migrating to the next-generation architecture__//
++We have improved the validation feedback when migrating to the next-generation architecture.
--{{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}}
++//__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.
--== **Volume mapping - Network Share** ==
++//__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.
--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.
--
--//__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.
--
--== **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.
--
--//__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