Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 450.1
edited by CarlijnKokkeler
on 2024/04/09 16:19
on 2024/04/09 16:19
Change comment:
There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2022/11/21 13:11
on 2022/11/21 13:11
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 - 218 -SprightlySpring1 +188 - Close Encounters - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,60 +1,91 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 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. 5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community. 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. 7 +== **3rd generation runtime bolstering** == 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 9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 22 22 23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. 11 +//__Migration of JMS backup configuration improved__// 12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime. 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"]]. {{/info}} 14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 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"]]. 17 +//__Autogenerated exits can be deployed at once__// 18 +This release has fixed a bug that prevented you from deploying an exit flow correctly. 28 28 29 -{{info}} Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}} 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. 20 +//__Code mapping functionality available on 3rd generation runtime__// 21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality. 34 34 35 -//__ RootCloud__//36 - Optionsand screensrelatedto thedeprecatedcloudoption'Root' havebeen removedfrom theportal.23 +//__Improved the performance when activating a release__// 24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release. 37 37 26 +//__Failing runtimes won't be restarted indefinitely anymore__// 27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped. 28 + 29 +== **Exportable Release Audit** ~* == 30 + 31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 32 + 33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 + 35 +{{warning}}Note that the following restrictions apply when exporting an audit document: 36 + * Changes made on definition and transformation level are **not** restored 37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 38 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 40 + 41 +== **Feedback items ** == 42 + 43 +We have also solved other feedback items besides the flow designer's critical updates. 44 + 45 +//__Data Sink Refactor__// 46 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately. 47 + 48 +//__Improved naming convention on Store related pages__// 49 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 50 + 51 +//__Press "Enter" to search on multiple pages__// 52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 53 + 54 +* Deploy → Deployment Plan 55 +* Deploy → Properties → History 56 +* Deploy → User Management → Roles 57 +* Manage → Error Messages → Error Messages 58 +* Manage → Error Messages → Flows with Error Messages 59 +* Manage → Error Messages → Exceptions of Error Messages 60 +* Manage → Log Entries 61 +* Manage → Alerts 62 +* Manage → Triggers 63 +* Manage → Tags – Cant find (only Gen2) 64 +* Manage → Notifications 65 +* Manage → Notification Settings 66 +* Manage → Data Usage → History 67 +* Manage → Code mappings → All tabs 68 + 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"]] 73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 46 46 47 -== **Key Takeaways** ==77 +== **Key takeaways** == 48 48 49 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:79 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 50 50 51 51 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 83 +* 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 55 * Check out the release notes [here] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 88 +* Upgrade to the latest build number 58 58 * Keep making great integrations 59 59 60 60 Let's stay in touch and till next time! ... ... @@ -62,11 +62,6 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -{{/info}} 66 -))) 67 - 68 -((( 69 -{{toc/}} 70 -))) 96 +~*~* Indicates a GEN3-only feature. 97 +{{/info}})))((({{toc/}}))){{/container}} 71 71 {{/container}} 72 -{{/container}}