Changes for page 204 - Found It

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-200 - Uncharted Territories
	1	+201 - Be Informed

Content

...	...	@@ -1,27 +1,30 @@
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.
	1	+In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.201 - Be Informed.WebHome||target= "blank"]].
4	4
5	5	=====Minor changes=====
6	6
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
	7	+* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
	8	+* Design-Architecture: Topic Storage detail page contains help text. (#994)
	9	+* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
	10	+* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
	11	+* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
	12	+* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
	13	+* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
	14	+* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
	15	+** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
	16	+** Changes with a direct effect will not be listed (for example, restarting a machine).
14	14
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		-
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.
21		-
22	22	====Bug fixes====
23	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)
	20	+* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
	21	+* Design - Settings: The full length of the contract number can now be registered. (#958)
	22	+* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
	23	+* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
	24	+* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
27	27	* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
	26	+
	27	+=====Infra and image changes=====
	28	+
	29	+* Changed the endpoint for sending error messages to the eMagiz Control Tower.
	30	+* Updated the Spring version of the gateway supporting deploy and manage phase operations.