Changes for page 207 - Aligned State

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

From 28.1 to 29.1 From 102.1 to 103.1

From version 29.1

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

Change comment: There is no comment for this version

To version 102.1

edited by Erik Bakker
on 2023/04/13 09:23

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
++195 - Easter Party

Content

@@ -2,135 +2,101 @@
  {{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 few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
--== **New monitoring stack** ==
++== **Release properties** ==**
--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.
++With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
--* [[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.HTTP Statistics.WebHome||target="blank"]]
++As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
--{{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}}
++{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
--== **Transformation Improvements** ==
++{{info}}The following considerations need to be taken into account when using this functionality:
++* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
++* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
++* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
++*{{/info}}
--//__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.
++== **API improvements** ==
--//__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.
++//__Improved auto-generated error handling__//
++When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
++//__Switch default message format__//
++We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
--== **Feedback items ** ==
++//__Re-using elements in gateway message__//
++This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
--Apart from the key updates around functionality, we have also solved other feedback items.
++//__Improved naming of API operations when adding integrations to Create__//
++Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
--//__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.
++== **3rd generation improvements** ==
--//__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.
++//__Update of the static alerting engine__//
++In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
--//__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.
++//__Add "Data pipeline" functionality__//
++This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
--//__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.
++//__Fix related to the debugger__//
++This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
--//__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.
++{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
--//__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.
++//__Improved migration process__//
++This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
++//__Deployment plan change__//
++In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
--//__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.
++{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
--//__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.
++== **Feedback items ** ==
--//__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.
++//__License Tracker improvements__//
++With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
--//__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.
++//__Ability to view the message definition for a topic__//
++Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
--//__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.
++//__Restricted access for uploading custom certificates to endpoints__//
++To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
--//__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.
++== **Bug fixes ** ==
--//__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.
++//__Improved deletion behavior for enumerations__//
++To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
--//__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.
++//__Prevent "async" api operations__//
++With this release, we have removed the ability to select the "async" option when the default message format is API Management.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
++//__Importing a response definition broke the request definition__//
++Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
--//__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.
++//__Removing a flow does not update the API "all-entry" anymore__//
++When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
++//__Stop deployment plan when a property is missing__//
++Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
--//__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.
++//__Cap stack trace of error messages and log entries__//
++To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
--//__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.
--
--//__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.
--
--//__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** ==
--
--//__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"]]
++* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
++* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
++* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||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 207 - Aligned State

Summary

Details

Navigation