Changes for page 191 - Fifty Fifty

Summary

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

Details

Page properties

Content

...	...	@@ -13,60 +13,62 @@
13	13
14	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.
15	15
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.
	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. 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.
18	18
19	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.
	20	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
21	21
22	22	//__Improved migration for JMS flows__//
23	23	This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24	24
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}}
	25	+{{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}}
26	26
27	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.
	28	+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.
29	29
30	30	//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31	31	We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
32	32
	33	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	34	+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.
	35	+
	36	+//__Added "Reset" functionality__//
	37	+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.
	38	+
33	33	== **Feedback items ** ==
34	34
35	35	We have also solved other feedback items besides the flow designer's critical updates.
36	36
37	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.
	44	+We have improved various display names using the merge functionality within our store offering.
39	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.
	46	+//__Update security protocols for our internal architecture__//
	47	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
42	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
	49	+//__Improved read-only description for "if exists" constructions in Transformations__//
	50	+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.
57	57
	52	+
58	58	== **Bug fixes ** ==
59	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.
	55	+//__Decent validation feedback when not filling in the property value__//
	56	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
62	62
	58	+//__Incorrect resource locations__//
	59	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	60	+
	61	+//__Apply to environment in User Management performance improvement__//
	62	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	63	+
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
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"]]
	68	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	69	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	70	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	71	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
70	70
71	71	== **Key takeaways** ==
72	72