Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01

From version 294.1
edited by Carlijn Kokkeler
on 2023/12/18 12:32
Change comment: There is no comment for this version
To version 435.1
edited by Carlijn Kokkeler
on 2024/04/08 11:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +218 - Sprightly Spring
Content
... ... @@ -5,36 +5,66 @@
5 5  
6 6  **Hi there, eMagiz developers!**
7 7  
8 -== **TBD** ==
9 9  
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.
10 10  
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
11 11  
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 runtime>>doc:Main.Support.Migration Paths.migration-path-spring-6-migration||target="blank"]].
26 +
12 12  == **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.
13 13  
14 -//__Missing properties overview__//
15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
16 16  
17 -ADD FIGURE
33 +//__Copy to clipboard buttons__//
34 +Copy to clipboard buttons have been added to various pages:
18 18  
19 -//__Broker queue metrics dashboards__//
20 -It is now possible to select the MQTT broker in the queue metrics dashboards.
36 + * Deploy agent pop-up
37 + * Create - Flow designer: Properties
38 + * Deploy - Property releases: Property details
21 21  
22 -== **Bug Fixes** ==
40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
23 23  
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.
24 24  
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 +
25 25  == **Fancy Forum Answers** ==
26 26  
27 27  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:
28 28  
29 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
30 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
31 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
32 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
33 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
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"]]
34 34  
66 +== **Key Takeaways** ==
35 35  
36 -== **Key takeaways** ==
37 -
38 38  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:
39 39  
40 40  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -44,7 +44,6 @@
44 44  * Check out the release notes [here]
45 45  * Start thinking about how the license tracker can aid your development
46 46  * Start thinking about major, minor, and patch
47 -* Upgrade to the latest build number
48 48  * Keep making great integrations
49 49  
50 50  Let's stay in touch and till next time!
... ... @@ -52,7 +52,6 @@
52 52  {{info}}
53 53  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
54 54  
55 -~*~* Indicates a next-generation-architecture only feature.
56 56  {{/info}}
57 57  )))
58 58