Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+225 - TBD

Author

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

Content

...	...	@@ -1,90 +1,86 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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	+**Hi there, eMagiz developers!**
6	6
7		-== **3rd generation runtime bolstering** ==
8	8
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.
	9	+== **Feedback Items** ==
	10	+//__Alerting notification settings__//
	11	+The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
10	10
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.
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
13	13
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.
	15	+//__Process containers__//
	16	+If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	18	+//__Design settings__//
	19	+When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
19	19
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.
	21	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
22	22
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.
	23	+//__Untested images__//
	24	+ A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
	25	+
	26	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
25	25
26		-== **Exportable Release Audit** ~* ==
	28	+//__Infinispan Cache Manager__//
	29	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	30	+
	31	+//__Infinispan Cache Manager error message__//
	32	+We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
27	27
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.
	34	+//__Flow bump__//
	35	+When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
	36	+
	37	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
29	29
30		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	39	+//__Unused support objects__//
	40	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
31	31
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}}
	42	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	43	+
	44	+//__Deleting routes__//
	45	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
37	37
38		-== **Feedback items ** ==
	47	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
39	39
40		-We have also solved other feedback items besides the flow designer's critical updates.
	49	+//__Debug queue__//
	50	+The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
	51	+
	52	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	53	+
	54	+== **Bug Fixes** ==
	55	+//__Internal server error__//
	56	+The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
41	41
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.
	58	+//__Namespace update__//
	59	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
44	44
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.
	61	+//__Error pop-up__//
	62	+We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
47	47
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
	64	+//__SMB inbound channel adapter__//
	65	+The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again.
62	62
63		-== **Bug fixes ** ==
64		-
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.
67		-
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
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"]]
	71	+* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
75	75
76		-== **Key takeaways** ==
	73	+== **Key Takeaways** ==
77	77
78		-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:
	75	+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:
79	79
80	80	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81	81	* If you have feedback or ideas for us, talk to the Platypus
82		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	79	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83	83	* Clear your browser cache (Ctrl + Shift + Del)
84		-* Check out the release notes [here]
	81	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
85	85	* Start thinking about how the license tracker can aid your development
86	86	* Start thinking about major, minor, and patch
87		-* Upgrade to the latest build number
88	88	* Keep making great integrations
89	89
90	90	Let's stay in touch and till next time!
...	...	@@ -92,6 +92,11 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a GEN3-only feature.
96		-{{/info}})))((({{toc/}}))){{/container}}
	91	+{{/info}}
	92	+)))
	93	+
	94	+(((
	95	+{{toc/}}
	96	+)))
97	97	{{/container}}
	98	+{{/container}}