Changes for page 208 - Controlled State

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

From 23.1 to 22.1 From 74.1 to 73.1

From version 73.1

edited by Erik Bakker
on 2023/01/31 12:16

Change comment: There is no comment for this version

To version 23.1

edited by Erik Bakker
on 2022/10/24 08:59

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

Content

@@ -2,129 +2,135 @@
  {{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!** 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!
--== **Dynamic Alerts** ~*~* ==
++== **New monitoring stack** ==
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++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.
--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.
++* [[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-alerting-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 API Gateway.advanced-monitoring-apigateway-http-statistics.WebHome||target="blank"]]
--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.
++{{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}}
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++== **Transformation Improvements** ==
--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.
++//__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.
--* 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.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
++== **Feedback items ** ==
--{{info}}The following restrictions apply to this functionality:
--  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
--  * The wiretap 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 wiretap functionality will be shutdown automatically under water.
--    ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
++Apart from the key updates around functionality, we have also solved other feedback items.
--== **Debugger ** ~*~* ~* ==
++//__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.
--{{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}}
++//__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.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
++//__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 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 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.
--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 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.
--On top of that, we have added some additional functionality.
++//__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.
--* 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.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.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.
--== **3rd generation runtime bolstering** ==
++//__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.
--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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--{{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}}
++//__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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
--//__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"]]
++//__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.
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
--== **Feedback items ** ==
++//__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.
--We have also solved other feedback items besides the flow designer's critical updates.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
++== **Bug Fixes** ==
--== **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.
--//__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.
++//__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.”
--//__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.
++//__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.
--//__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.
++//__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.
--//__Fix editability of properties when importing store items__//
--With this release, you can once again change property names upon importing a store item.
++//__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, 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:
++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:
--* [[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"]]
++* [[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"]]
  == **Key takeaways** ==
--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:
++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:
--* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
++* If you have questions surrounding our Program Increment Planning, please get in touch with
  * 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)
@@ -137,7 +137,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