Changes for page 208 - Controlled State

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

From 26.1 to 27.1 From 75.1 to 76.1

From version 27.1

edited by Erik Bakker
on 2022/10/24 09:02

Change comment: There is no comment for this version

To version 75.1

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

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 @@
--186 - Daemon Switch
++191 - Fifty Fifty

Content

@@ -2,135 +2,108 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** We have hit the ground running in this quarter by not only focusing on larger features but also spend a substantial chunk of time on focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to a first set of models. So let us dive into all we have to offer this time!
++**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.
--== **New monitoring stack** ==
++== **Dynamic Alerts** ~*~* ==
--This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of what these changes entail please check out the following microlearnings.
++{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
--* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
--* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
--* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]]
--* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-apigateway-http-statistics.WebHome||target="blank"]]
++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.
--{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter please contact us at productmanagement@emagiz.com to discuss the possibilities{{/info}}
++We offer alerting on five types.
--== **Transformation Improvements** ==
++* Error message
++* Log message
++* Queue consumers
++* Messages in queue
++* Queue throughput
--//__Toggle between Design and Create__//
--This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
--//__Improved Transformation options for booleans__//
--On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks.
++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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
--== **Feedback items ** ==
++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.
--Apart from the key updates around functionality, we have also solved other feedback items.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
--//__Correctly define the size of a cloud slot when creating it for the first time__//
--Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted.
++== **Debugger ** ~*~* ~* ==
--//__Updated infographic Capture__//
--As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
++{{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}}
--//__Updated error feedback in Design__//
--Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown.
++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 styling of Topic Storage in Design Architecture__//
--When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
--//__Improved styling of error feedback on User Management in Deploy__//
--With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
--//__Show only the ten latest flow versions when selecting a flow version in a Release__//
--To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
++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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
--//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__//
--Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification.
++{{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}}
--//__Clear API Gateway System message__//
--With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level.
++== **Volume mapping - Network Share** ==
--//__Additional information in Property History__//
--To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes.
++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.
--//__Save Tag when ready__//
--With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
--//__View deployment step information when having view rights__//
--With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
--//__Validating external recipients in notification settings__//
--Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values.
++== **Feedback items ** ==
--//__Automatically link enumeration list to attribute__//
--When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Approve and go to environment__//
--With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment.
++//__Improved validation feedback on non-supported WSS4J interceptor __//
++We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
++//__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.
--//__Remove irrelevant information on a runtime in Design Architecture__//
--We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
++== **Bug fixes ** ==
--//__Add question about message redelivery in Capture__//
--When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution.
++//__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.
--//__Prevent pressing “Apply to environment” multiple times leading to conflicts__//
--With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period.
++//__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.
--//__Add “State” to the topic details in Deploy Architecture__//
--Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched.
++//__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.
--//__Improved stability of logging on the Gen3 Architecture__//
--With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally.
++//__Fix editability of properties when importing store items__//
++With this release, you can once again change property names upon importing a store item.
--== **Bug Fixes** ==
--
--//__Various updates when importing store items in Design including a transformation__//
--With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
--
--//__Opening flow testing widget in specific circumstances was not working__//
--With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.”
--
--//__Improved styling when adding a large message to a flow test__//
--With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message.
--
--//__Errors on the UI do not keep following me__//
--Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete.
--
--//__Navigating back to the transformation in Create works again__//
--With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see.
--
--//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__//
--With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz.
--
--//__Selecting tags when drawing a line in Capture__//
--We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture.
--
--//__Remove invalid selection when configuring a cron trigger via the tooling__//
--With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution.
--
  == **Fancy Forum Answers** ==
--As always, a gentle reminder to all 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:
++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:
--* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
--* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
--* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
++* [[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"]]
  == **Key takeaways** ==
--Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
++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
++* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@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>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
@@ -143,7 +143,7 @@
  Let's stay in touch and till next time!
  {{info}}
--~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
++~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  ~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}

Changes for page 208 - Controlled State

Summary

Details

Navigation