Wiki source code of 218 - Sprightly Spring
Version 437.1 by Carlijn Kokkeler on 2024/04/08 11:20
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** | ||
| 7 | |||
| 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 our release that will be released on April 11th, 2024, which is this release. | ||
| 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 | ||
| 22 | |||
| 23 | Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. | ||
| 24 | |||
| 25 | 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||target="blank"]]. | ||
| 26 | |||
| 27 | == **Feedback Items** == | ||
| 28 | //__Dynamic trigger__// | ||
| 29 | The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger. | ||
| 30 | |||
| 31 | [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] | ||
| 32 | |||
| 33 | //__Copy to clipboard buttons__// | ||
| 34 | Copy to clipboard buttons have been added to various pages: | ||
| 35 | |||
| 36 | * Deploy agent pop-up | ||
| 37 | * Create - Flow designer: Properties | ||
| 38 | * Deploy - Property releases: Property details | ||
| 39 | |||
| 40 | [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] | ||
| 41 | |||
| 42 | //__Reset H2 database__// | ||
| 43 | For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. | ||
| 44 | |||
| 45 | {{info}}Please note the following: | ||
| 46 | |||
| 47 | * Only H2 databases that are registered under the standard eMagiz data folder will be removed. | ||
| 48 | * It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. | ||
| 49 | * For on-premise runtimes, only a reset of the runtime is needed. | ||
| 50 | |||
| 51 | For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}} | ||
| 52 | |||
| 53 | [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] | ||
| 54 | |||
| 55 | == **Bug Fixes** == | ||
| 56 | //__Runtime overview improvements__// | ||
| 57 | The runtime overview has been improved regarding checks on the runtime version. | ||
| 58 | |||
| 59 | == **Fancy Forum Answers** == | ||
| 60 | |||
| 61 | 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: | ||
| 62 | |||
| 63 | * [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] | ||
| 64 | * [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] | ||
| 65 | |||
| 66 | == **Key Takeaways** == | ||
| 67 | |||
| 68 | 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 | |||
| 70 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 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. | ||
| 73 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 74 | * Check out the release notes [here] | ||
| 75 | * Start thinking about how the license tracker can aid your development | ||
| 76 | * Start thinking about major, minor, and patch | ||
| 77 | * Keep making great integrations | ||
| 78 | |||
| 79 | Let's stay in touch and till next time! | ||
| 80 | |||
| 81 | {{info}} | ||
| 82 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 83 | |||
| 84 | {{/info}} | ||
| 85 | ))) | ||
| 86 | |||
| 87 | ((( | ||
| 88 | {{toc/}} | ||
| 89 | ))) | ||
| 90 | {{/container}} | ||
| 91 | {{/container}} |