Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 458.1
edited by Erik Bakker
on 2024/04/09 16:30
on 2024/04/09 16:30
Change comment:
There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
on 2022/11/21 12:31
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 - 218 -SprightlySpring1 +188 - Close Encounters - Content
-
... ... @@ -1,57 +1,86 @@ 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!** In this release,we willdoalarge maintenance update, moving the eMagiz[[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]stackfrom Spring 5toSpring 6 and from Java 8 to Java 17. Pleaserefertoournew [[runtimeimage>>doc:Main.Release Information.RuntimeImages.V300.WebHome||target="blank"]] andSpring 6 [[migrationpath>>doc:Main.eMagizSupport.MigrationPaths.migration-path-spring-6-migration.WebHome||target="blank"]] formoreinformation. Nextto this, we have improved eventstreaminglogging, sothatlogs arenotclutteredwithirrelevantinfo anymore. Lastly, wehaveremovedthedeprecated 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 the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community. 7 7 8 -== **Spring 6 Migration** == 9 -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** == 10 10 11 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 12 -* JDBC BoneCP data source 13 -* SSL web service message sender 14 -* Web service outbound gateway 15 -* SFTP session factory 16 -* HTTP components message sender 17 -* Job manager 18 -* Credentials 19 -* Simple job launcher 20 -* Default SFTP session factory 9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it. 21 21 22 - {{info}}In ourcontinued efforts to makethe transitionto Spring6 as smooth as possible we have written down the advised process for identifying andupdatingthe relevant flows as aconsequence ofthe Spring6 migration, which youcan find [[here>>doc:Main.eMagiz Support.MigrationPaths.migration-path-spring-6-migration.WebHome||target="blank"]].11 +//__Migration of JMS backup configuration improved__// 23 23 24 - This largemaintenance update, moving theeMagiz runtime stackfrom Spring5 to Spring6 and from Java 8 to Java 17, includesmoving to latest (major) versions of open source projects, libraries and technologies. For this, anew[[runtime image>>doc:Main.ReleaseInformation.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new imageversion, several Springlibraries havebeen changed significantly. Moreinformationcan be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. {{/info}}13 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 25 25 26 - {{info}}Please be aware that we will create autosaved versions foraffectedflows still running on thelegacy runtime architecture. Thisway, we ensureconsistency in what the user sees whenworking with flow componentsin theCreatephase while at the same time prepare your model for a future migration to the current runtime architecture. Shouldyou needto make a functionalchange inone of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}15 +//__Autogenerated exits can be deployed at once__// 27 27 28 -== **Feedback Items** == 29 -//__Event streaming logging__// 30 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 17 +//__Code mapping functionality available on 3rd generation runtime__// 31 31 32 -//__Root Cloud__// 33 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal. 19 +//__Improved the performance of deploying or activating a release__// 34 34 21 +//__Failing runtimes won't be restarted indefinetly anymore__// 22 + 23 +== **Exportable Release Audit** ~* == 24 + 25 +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. 26 + 27 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 28 + 29 +{{warning}}Note that the following restrictions apply when exporting an audit document: 30 + * Changes made on definition and transformation level are **not** restored 31 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 32 + * 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 33 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 34 + 35 +== **Feedback items ** == 36 + 37 +We have also solved other feedback items besides the flow designer's critical updates. 38 + 39 +//__Data Sink Refactor__// 40 +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 your seperately. 41 + 42 +//__Improved naming convention on Store related pages__// 43 +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. 44 + 45 +//__Press "Enter" to search on multiple pages__// 46 +In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows 47 + 48 +* Deploy → Deployment Plan 49 +* Deploy → Properties → History 50 +* Deploy → User Management → Roles 51 +* Manage → Error Messages → Error Messages 52 +* Manage → Error Messages → Flows with Error Messages 53 +* Manage → Error Messages → Exceptions of Error Messages 54 +* Manage → Log Entries 55 +* Manage → Alerts 56 +* Manage → Triggers 57 +* Manage → Tags – Cant find (only Gen2) 58 +* Manage → Notifications 59 +* Manage → Notification Settings 60 +* Manage → Data Usage → History 61 +* Manage → Code mappings → All tabs 62 + 35 35 == **Fancy Forum Answers** == 36 36 37 37 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: 38 38 39 -* [[ ModelDashboard- Manage-color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]40 -* [[ Error handlingwithinXSLT extensiongateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]41 -* [[ RequestingAzuretoken notworkingbecause of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]42 -* [[ PGPSigning and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]67 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 68 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 69 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 70 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 43 43 44 -== **Key Takeaways** ==72 +== **Key takeaways** == 45 45 46 -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:74 +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: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus 50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 51 51 * Clear your browser cache (Ctrl + Shift + Del) 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development 54 54 * Start thinking about major, minor, and patch 83 +* Upgrade to the latest build number 55 55 * Keep making great integrations 56 56 57 57 Let's stay in touch and till next time! ... ... @@ -59,11 +59,6 @@ 59 59 {{info}} 60 60 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 62 -{{/info}} 63 -))) 64 - 65 -((( 66 -{{toc/}} 67 -))) 91 +~*~* Indicates a GEN3-only feature. 92 +{{/info}})))((({{toc/}}))){{/container}} 68 68 {{/container}} 69 -{{/container}}