Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+222 - Flee Frustration

Author

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

Content

...	...	@@ -1,53 +1,49 @@
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!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
	6	+**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
6	6
7		-== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
8		-
9		-As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
10		-
11	11	== **Feedback Items** ==
	9	+//__Cron triggers__//
	10	+Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
12	12
13		-//__Improved Validation when migrating to the next-generation architecture__//
14		-To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	14	+//__Design changes__//
	15	+If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
17	17
18		-//__Improved HTTP Statistics__//
19		-To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	17	+[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
20	20
21		-//__Show values on the runtime level in Deploy Architecture__//
22		-We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	19	+== **Bug Fixes** ==
	20	+//__Trigger activation__//
	21	+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.
23	23
24		-{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25		-* JMS - The number of queues in the active release.
26		-* Messaging Container - The number of messaging integrations in the active release.
27		-* Messaging Connector - The number of messaging integrations related to this system in the active release.
28		-* API Gateway Container - The number of operations in the active release.
29		-* Event Streaming Container - The number of event processors in the active release.
	23	+//__Multiple users deploying__//
	24	+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.
30	30
31		-There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	26	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
32	32
33		-== **Bug Fixes** ==
	28	+//__Invalid memory configurations__//
	29	+We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
34	34
35		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
36		-In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	31	+//__Property value synchronization__//
	32	+Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
37	37
38		-//__Ensure that differing container configurations deploy the correct configuration__//
39		-When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	34	+//__JMS number__//
	35	+The number on the JMS container correctly displays the amount of queues present in Design.
40	40
41		-//__Remove queurying options in Manage__//
42		-To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
	37	+[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
43	43
44	44	== **Fancy Forum Answers** ==
45	45
46	46	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:
47	47
48		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	43	+* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
	44	+* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
49	49
50		-== **Key takeaways** ==
	46	+== **Key Takeaways** ==
51	51
52	52	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:
53	53
...	...	@@ -55,10 +55,9 @@
55	55	* If you have feedback or ideas for us, talk to the Platypus
56	56	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57	57	* Clear your browser cache (Ctrl + Shift + Del)
58		-* Check out the release notes [here]
	54	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
59	59	* Start thinking about how the license tracker can aid your development
60	60	* Start thinking about major, minor, and patch
61		-* Upgrade to the latest build number
62	62	* Keep making great integrations
63	63
64	64	Let's stay in touch and till next time!
...	...	@@ -66,6 +66,11 @@
66	66	{{info}}
67	67	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68	68
69		-~*~* Indicates a next-generation-architecture only feature.
70		-{{/info}})))((({{toc/}}))){{/container}}
	64	+{{/info}}
	65	+)))
	66	+
	67	+(((
	68	+{{toc/}}
	69	+)))
71	71	{{/container}}
	71	+{{/container}}