Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 94.1
edited by Erik Bakker
on 2023/03/17 08:35
on 2023/03/17 08:35
Change comment:
There is no comment for this version
To version 466.1
edited by CarlijnKokkeler
on 2024/04/23 10:49
on 2024/04/23 10:49
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 -19 4-GiantLeap1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,82 +1,65 @@ 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!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.6 +**Hi there, eMagiz developers!** 6 6 7 -== **3rd generation improvements** == 8 8 9 -//__Better feedback in the error log when a corrupt stylesheet is encountered__// 10 -We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action. 9 +== **Feedback Items** == 10 +//__Machine agents__// 11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE. 11 11 12 -//__ Better internal errorhandling toavoid unnecessary alerting and notifications__//13 -We haveimprovedthe internalerror handling when sending metrics fromtheruntime toour monitoringstack.Thiswill gravely reducethealertsyou receiveonthis topicwhenyourmodel runsonthe3rd generationmonitoringstack.13 +//__Custom webhook__// 14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more HERE. 14 14 15 -//__ ImprovedManageDashboard__//16 - Thisreleaseimproveswhatyoucansee inthe ManageDashboardafteryou migrateyour modeltothe3rdgenerationruntimearchitecture.16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4 17 17 18 -//__Improved p rocess surrounding"slot standby" and "slot wakeup" for3rd generation runtimes__//19 - Whenaslot isput intostandby mode,we also stopallon-premise runtimestoavoidexcessive logging(and alerting) on yourmodels with this functionality. The oppositehappens whenthe slotwakeupis triggered. Asaresult,notonlythecloud runtimesare started but also all on-premise runtimes.19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 20 20 21 -//__Improved process of deploy preparation__// 22 -With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced. 22 +== **Bug Fixes** == 23 +//__Error handling__// 24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 23 23 24 -//__ Improvedmigrationof Streamingcontainer__//25 - When migrating yourstreaming container, we now considerwhether "custom error handling" isused within one ofthe event processors.Based onthat determination,additionalcomponents areaddedtoensurethat thestreaming containerwill workaftermigrating withoutmanual intervention.26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 26 26 27 -//__ Add HistorytoNotificationsin Manage__//28 - To improve theauditability of ourplatform, wehaveintroducedanaudittrailto the Notificationsection in Manageformodelsrunning on our 3rd generation monitoring stack. This way,itis always visible whenthenotifications werepausedand who pausedor unpausedthe notifications.29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 29 29 30 -//__ Improved Manage phasefor EventStreaming__//31 - Basedon thefeedbackon ourfirst iterationof theManagephasefor EventStreaming,we have improved the graphs andthe calculationsthatfill the graphs with values. Ontop of that, wehave added help texts to clarify whateach chartourtabledisplays to you.32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 32 32 33 -//__ Improvedhelptext fornetwork volumes__//34 - Withthisrelease,wehaveimprovedthehelptextthatexplains networkvolumesandhowtousethemwithin oursolution.35 +//__Unused properties__// 36 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 35 35 36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 38 +//__Enumeration values__// 39 +Enumeration values for event processors can now be edited in Create. 37 37 38 -== **Feedback items ** == 41 +//__SFTP sessions__// 42 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE. 39 39 40 -//__Generation of security logic API Gateway in case of API Key as security method is improved__// 41 -With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism. 42 - 43 -//__User Roles are sorted alphabetically__// 44 -All user roles under User Management are now also sorted alphabetically. 45 - 46 -//__Name of keystore for user management now includes the environment__// 47 -To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename. 48 - 49 -//__Improved Topic calculations in Design Architecture__// 50 -Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level. 51 - 52 -== **Bug fixes ** == 53 - 54 -//__Consolidated upgrade process cloud template__// 55 -With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud. 56 - 57 -//__Ensure users can deploy release on environments they have edit rights on__// 58 -Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so. 59 - 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 64 -* [[ APISecuritynotupdatedinall entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]65 -* [[ Preventingexceptionstriggeringon HTTP 400 statuscode>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]66 -* [[De ployment of 3rdgenruntimestoAzureKubernetes Service(AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]48 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 49 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 50 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 67 67 68 -== **Key takeaways** ==52 +== **Key Takeaways** == 69 69 70 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:54 +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: 71 71 72 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 * If you have feedback or ideas for us, talk to the Platypus 74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 58 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 75 75 * Clear your browser cache (Ctrl + Shift + Del) 76 -* Check out the release notes [here] 60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 77 77 * Start thinking about how the license tracker can aid your development 78 78 * Start thinking about major, minor, and patch 79 -* Upgrade to the latest build number 80 80 * Keep making great integrations 81 81 82 82 Let's stay in touch and till next time! ... ... @@ -84,6 +84,11 @@ 84 84 {{info}} 85 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]] 86 86 87 -~*~* Indicates a GEN3-only feature. 88 -{{/info}})))((({{toc/}}))){{/container}} 70 +{{/info}} 71 +))) 72 + 73 +((( 74 +{{toc/}} 75 +))) 89 89 {{/container}} 77 +{{/container}}