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 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
on 2023/11/21 11:09
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
-
... ... @@ -2,137 +2,76 @@ 2 2 {{container layoutStyle="columns"}}((( 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!5 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 -== **New monitoring stack** == 7 +== **Next Generation Architecture Default** == 8 +With this release, the next generation architecture will become the default. New models will use this generation as default. 8 8 9 - This releasewill introduceanew monitoringtack that is availablefor models that run in thenew runtimearchitectureof eMagiz.ith thehelpof thismonitoring stack wehaveredesigned variousscreens in Manage and restructured our alerting approach. For a sneak preview of whatthese changes entail please check out the followingmicrolearnings.10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 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"]] 12 +== **Cloud Template R11 - Single Lane** == 13 +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 15 15 16 - {{info}}Notethat the new monitoring stack is only available for modelsthat run thenew runtimearchitecture.Shouldyouwish toecome an early adopterplease contact us at productmanagement@emagiz.comto discuss the possibilities{{/info}}15 +== **Cloud Template R13 - Double Lane** == 17 17 18 -== **Transformation Improvements** == 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. 18 +== **Feedback Items** == 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. 20 +//__Unused properties overview__// 21 +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: 22 +* Not used by any runtime that is in the Create phase release. 23 +* Not required by a flow that is in the Create phase release. 24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 26 +//__Send build requests asynchronously__// 27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 27 27 28 -== **Feedback items ** == 29 +//__Queue explorer milliseconds__// 30 +The queue browser now displays milliseconds in the timestamps. 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 32 +//__Cancel and next buttons order__// 33 +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. 31 31 32 -//__ Correctly define thesizeof a cloudslot when creatingit for thefirst time__//33 - Currently,eMagizwill look to Design whencreating the cloudslotforthefirst time. This is toavoidyouhavingto “create”your solutiontwice,as therewerenstanceswhere eMagiz would alwayscreate thecloudslotwith the smallestsize availablefirst,evenif this were not what you wanted.35 +//__Unused images__// 36 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 34 34 35 -//__ Updated infographicCapture__//36 -A sofnow,we have updated the infographic ontheCapturephasetoincorporate thenew look and feelandexplain the updatedfunctionalityinCapture.38 +//__Carwash logging__// 39 +A new logging feature enabling us to make better choices in encryption standards will be released. 37 37 38 -//__ UpdatederrorfeedbackinDesign__//39 - Before, you could see a transformationerrorinDesigneventhough thetransformationwas notusedin yoursolution (i.e., “data pipeline”functionality).However, whenyou now defineaspecific integration asaatapipelinesolution, the error willnotbeshown.41 +//__Static alerts queue consumers__// 42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 40 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 storetems in Design including a transformation__//98 -W iththis release,wehavemadeseveralimprovementsforimportingstoreitemsinDesign,includingatransformation.Thiswillfurtherbolsterourofferingon this.46 +//__Images rebuild__// 47 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped. 99 99 100 -//__ Opening flowtestingwidget inspecificcircumstances wasnotworking__//101 - Withthis release,wefixedan issuewhereyou couldnot opentheflow testing functionality intheCreatephasewhenyourflow containeda particular constructioncombinedwiththe“nullChannel.”49 +//__Flow Designer connection line__// 50 +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. 102 102 103 -//__ Improved stylingwhenaddinga large messagetoa flow test__//104 -W iththisrelease,thestylingofthepop-up willnotchangewhen youdefine alargemessageasinput(orexpectedoutput)ofyourflowtest. This willensurethatyou canstilleasily specifytheflowtestmessage’snameand description afterenteringthelargemessage.52 +//__Portal for migrated models__// 53 +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. 105 105 106 -//__Error son the UI donot keep following me__//107 - Before,wehadsomeissues:when you navigatedawayfromtheAPI Gatewaystatistics page,anerrorpop-upwouldkeepfollowingyouthroughout theplatform.To resolvethisissue,youneededto refreshthebrowser.Wehavefixedthisissuepermanentlywiththisrelease,makingtherefreshobsolete.55 +//__Error channel inbounds__// 56 +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. 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:60 +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"]] 62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 128 128 67 + 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:70 +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 72 +* 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. 74 +* 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,8 @@ 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]] 85 +~* 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.87 +~*~* Indicates a next-generation-architecture only feature. 149 149 {{/info}})))((({{toc/}}))){{/container}} 150 150 {{/container}}