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 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
on 2024/01/29 14:48
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,106 @@ 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-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 +//__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 +== **Formatting & Alignments** == 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.25 +//__Input fields__// 26 +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]] 28 +//__UI improvements__// 29 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 27 27 28 -== **Feedback items ** == 31 +//__Runtime overview image versions__// 32 +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. 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 34 +//__Component changes reversion__// 35 +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. 31 31 32 -//__ Correctly definethesizeof a cloud slot whencreatingitforthe firsttime__//33 - Currently,eMagiz will lookto Designwhencreatingthe cloud slot forthe firsttime.This is to avoid you having to“create” yoursolution twice,astherewereinstances whereeMagiz wouldalwayscreate thecloud slot with thesmallestsizeavailable first, even if thiswere not what you wanted.37 +//__State generation statistics__// 38 +The state generation graphs will now show the correct number of cache hits and misses. 34 34 35 -//__ UpdatedinfographicCapture__//36 -A sof now, wehave updatedthe infographicon theCapturephaseto incorporatethenewlookand feeland explaintheupdatedfunctionalityinCapture.40 +//__Queue browser timestamps__// 41 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 37 37 38 -//__ Updated errorfeedbackinDesign__//39 - Before, you could see a transformationerror inDesignevenhoughthetransformationwasnot usedinyour solution (i.e., “datapipeline” functionality).However,whenyou now definespecific integrationasapipelinesolution,the error will notbeown.43 +//__Addition and deletion of internal recipients__// 44 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 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. 46 +== **Feedback Items** == 43 43 44 -//__ Improvedstyling oferrorfeedback on User Management in Deploy__//45 - Withthisreleasewehaveimprovedthestylingofthe feedback pop-upyouget inUser management afterpressing“Applytoenvironment”andseveralupdatescould not beexecuted.48 +//__Update flows__// 49 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 46 46 47 -//__ Showonly the ten latestflow versionswhenselectingaflow version in a Release__//48 -T o improve thequality andspeedofdefiningaelease, we will showonlythelatest ten versions of a flow in the release widget,astheseten aremost likelyto beselectedby a user. If you need anolder version, you can addit via the“Details”optiononthe release.51 +//__Q&A forum search__// 52 +The option to search by pressing the Enter key has been added to the Q&A forum. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 54 +//__Memory settings__// 55 +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. 51 51 52 -//__ Optional Client Secret whenusingthegrant_type Password when callingan OAuth2.0 IDP__//53 - Before,youeededto define the ClientSecretevenforthe grant_typePassword,whereit is not always required.We have correctedthis behaviortoensure thatthisis in linewith theOAuth 2.0 specification.57 +//__Runtime validation__// 58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 54 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 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.63 +//__Removal of onramp__// 64 +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 flowtesting widgetnspecificcircumstanceswas notworking__//101 -W ith this release,wefixed an issue whereyou could notopentheflow testingfunctionalityin theCreate phase when your flow containedaparticular constructioncombinedwiththe “nullChannel.”66 +//__Runtime statistics details__// 67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 102 102 103 -//__ Improved styling whenadding a largemessage to a flow test__//104 - With thisrelease, the stylingof theop-up will not change when you define alargemessageas input (orexpectedoutput)of yourflowtest. This willensurethatyou canstilleasily specifythe flowtestmessage’snameanddescriptionafterenteringthelargemessage.69 +//__Deployment prechecks__// 70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 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 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:75 +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"]]77 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 78 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 79 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 128 128 129 -== **Key takeaways** ==81 +== **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:83 +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 85 +* 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. 87 +* 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]] 97 +~* 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}} 99 +{{/info}} 100 +))) 101 + 102 +((( 103 +{{toc/}} 104 +))) 150 150 {{/container}} 106 +{{/container}}