Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+200 - Uncharted Territories

Author

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

Content

...	...	@@ -1,17 +1,27 @@
1		-In the last sprint cycle, 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. Find out about the rest below!
	1	+In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]].
4	4
5		-====New features====
6		-* Design - Architecture: 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.
	5	+=====Minor changes=====
7	7
8		-====Bug fixes====
9		-* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
10		-* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
11		-* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)4
12		-* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
13		-* Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
14		-* Deploy - Releases: 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. (#1293)
	7	+* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
	8	+* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
	9	+** For Kafka templates:
	10	+*** Batch size: 200000
	11	+*** Linger: 300
	12	+** For Kafka message listener containers
	13	+*** Fetch min. amount: 100000
15	15
	15	+{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
16	16
	17	+* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	18	+* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
	19	+* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
	20	+* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
17	17
	22	+====Bug fixes====
	23	+
	24	+* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
	25	+* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
	26	+* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
	27	+* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)