Changes for page 224 - Summer Sonata

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-203 - Fast Paced
	1	+218 - Sprightly Spring

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,46 +1,79 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Release Properties - Early Feedback** ==
8		-The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
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.
	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.WebHome||target="blank"]].
	26	+
10	10	== **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.
11	11
12		-//__"All entries" are now cleaned up as part of the migration__//
13		-To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
	31	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
14	14
15		-//__Trigger ID added to our alerting on the next-generation architecture__//
16		-We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
	33	+//__Copy to clipboard buttons__//
	34	+Copy to clipboard buttons have been added to various pages:
17	17
18		-== **Bug Fixes** ==
	36	+ * Deploy agent pop-up
	37	+ * Create - Flow designer: Properties
	38	+ * Deploy - Property releases: Property details
19	19
20		-//__Ensure no flow can be in a release twice__//
21		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
	40	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
22	22
23		-//__Ensure no flow can be in a release twice__//
24		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
	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.
25	25
	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	+
26	26	== **Fancy Forum Answers** ==
27	27
28	28	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:
29	29
30		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||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"]]
31	31
32		-== **Key takeaways** ==
	66	+== **Key Takeaways** ==
33	33
34		-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:
	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:
35	35
36	36	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
37	37	* If you have feedback or ideas for us, talk to the Platypus
38		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	72	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
39	39	* Clear your browser cache (Ctrl + Shift + Del)
40	40	* Check out the release notes [here]
41	41	* Start thinking about how the license tracker can aid your development
42	42	* Start thinking about major, minor, and patch
43		-* Upgrade to the latest build number
44	44	* Keep making great integrations
45	45
46	46	Let's stay in touch and till next time!
...	...	@@ -48,6 +48,11 @@
48	48	{{info}}
49	49	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50	50
51		-~*~* Indicates a next-generation-architecture only feature.
52		-{{/info}})))((({{toc/}}))){{/container}}
	84	+{{/info}}
	85	+)))
	86	+
	87	+(((
	88	+{{toc/}}
	89	+)))
53	53	{{/container}}
	91	+{{/container}}