Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 28.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 281.2
edited by Carlijn Kokkeler
on 2023/12/04 15:08
on 2023/12/04 15:08
Change comment:
Update document after refactoring.
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 86- DaemonSwitch1 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,138 +1,66 @@ 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 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!6 +**Hi there, eMagiz developers!** We have... 6 6 7 -== ** New monitoring stack** ==8 +== **Alerts** == 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. 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 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.HTTP Statistics.WebHome||target="blank"]] 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 15 15 16 - {{info}}Notethat thenew monitoring stack is only available for models that run the new runtime architecture. Should you wish tobecomean early adopter pleasecontactus atproductmanagement@emagiz.com to discussthe possibilities{{/info}}16 +== **Feedback Items** == 17 17 18 -== **Transformation Improvements** == 18 +//__Container version overview__// 19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 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. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 22 22 23 -//__ Improved Transformation options for booleans__//24 - Ontopfthat,weillintroduceadditionalfunctionalitytotransform"Booleantoenumeration," "enumeration to Boolean,"and" Booleanto Boolean." Just as you areused to for the"enumerationtoenumeration" transformation,you can nowdefine a valuemapping for each combinationmentioned above.See belowforan example of howthis looks.23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 27 27 28 -== **Feedback items ** == 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 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 updates whenimporting storeitems in Design includinga transformation__//98 - With thisrelease, we have madeseveralmprovementsforimportingstoreitems inDesign, includingatransformation. This will furtherbolsterourfferingon this.32 +//__Runtime metrics processing__// 33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 99 99 100 -//__ Opening flow testing widgetin specific circumstances was not working__//101 -W iththisrelease, we fixed anissuewhereyoucouldnot openheflow testingfunctionalityintheCreatephase when your flow containedaparticularconstructioncombinedwiththe “nullChannel.”35 +//__Deployment plan__// 36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 102 102 103 -//__ Improved styling when adding a large messageto a flow test__//104 - Withthis release,thestylingofthe pop-up willnot changewhenyou definealargemessage asinput(or expected output) of yourflow test. Thiswillensurethat you cantilleasily specifytheflowtestmessage’s name and descriptionafter entering the large message.38 +//__Store message merging__// 39 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 105 105 106 -//__ Errors on theUIdo notkeepfollowing me__//107 - Before,we had someissues:whenyou navigatedaway from theAPI Gatewaystatisticspage,anerrorpop-up would keepfollowing youthroughoutthe platform.Tosolvethisissue, you neededtofreshthebrowser.Wehavefixedthisissuepermanentlywiththisrelease,makingtherefresh obsolete.41 +//__View all store items__// 42 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 108 108 109 -//__ Navigatingback tothetransformation in Create works again__//110 -W iththisrelease, we havesquasheda bugthat annoyedusers. Before, it could happenthatwhen you navigated awayfromthetransformationpagen yourflowin Create and returned later,the transformationwasnot shownanymore. With this release,wehavemadesurethatregardlessofwhereyoucomefrom, the transformationwill be visible for youtosee.44 +//__Out of memory behavior__// 45 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 111 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. 47 +//__Max fetch size__// 48 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 49 + 114 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:53 +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"]] 55 +* [[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:59 +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 61 +* 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. 63 +* 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]] 74 +~* 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}} 76 +~*~* Indicates a next-generation-architecture only feature. 77 +{{/info}} 78 +))) 79 + 80 +((( 81 +{{toc/}} 82 +))) 150 150 {{/container}} 84 +{{/container}}