Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
on 2023/01/31 14:39
Change comment:
There is no comment for this version
To version 191.1
edited by Carlijn Kokkeler
on 2024/01/29 15:29
on 2024/01/29 15:29
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 91-FiftyFifty1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,36 +1,31 @@ 1 - Thereleaseintroducesalotofsmallfixesasaresultofour"hackathon"efforts.Subsequentlywewillreleaseseveral3rdgenerationruntimeofferings.1 +In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 91-FiftyFifty.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.213 - Joyful Journeys||target="blank"]]. 4 4 5 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. 12 12 13 - =====Majorchanges=====7 +* Home - Q&A: The option to search by pressing the Enter key has been added. 14 14 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 - 17 17 =====Minor changes===== 18 18 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. 11 +* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822) 12 +* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172) 13 +* Create - Transformation: UI improvements for static input components have been done. (#1172) 14 +* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129) 15 +* Deploy - Releases: When a new property release is created, this property release can now be viewed and deleted. (#1031) 16 +* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053) 17 +* Deploy - Runtime overview: Insight into invented and actual deployments has been improved. 18 +* Deploy - Architecture: It is now possible to change the memory settings of a container before pressing "Apply to environment". (#968) 19 +* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977) 20 +* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved. 21 +* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved. 28 28 29 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 36 25 +* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021) 26 +* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030) 27 +* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 28 +* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161) 29 +* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 30 +* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. 31 +* Manage - Notification settings: Internal recipients are now added correctly.