Changes for page 256 - Power Up

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-255 - Fine Form
	1	+201 - Be Informed

Content

...	...	@@ -1,21 +1,30 @@
1		-This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to allow specific customers to run on our MAM functionality.
	1	+In the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.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		-==== Minor changes ====
	5	+=====Minor changes=====
6	6
7		-* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available.
8		-* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
9		-* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release.
10		-** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing.
11		-* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485)
	7	+* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#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 improvements to the edit integration page. (#954)
	11	+* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969)
	12	+* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983)
	13	+* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979)
	14	+* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828)
	15	+** Changes made in Deploy Architecture with an effect to 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).
12	12
13		-==== Bug fixes ====
	18	+====Bug fixes====
14	14
15		-* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611)
16		-* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569)
17		-* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368)
18		-** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again.
19		-** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ
	20	+* Design - Solutions: We fixed an issue that a message mapping error is displayed 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 Gen3 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 you 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)
	25	+* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
20	20
	27	+=====Infra and image changes=====
21	21
	29	+* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower.
	30	+* Updated the Spring version of the gateway supporting deploy and manage phase operations.