Changes for page 270 - Round Round

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-266 - Feel Free
	1	+191 - Fifty Fifty

Content

...	...	@@ -1,31 +1,36 @@
1		-This release has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
	1	+The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
4	4
5		-==== Minor changes ====
	5	+=====New features=====
	6	+* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
	7	+** Error Message is to evaluate the headers of the original message which resulted in an error.
	8	+** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
	9	+** Queue Consumers is to configure for queues where more than 1 consumer is expected.
	10	+** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
	11	+** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
6	6
7		-* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
8		-** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
9		-** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
10		-* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
11		-* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
12		-* Create - Add Integrations: Improved how we autogenerate flows for the user.
13		-* General - Platform: Improved our general deletion behavior when deleting a model.
	13	+=====Major changes=====
14	14
15		-==== Bug fixes ====
	15	+* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
16	16
17		-* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
18		-* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
19		-* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
20		-* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
21		-* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
22		-* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
23		-* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
24		-* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
25		-* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
	17	+=====Minor changes=====
26	26
27		-==== Remarks ====
	19	+* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
	20	+* Create - Flow designer: sensitive information stored in property values is masked. (#790)
	21	+* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
	22	+* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
	23	+* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
	24	+* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
	25	+* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
	26	+* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
	27	+* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
28	28
29		-* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30		-* General - Infrastructure: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
31		-** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.
	29	+====Bug fixes====
	30	+* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
	31	+* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
	32	+* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
	33	+* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
	34	+* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
	35	+* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
	36	+