Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 91.1
edited by Erik Bakker
on 2023/03/14 06:52
on 2023/03/14 06:52
Change comment:
There is no comment for this version
To version 464.1
edited by CarlijnKokkeler
on 2024/04/23 10:37
on 2024/04/23 10:37
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-BigLeap1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,80 +1,57 @@ 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 couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.6 +**Hi there, eMagiz developers!** 6 6 7 -== **3rd generation improvements** == 8 8 9 -//__Better feedback in 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 reducethenumber of alertsyouwill receive on this 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 migratedyour 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 is put intostandby modewenowalso stopall on-premiseruntimes toavoid excessive logging (and alerting) on your modelsthathavethis functionality activated. The opposite happenswhenthe slotwakeupis triggered. Asaresultnotonlythecloud 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 deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring 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 containerwe now take into account whether"custom error handling" isused within one ofthe event processors.Based onthat determinationspecific additionalcomponents areaddedtoensurethat thestreaming containerwill workaftermigrating without anymanual 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 it is always visiblewhenthenotifications 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 EventStreamingwe have improved the graphs andthe calculationsthatfill the graphs with values. Ontop of that wehave added helptexts to clarify whateach graph ourtabledisplays to you.32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 32 32 33 -//__Improved help text for network volumes__// 34 -With this release we have improved the help text that explains network volumes and how to use them within our solution. 35 - 36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate 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}} 37 - 38 -== **Feedback items ** == 39 - 40 -//__Removed OData as option for an API Gateway operation__// 41 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform. 42 - 43 -//__Changes in API Gateway operation paths is automatically updated in Create__// 44 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry. 45 - 46 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 47 - 48 -== **Bug fixes ** == 49 - 50 -//__Prevent endless loop in Deploy -> User Management__// 51 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 52 - 53 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 54 - 55 -//__Update error handling during migration to the 3rd generation runtime__// 56 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 57 - 58 58 == **Fancy Forum Answers** == 59 59 60 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: 61 61 62 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]] 63 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]] 64 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]] 39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]] 40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]] 41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]] 42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]] 65 65 66 -== **Key takeaways** ==44 +== **Key Takeaways** == 67 67 68 -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:46 +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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 -* Check out the release notes [here] 52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 75 75 * Start thinking about how the license tracker can aid your development 76 76 * Start thinking about major, minor, and patch 77 -* Upgrade to the latest build number 78 78 * Keep making great integrations 79 79 80 80 Let's stay in touch and till next time! ... ... @@ -82,6 +82,11 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a GEN3-only feature. 86 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 87 87 {{/container}} 69 +{{/container}}