Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+203 - Fast Paced

Author

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

Content

...	...	@@ -1,44 +1,46 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	5	+**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
7	7
	7	+== **Release Properties - Early Feedback** ==
	8	+The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
	9	+
8	8	== **Feedback Items** ==
9		-//__Trigger activation__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
13	13
14		-== **Bug Fixes** ==
15		-//__Trigger activation__//
16		-Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
17	17
18		-//__Trigger activation__//
19		-Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
20		-
	18	+//__Improved performance Manage Dashboards__//
	19	+We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
21	21
	21	+== **Bug Fixes** ==
22	22
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
	25	+
23	23	== **Fancy Forum Answers** ==
24	24
25	25	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:
26	26
27		-* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
28		-* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
29		-* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
30	30
31		-== **Key Takeaways** ==
	32	+== **Key takeaways** ==
32	32
33		-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:
	34	+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:
34	34
35	35	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
36	36	* If you have feedback or ideas for us, talk to the Platypus
37		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	38	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38	38	* Clear your browser cache (Ctrl + Shift + Del)
39		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
	40	+* Check out the release notes [here]
40	40	* Start thinking about how the license tracker can aid your development
41	41	* Start thinking about major, minor, and patch
	43	+* Upgrade to the latest build number
42	42	* Keep making great integrations
43	43
44	44	Let's stay in touch and till next time!
...	...	@@ -46,11 +46,6 @@
46	46	{{info}}
47	47	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48	48
49		-{{/info}}
50		-)))
51		-
52		-(((
53		-{{toc/}}
54		-)))
	51	+~*~* Indicates a next-generation-architecture only feature.
	52	+{{/info}})))((({{toc/}}))){{/container}}
55	55	{{/container}}
56		-{{/container}}