Changes for page 213 - Joyful Journeys

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

From 27.1 to 28.1 From 134.1 to 135.1

From version 28.1

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

Change comment: There is no comment for this version

To version 134.1

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

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

Content

@@ -2,135 +2,76 @@
  {{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 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.
--== **New monitoring stack** ==
++== **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:
--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.
++* 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.
--* [[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.HTTP Statistics.WebHome||target="blank"]]
++{{info}}For more information please check out the following microlearnings:
--{{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}}
++* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new||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"]]
--== **Transformation Improvements** ==
++Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
++{{/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.
++== ** 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.
--//__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@202-release-blog--manage-graphs-zoomed-out.png]]
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
++== **Feedback Items** ==
--== **Feedback items ** ==
++//__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.
--Apart from the key updates around functionality, we have also solved other feedback items.
++//__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).
--//__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.
++//__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.
--//__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.
++{{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}}
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
--
--//__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.
--
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
--
--//__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.
--
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
--
--//__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.
--
--//__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.
++//__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.
--//__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 validation feedback in migrating to the next-generation architecture__//
++We have improved the validation feedback when migrating to the next-generation architecture.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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"]]
++* [[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** ==
--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 213 - Joyful Journeys

Summary

Details

Navigation