Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 29.1
edited by Erik Bakker
on 2022/10/24 09:03
on 2022/10/24 09:03
Change comment:
There is no comment for this version
To version 255.1
edited by Carlijn Kokkeler
on 2023/11/21 12:05
on 2023/11/21 12:05
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 186-DaemonSwitch1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,138 +1,83 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have hit the groundrunning in this quarter by not only focusing on largerfeatures 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!6 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 -== **New monitoring stack** == 8 +{{warning}} 9 +Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. 10 +{{/warning}} 8 8 9 - Thisrelease will introduce a new monitoring stackthat is availableformodels that run in the new runtime architectureof eMagiz. With the help of thismonitoring stack wehave redesigned various screens in Manage and restructuredour alertingapproach. For a sneakpreview of what these changes entail please check out the following microlearnings.12 +== **Quicker Deployment Plan** == 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-alerting-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.HTTP Statistics.WebHome||target="blank"]] 14 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now! 15 15 16 - {{info}}Notehatthew monitoring stackisonlyavailable formodels that run the new runtime architecture.Should you wish to becomean early adopter please contactus at productmanagement@emagiz.com to discuss the possibilities{{/info}}16 +== **Next Generation Architecture Default** == 17 17 18 - ==**TransformationImprovements**==18 +With this release, the next generation architecture will become the default. New models will use this generation as default. 19 19 20 -//__Toggle between Design and Create__// 21 -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. 20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]] 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 +== **Cloud Template R11 Docker - Single Lane** == 25 25 26 - [[image:Main.Images.ReleaseBlog.WebHome@179-release-blog--transformation-options-boolean.png]]24 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]]. 27 27 28 -== ** Feedbackitems** ==26 +== **Cloud Template R13 Docker - Double Lane** == 29 29 30 - Apartfromthekeyupdatesaroundfunctionality,we have also solvedotherfeedbackitems.28 +This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 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. 30 +== **Feedback Items** == 34 34 35 -//__U pdatedinfographicCapture__//36 - Asofnow,wehave updatedthe infographicon the Capture phase toincorporate thenewlookandfeel andexplain the updatedfunctionalityinCapture.32 +//__Unused properties overview__// 33 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 37 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. 35 +* Not used by any runtime that is in the Create phase release. 36 +* Not required by a flow that is in the Create phase release. 37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 40 40 41 -//__ Improvedstylingof Topic Storagein DesignArchitecture__//42 - Whenhavinga largenumberoftopicsinyourenvironment,thetopic storage overviewin DesignArchitecturewill now beimproved asthehorizontalscrollbaris gone.39 +//__Send build requests asynchronously__// 40 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 43 43 44 -//__ Improvedstylingof error feedback on UserManagementin Deploy__//45 - Withthis releasewehaveimprovedthe stylingofthe feedbackpop-upyou get in Usermanagement after pressing “Apply to environment” andseveral updatescould notbeexecuted.42 +//__Queue explorer milliseconds__// 43 +The queue browser now displays milliseconds in the timestamps. 46 46 47 -//__ Show onlythe tenlatestflow versionswhen selecting a flow version in a Release__//48 -T oimprove thequalityandspeedofdefining arelease,wewill show onlythelatestten versionsofaflowinthereleasewidget,as thesetenaremostlikelytobeselectedbya user.Ifyouneedanolderversion, you can add itvia the“Details” optionon the release.45 +//__Cancel and next buttons order__// 46 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 48 +//__Unused images__// 49 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 51 51 52 -//__ OptionalClient Secretwhen using the grant_type Password whencallingan OAuth2.0 IDP__//53 - Before,youneededtodefinetheClientSecretevenfor the grant_typePassword,where itis notalways required.Wehave correctedthisbehaviorensurethat this is inlinewith theOAuth 2.0 specification.51 +//__Carwash logging__// 52 +A new logging feature enabling us to make better choices in encryption standards will be released. 54 54 55 -//__ ClearAPI GatewaySystemmessage__//56 - With this release, we have added the Clearbuttonthat you alreadyknowfromthe messaging patternto theAPI Gateway system message.Thisunifies the optionsbetweenthetwo patternsinDesignonthesystem messagelevel.54 +//__Static alerts queue consumers__// 55 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 57 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 updateswhenimporting store items inDesignincluding a transformation__//98 - Withthis release,we havemadeseveralimprovementsforimportingstoreitemsinDesign,includinga transformation.Thiswillfurtherbolster our offering on this.59 +//__Flow Designer connection line__// 60 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 99 99 100 -//__ Openingflowtestingwidgetin specificcircumstanceswas not working__//101 -W ith this release,wefixed anissue whereyou could notopentheflowtestingfunctionalityinheCreatephasewhenyour flowcontained aparticularconstructioncombinedwiththe“nullChannel.”62 +//__Portal for migrated models__// 63 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 102 102 103 -//__ Improvedstyling whenadding a largemessage to a flowtest__//104 -W iththisrelease,the stylingofthepop-upwillnotchangewhenyouefinea large messageasinput(orexpectedoutput)ofyourflow test.This willensure thatyoucanstilleasilyspecifytheflowtestmessage’sname anddescription afterenteringthelarge message.65 +//__Error channel inbounds__// 66 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 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. 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:70 +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"]] 72 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 128 128 129 129 == **Key takeaways** == 130 130 131 -Thanks to all thathelp build,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:76 +Thanks to all who 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 78 +* 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 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 +* 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) 137 137 * Check out the release notes [here] 138 138 * Start thinking about how the license tracker can aid your development ... ... @@ -143,8 +143,14 @@ 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]] 91 +~* 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 -~*~* Indicates a GEN3-only feature. 149 -{{/info}})))((({{toc/}}))){{/container}} 93 +~*~* Indicates a next-generation-architecture only feature. 94 +{{/info}} 95 +))) 96 + 97 +((( 98 +{{toc/}} 99 +))) 150 150 {{/container}} 101 +{{/container}}