Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Content

...	...	@@ -1,71 +1,26 @@
1		-{{container}}
2		-{{container layoutStyle="columns"}}(((
3		-[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
	1	+In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact.
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.
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explores.WebHome||target="blank"]].
6	6
7		-== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
	5	+=====New features=====
8	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.
	7	+* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template release notes for more information.
10	10
11		-== **Feedback Items** ==
	9	+=====Minor changes=====
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.
	11	+* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
	12	+* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
	13	+* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
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.
	16	+====Bug fixes====
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.
	18	+* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
	19	+* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
	20	+* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
	21	+* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
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.
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}}
	24	+=====Infra and image changes=====
32	32
33		-== **Bug Fixes** ==
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.
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.
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.
43		-
44		-== **Fancy Forum Answers** ==
45		-
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		-
48		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
49		-
50		-== **Key takeaways** ==
51		-
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		-
54		-* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55		-* If you have feedback or ideas for us, talk to the Platypus
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		-* Clear your browser cache (Ctrl + Shift + Del)
58		-* Check out the release notes [here]
59		-* Start thinking about how the license tracker can aid your development
60		-* Start thinking about major, minor, and patch
61		-* Upgrade to the latest build number
62		-* Keep making great integrations
63		-
64		-Let's stay in touch and till next time!
65		-
66		-{{info}}
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		-
69		-~*~* Indicates a next-generation-architecture only feature.
70		-{{/info}})))((({{toc/}}))){{/container}}
71		-{{/container}}
	26	+* No infra and/or image changes is this release.