Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 453.1
edited by Carlijn Kokkeler
on 2024/04/09 16:21
on 2024/04/09 16:21
Change comment:
There is no comment for this version
To version 551.1
edited by Carlijn Kokkeler
on 2024/06/17 12:09
on 2024/06/17 12:09
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 18-Sprightly Spring1 +223 - TBD - Content
-
... ... @@ -4,45 +4,44 @@ 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 6 **Hi there, eMagiz developers!** 7 -In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal. 7 + 8 +== **Feedback Items** == 9 +//__SwaggerUI default__// 10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 8 8 9 -== **Spring 6 Migration** == 10 -As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in this release. 12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 11 11 12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 13 -* JDBC BoneCP data source 14 -* SSL web service message sender 15 -* Web service outbound gateway 16 -* SFTP session factory 17 -* HTTP components message sender 18 -* Job manager 19 -* Credentials 20 -* Simple job launcher 21 -* Default SFTP session factory 14 +== **Bug Fixes** == 15 +//__Cron triggers__// 16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 22 22 23 - Legacy configurations that contain SSL webservicemessagesendercomponents arealso updated withanonruntime affectingchange.18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 24 24 25 -{{info}}In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]]. 20 +//__Trigger activation__// 21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. 26 26 27 -This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. {{/info}} 23 +//__Multiple users deploying__// 24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. 28 28 29 - {{info}}Please be aware that we will create autosaved versions for affected flows still runningon thelegacy runtimearchitecture. This way, we ensure consistency in what the user sees when workingwith flow componentsin theCreate phase whilet thesametime prepare your modelfor a future migration to thecurrent runtimearchitecture. Should you need to makea functional change in one of theseaffected flows, you cando so without a deployment and without usingSpring6 in your legacy runtime. {{/info}}26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 30 30 31 -== **Feedback Items** == 32 -//__Event streaming logging__// 33 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 34 34 35 -//__ RootCloud__//36 - Optionsand screensrelatedtothedeprecatedcloudoption'Root'havebeenremovedfromtheportal.31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 37 37 34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 36 + 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 38 + 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]] 43 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]] 44 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]] 45 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]] 43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 46 46 47 47 == **Key Takeaways** == 48 48 ... ... @@ -52,7 +52,7 @@ 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 53 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 54 * Clear your browser cache (Ctrl + Shift + Del) 55 -* Check out the release notes [here] 54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 58 58 * Keep making great integrations