Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-218 - Sprightly Spring
	1	+189 - Private Eye

Author

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

Content

...	...	@@ -1,60 +1,85 @@
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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. 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	+== **Private Store** ==
	8	+On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
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
	10	+{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
22	22
23		-Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
	12	+== **3rd generation runtime bolstering** ==
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"]].
	14	+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.
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"]]. {{/info}}
	16	+//__SOAP and REST web services migration including splitting them__//
	17	+With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
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.
	19	+//__Changing SSL settings for 3rd generation runtime models works__//
	20	+As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
34	34
35		-//__Root Cloud__//
36		-Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
	22	+//__Improved migration for JMS flows__//
	23	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
37	37
	25	+{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
	26	+
	27	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	28	+As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
	29	+
	30	+//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
	31	+We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	32	+
	33	+== **Feedback items ** ==
	34	+
	35	+We have also solved other feedback items besides the flow designer's critical updates.
	36	+
	37	+//__Improved naming convention on Store related pages__//
	38	+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.
	39	+
	40	+//__Press "Enter" to search on multiple pages__//
	41	+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.
	42	+
	43	+* Deploy → Deployment Plan
	44	+* Deploy → Properties → History
	45	+* Deploy → User Management → Roles
	46	+* Manage → Error Messages → Error Messages
	47	+* Manage → Error Messages → Flows with Error Messages
	48	+* Manage → Error Messages → Exceptions of Error Messages
	49	+* Manage → Log Entries
	50	+* Manage → Alerts
	51	+* Manage → Triggers
	52	+* Manage → Tags – Cant find (only Gen2)
	53	+* Manage → Notifications
	54	+* Manage → Notification Settings
	55	+* Manage → Data Usage → History
	56	+* Manage → Code mappings → All tabs
	57	+
	58	+== **Bug fixes ** ==
	59	+
	60	+//__Loading problems of Deployment plan execution overview__//
	61	+We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
	62	+
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"]]
	67	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	68	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	69	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
46	46
47		-== **Key Takeaways** ==
	71	+== **Key takeaways** ==
48	48
49		-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:
	73	+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.
	77	+* 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
	82	+* 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		-)))
	90	+~*~* Indicates a GEN3-only feature.
	91	+{{/info}})))((({{toc/}}))){{/container}}
71	71	{{/container}}
72		-{{/container}}