Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 26.1
edited by Erik Bakker
on 2022/10/24 09:01
on 2022/10/24 09:01
Change comment:
There is no comment for this version
To version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
on 2024/01/29 14:41
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 -1 86-DaemonSwitch1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,150 +1,103 @@ 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!** Wehave hit the ground running in thisquarter by not only focusing on larger featuresbut also spenda 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!** This release .... 6 6 7 -== **New monitoring stack** == 8 +== **Pop-up Improvements** == 9 +//__Property releases__// 10 +When a new property release is created, this property release can now be viewed and deleted. 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 restructuredour alerting approach. Fora sneakpreviewof what these changes entailplease check outthefollowing microlearnings.12 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.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-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.Crash Course.Crash Course Platform.advanced-monitoring-apigateway-http-statistics.WebHome||target="blank"]] 14 +//__Runtime deletion__// 15 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 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}} 17 +//__Wiretap & debug error messages__// 18 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 17 17 18 -== **Transformation Improvements** == 20 +//__Action messages__// 21 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 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. 23 +== **User Journey** == 24 +//__Update flows__// 25 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 22 22 23 -//__I mproved Transformation optionsfor booleans__//24 - Ontopof that, wewill introduce additionalfunctionality to transform"Booleantoenumeration," "enumerationtoBoolean," and"Boolean to Boolean."Justas youareused to for the"enumeration to enumeration"transformation,you can now definea valuemapping forachcombination mentionedabove.See belowforanexampleof how thislooks.27 +//__Input fields__// 28 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 27 27 28 -== **Feedback items ** == 33 +//__Q&A forum search__// 34 +The option to search by pressing the Enter key has been added to the Q&A forum. 29 29 30 - Apartfrom thekey updates around functionality, we have also solved other feedbackitems.36 +== **Feedback Items** == 31 31 32 -//__ Correctlydefine thesizeof a cloud slotwhen creatingit for the first time__//33 - Currently,eMagizwilllook to Design whencreating thecloud slot forthe firstme. Thisis to avoidyou havingto“create”yourolutiontwice,astherewereinstanceswhereeMagizwould alwayscreatethe cloudslot withthesmallestzeavailablefirst,evenfthiswerenotwhatyouwanted.38 +//__Memory settings__// 39 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 34 34 35 -//__ Updatedinfographic Capture__//36 - Asofnow,we haveupdatedtheinfographiconthe Capturephase toincorporate thenewlook andfeelandexplainthe updatedfunctionalityin Capture.41 +//__Runtime validation__// 42 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 37 37 38 -//__ Updatederror feedbackinDesign__//39 - Before,youcould see atransformationerror inDesigneventhoughthetransformationwasnotusedinyoursolution(i.e.,“data pipeline” functionality).However,whenyou now definepecificintegration asa data pipelinesolution,theerror willnotbeshown.44 +//__Runtime overview image versions__// 45 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 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 updates when importingstoreitems inDesign including a transformation__//98 -W iththis release,wehavemadeseveralimprovementsforimportingstoreitemsin Design,includinga transformation.Thiswillfurther bolsterouroffering on this.49 +//__Removal of onramp__// 50 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 99 99 100 -//__ Opening flow testing widgetin specific circumstanceswas not working__//101 - Withthis release,wefixedanissuewhere youcouldnotopentheflow testingfunctionalityintheCreatephasewhenyourflowcontainedaparticularconstructioncombinedwith the“nullChannel.”52 +//__Component changes reversion__// 53 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 102 102 103 -//__ Improvedstylingwhenddinga large messagetoaflowtest__//104 - Withthis release,thestyling ofthepop-up will not changewhenyou define a large message asinput(orexpected output) of your flow test. This willensurethat youcan still easily specify theflow testmessage’snameand descriptionafterenteringthelargemessage.55 +//__State generation statistics__// 56 +The state generation graphs will now show the correct number of cache hits and misses. 105 105 106 -//__ Errors onheUI do notkeep followingme__//107 - Before,we hadsomeissues:when you navigatedawayfromtheAPI Gatewaystatistics page,anerror pop-up wouldkeepfollowingyouhroughouttheplatform. To resolve this issue, youneededto refreshthe browser. We have fixedthissuepermanently with this release,making the refreshobsolete.58 +//__Runtime statistics details__// 59 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 108 108 109 -//__ Navigatingback tothe transformation in Create worksgain__//110 - Withthis release, we have squashed a bugthat annoyed users. Before, it could happenthat when you navigated awayfrom the transformationpageinyour flow in Createand returnedlater, thetransformationwas not shownanymore. With this release, we have madesurethat regardlessofwhereyoucomefrom, the transformation will be visible for you tosee.61 +//__Queue browser timestamps__// 62 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 111 111 112 -//__ Remove the qualified namewheneditinga non-legacy Mendix entry in eMagiz__//113 - Withthis release,wehave removedthepossibilityof changing the obsoletequalifiednamewhen editing a non-legacyMendixentry ineMagiz.64 +//__Deployment prechecks__// 65 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 114 114 115 -//__ Selectingtags when drawingalineinCapture__//116 - Wehavenow madethispossible(again). Thisway,youcan directlyselectthe tag(s) you wantinsteadof openingthedetailedinformationonthelineit isalreadyaddedtoCapture.67 +//__Addition and deletion of internal recipients__// 68 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 117 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:72 +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' withvalue '0' willnotbeset sinceit is nota String and noConverter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]126 -* [[ Kafka Consumer Mendix StringDeserializerisnot working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]127 -* [[ Namespaceprefix'xs'hasnotbeendeclared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]74 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 75 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 76 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 128 128 129 -== **Key takeaways** ==78 +== **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:80 +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 82 +* 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. 84 +* 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 139 139 * Start thinking about major, minor, and patch 140 -* Upgrade to the latest build number 141 141 * Keep making great integrations 142 142 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]] 94 +~* 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}} 96 +{{/info}} 97 +))) 98 + 99 +((( 100 +{{toc/}} 101 +))) 150 150 {{/container}} 103 +{{/container}}