Changes for page 194 - Giant Leap

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+188 - Close Encounters

Content

...	...	@@ -2,73 +2,76 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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.
	5	+**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6	6
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).
9		-
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}}
11		-
12	12	== **3rd generation runtime bolstering** ==
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. 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.
	11	+//__Migration of JMS backup configuration improved__//
	12	+With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
18	18
19		-//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
	14	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	15	+As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
21	21
22		-//__Improved migration for JMS flows__//
23		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
24	24
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}}
	20	+//__Code mapping functionality available on 3rd generation runtime__//
	21	+As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
26	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 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.
	23	+//__Failing runtimes won't be restarted indefinitely anymore__//
	24	+We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
29	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.
	26	+== **Exportable Release Audit** ~* ==
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.
	28	+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		-//__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.
	30	+[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
38	38
	32	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	33	+ * Works **only** for releases that are promoted and made active on **Production**
	34	+ * You will **only** see changes made during the **current** calendar year
	35	+ * On the first of April all objects of the **last** calendar year will be **removed**.
	36	+ ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	37	+
39	39	== **Feedback items ** ==
40	40
41	41	We have also solved other feedback items besides the flow designer's critical updates.
42	42
43	43	//__Improved naming convention on Store related pages__//
44		-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.
45	45
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.
	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. This release has added this functionality to many more pages across the portal. The complete list is as follows.
48	48
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.
	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
51	51
52		-
53	53	== **Bug fixes ** ==
54	54
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.
	65	+//__Loading problems of Deployment plan execution overview__//
	66	+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.
57	57
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		-
64	64	== **Fancy Forum Answers** ==
65	65
66	66	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:
67	67
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"]]
	72	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	73	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	74	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
72	72
73	73	== **Key takeaways** ==
74	74