Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Deployment Delights
	1	+225 - TBD

Content

...	...	@@ -3,46 +3,31 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have...
	6	+**Hi there, eMagiz developers!**
7	7
8		-== **Release Maintenance** ==
9	9
10		-
11		-
12		-
13		-
14	14	== **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.
15	15
16		-//__Harbor port change__//
17		-The port for which you need to register has been changed ...?
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
18	18
19		-//__Container version overview__//
20		-In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
	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.
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
	18	+== **Bug Fixes** ==
23	23
24		-//__Unchanged containers__//
25		-When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
26	26
27		-//__Rebuilding of images__//
28		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29	29
30	30
31		-== **Bug Fixes** ==
32	32
33		-//__Runtime metrics processing__//
34		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
35		-
36		-//__Deployment plan__//
37		-We solved a bug where a deployment step in the deployment plan could randomly get stuck.
38		-
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
43		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	28	+* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
44	44
45		-== **Key takeaways** ==
	30	+== **Key Takeaways** ==
46	46
47	47	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:
48	48
...	...	@@ -50,10 +50,9 @@
50	50	* If you have feedback or ideas for us, talk to the Platypus
51	51	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52	52	* Clear your browser cache (Ctrl + Shift + Del)
53		-* Check out the release notes [here]
	38	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
54	54	* Start thinking about how the license tracker can aid your development
55	55	* Start thinking about major, minor, and patch
56		-* Upgrade to the latest build number
57	57	* Keep making great integrations
58	58
59	59	Let's stay in touch and till next time!
...	...	@@ -61,7 +61,6 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
64		-~*~* Indicates a next-generation-architecture only feature.
65	65	{{/info}}
66	66	)))
67	67