Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+188 - Close Encounters

Content

...	...	@@ -2,66 +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!** In the last few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
	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		-== **"Live" mode on flow testing** ==
	7	+== **3rd generation runtime bolstering** ==
8	8
9		-With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
	9	+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.
10	10
11		-By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
	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.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
	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.
14	14
15		-Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
	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.
18	18
19		-== **3rd generation improvements** ==
	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.
20	20
21		-//__Event Streaming statistics completion__//
22		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	26	+== **Exportable Release Audit** ~* ==
23	23
24		-//__Deployments on next generation architecture__//
25		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
	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.
26	26
27		-//__Clean queues option__//
28		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	30	+[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
29	29
	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	+
30	30	== **Feedback items ** ==
31	31
32		-//__On-premise containers are started upon slot wakeup__//
33		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	40	+We have also solved other feedback items besides the flow designer's critical updates.
34	34
35		-//__See Fixed IP in Deploy Architecture__//
36		-To improve our cloud offerings' we now display the configured fixed IP on your cloud connectors. This will unlock you as the user to easily communicate this value to external parties without involvement on our end.
	42	+//__Improved naming convention on Store related pages__//
	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.
37	37
38		-//__Resource path is shown to the user__//
39		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	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.
40	40
41		-//__Flow designer improvements__//
42		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	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
43	43
44		-//__Improved capabilities of a company contact__//
45		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
46		-
47	47	== **Bug fixes ** ==
48	48
49		-//__Optional API parameters are handled correctly__//
50		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
	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.
51	51
52		-//__Without CDM rights nothing related to any data model can be edited anymore__//
53		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
54		-
55		-//__Improved sorting of Design and Deploy archticture__//
56		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
57		-
58	58	== **Fancy Forum Answers** ==
59	59
60	60	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:
61	61
62		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
63		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
64		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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"]]
65	65
66	66	== **Key takeaways** ==
67	67