Changes for page 194 - Giant Leap

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+188 - Close Encounters

Content

...	...	@@ -2,95 +2,72 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
	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.
6	6
7		-== **Queue Browser** ==
	7	+== **3rd generation runtime bolstering** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	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.
10	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
	11	+//__Migration of JMS backup configuration improved__//
12	12
13		-To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
	13	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	15	+//__Autogenerated exits can be deployed at once__//
16	16
17		-After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
	17	+//__Code mapping functionality available on 3rd generation runtime__//
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	19	+//__Improved the performance of deploying or activating a release__//
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	21	+//__Failing runtimes won't be restarted indefinetly anymore__//
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	23	+== **Exportable Release Audit** ~* ==
33	33
34		-== **3rd generation runtime bolstering** ==
	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.
35	35
36		-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.
	27	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
37	37
38		-//__SOAP and REST web services migration, including splitting them__//
39		-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. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
	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}}
40	40
41		-//__Changing SSL settings for 3rd generation runtime models works__//
42		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
43		-
44		-//__Improved migration for JMS flows__//
45		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
46		-
47		-{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
48		-
49		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
50		-As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
51		-
52		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
53		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
54		-
55		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
56		-With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
57		-
58		-//__Added "Reset" functionality__//
59		-With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
60		-
61	61	== **Feedback items ** ==
62	62
63	63	We have also solved other feedback items besides the flow designer's critical updates.
64	64
	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	+
65	65	//__Improved naming convention on Store related pages__//
66		-We have improved various display names using the merge functionality within our store offering.
	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.
67	67
68		-//__Update security protocols for our internal architecture__//
69		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
	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
70	70
71		-//__Improved read-only description for "if exists" constructions in Transformations__//
72		-To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
	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
73	73
74		-
75		-== **Bug fixes ** ==
76		-
77		-//__Decent validation feedback when not filling in the property value__//
78		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
79		-
80		-//__Incorrect resource locations__//
81		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
82		-
83		-//__Apply to environment in User Management performance improvement__//
84		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
85		-
86	86	== **Fancy Forum Answers** ==
87	87
88	88	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:
89	89
90		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
91		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
92		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
93		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||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"]]
94	94
95	95	== **Key takeaways** ==
96	96