Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 27.1
edited by Erik Bakker
on 2022/10/24 09:02
on 2022/10/24 09:02
Change comment:
There is no comment for this version
To version 126.1
edited by Erik Bakker
on 2023/06/19 14:24
on 2023/06/19 14:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 186-DaemonSwitch1 +200 - Uncharted Territories - Content
-
... ... @@ -2,135 +2,58 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavehittheground runninginthis quarterby not onlyfocusingon largerfeaturesbut also spend a substantialchunkoftimeon focusing withusallon a lotfsmallerfeedback itemsandbugs. All theseitemswillbeprovidedtoyouwiththis release.Amongtheseareflowdesignerimprovements, navigationimprovements,and consistency improvements.On top of that, wehavemadeournewmonitoring stack available toafirstsetofmodels.Solet us diveinto all wehaveto offer thistime!5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier. 6 6 7 -== **Ne wmonitoring stack** ==7 +== **Next generation improvements and bug fixes** == 8 8 9 -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. 9 +//__Enhanced right-hand view within Deployment Plan context__// 10 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 10 10 11 -* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 12 -* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 13 -* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]] 14 -* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-apigateway-http-statistics.WebHome||target="blank"]] 12 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 15 15 16 -{{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}} 14 +//__Improved timeout settings when deploying__// 15 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur. 17 17 18 - ==**Transformation Improvements**==17 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 19 19 20 -//__ TogglebetweenDesignandCreate__//21 -T hisrelease will introduce a togglethatallows youto quickly navigatebetween the Create TransformationandtheDesignMessageMapping.In bothCreateas Design,a new buttonisaddedonthetransformationlevelthatallows youtoopenthetransformationin Design(or Create)depending on where you arecurrently.This shouldmakevigatingeasierwhenyou makemistakeorforgetsomethingin Design.19 +//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 22 22 23 -//__Improved Transformation options for booleans__// 24 -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. 22 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 24 +//__Improved loading speed of Manage Dashboard__// 25 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 27 27 28 -== ** Feedbackitems27 +== **Store Improvements** == 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 29 +//__Importing in Design is improved__// 30 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 31 31 32 -//__Correctly define the size of a cloud slot when creating it for the first time__// 33 -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. 34 - 35 -//__Updated infographic Capture__// 36 -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. 37 - 38 -//__Updated error feedback in Design__// 39 -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. 40 - 41 -//__Improved styling of Topic Storage in Design Architecture__// 42 -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. 43 - 44 -//__Improved styling of error feedback on User Management in Deploy__// 45 -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. 46 - 47 -//__Show only the ten latest flow versions when selecting a flow version in a Release__// 48 -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. 49 - 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 51 - 52 -//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__// 53 -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. 54 - 55 -//__Clear API Gateway System message__// 56 -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. 57 - 58 -//__Additional information in Property History__// 59 -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. 60 - 61 -//__Save Tag when ready__// 62 -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. 63 - 64 -//__View deployment step information when having view rights__// 65 -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. 66 - 67 -//__Validating external recipients in notification settings__// 68 -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. 69 - 70 -//__Automatically link enumeration list to attribute__// 71 -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. 72 - 73 -//__Approve and go to environment__// 74 -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. 75 - 76 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]] 77 - 78 -//__Remove irrelevant information on a runtime in Design Architecture__// 79 -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. 80 - 81 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]] 82 - 83 -//__Add question about message redelivery in Capture__// 84 -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. 85 - 86 -//__Prevent pressing “Apply to environment” multiple times leading to conflicts__// 87 -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. 88 - 89 -//__Add “State” to the topic details in Deploy Architecture__// 90 -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. 91 - 92 -//__Improved stability of logging on the Gen3 Architecture__// 93 -With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally. 94 - 95 95 == **Bug Fixes** == 96 96 97 -//__ Various updateswhen importing storeitemsinDesignincludinga transformation__//98 -W iththis release,wehavemadeseveralimprovementsforimportingstoreitems inDesign,includingatransformation.Thiswill furtherbolsterour offering onthis.34 +//__Deprecated reminder pop-up removed__// 35 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems. 99 99 100 -//__ Opening flow testing widgetinspecificcircumstances wasnotworking__//101 -W iththis release,we fixedanissuewhereyoucouldnotopenthe flowtestingfunctionalityin the Createphasewhenyourflowcontainedaparticularconstructioncombinedwiththe“nullChannel.”37 +//__Improved selection area in Flow Designer__// 38 +When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow. 102 102 103 -//__Improved styling whenaddingalarge messageo a flowtest__//104 - Withthisrelease,thestylingof thepop-upwill notchangewhenyoudefinealargemessageasinput(orexpectedoutput) of yourflow test. This willensurethat youcan stilleasilyspecifytheflowtestmessage’s name anddescriptionafterentering thelargemessage.40 +//__Improved Kafka settings__// 41 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 105 105 106 -//__Errors on the UI do not keep following me__// 107 -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. 43 +{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 108 108 109 -//__Navigating back to the transformation in Create works again__// 110 -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. 111 - 112 -//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__// 113 -With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz. 114 - 115 -//__Selecting tags when drawing a line in Capture__// 116 -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. 117 - 118 -//__Remove invalid selection when configuring a cron trigger via the tooling__// 119 -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. 120 - 121 121 == **Fancy Forum Answers** == 122 122 123 -As always, a gentle reminder to a ll 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:47 +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: 124 124 125 -* [[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"]] 126 -* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]] 127 -* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]] 49 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 128 128 129 129 == **Key takeaways** == 130 130 131 -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:54 +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: 132 132 133 -* If you have questions surrounding our Program Increment Planning, please get in touch with 56 +* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 134 134 * If you have feedback or ideas for us, talk to the Platypus 135 135 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 136 136 * Clear your browser cache (Ctrl + Shift + Del) ... ... @@ -143,7 +143,7 @@ 143 143 Let's stay in touch and till next time! 144 144 145 145 {{info}} 146 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 148 148 ~*~* Indicates a GEN3-only feature. 149 149 {{/info}})))((({{toc/}}))){{/container}}