Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 135.1
edited by Carlijn Kokkeler
on 2023/10/23 16:39
on 2023/10/23 16:39
Change comment:
There is no comment for this version
To version 272.1
edited by Carlijn Kokkeler
on 2024/07/16 15:20
on 2024/07/16 15:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07-AlignedState1 +225 - Pop-up Party - Content
-
... ... @@ -1,46 +1,26 @@ 1 - In the last sprint cycle, we focused on deliveringstate generation components. On top of that, we made severalimprovements regarding the alignment ofcomponents,and didsomeperformanceimprovementsand bug fixes. Moreover, we made achange in the metrics storageduration.1 +During our recent sprint cycle 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 07-AlignedState .WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.225 - Pop-up Party||target="blank"]]. 4 4 5 -=====New features===== 6 -* State generation: New state generation features have been added. Please check out the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information. 5 +====New features==== 7 7 8 -=====Minor changes===== 9 9 10 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845) 11 -* Create - Framework: The framework used in the flow designer has been updated, improving performance. 12 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing. 13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009) 14 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993) 15 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase. 16 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064) 17 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines. 18 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well. 19 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy. 20 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024) 21 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications. 22 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069) 23 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070) 24 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) 25 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action. 26 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database. 8 +====Minor changes==== 9 +* Design - Architecture: If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern. (#1297) 10 +* Design - Settings: When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment. (#787) 11 +* Deploy - Releases: A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before. 12 +* Create - Flow Designer: Added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 13 +* Create - Flow Designer: Improved the error message when configuring an Infinispan Cache Manager with 'TCP-ping' transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 14 +* Create - Resources: When bumping a new version of flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. (#1326) 15 +* Create - Flow Designer: Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. (#795) 16 +* Deploy - Architecture: For clarity purposes, a confirmation pop-up will be shown when deleting routes. 17 +* Manage - Explore: The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 27 27 28 28 29 - 30 30 ====Bug fixes==== 31 - 32 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. 33 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported. 34 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions. 35 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888) 36 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027) 37 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. 38 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 39 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information. 40 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim". 41 - 42 - 43 - 44 -=====Infra and image changes===== 45 - 46 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards. 21 +* Design - Message mapping: We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. (#1357) 22 +* Create: The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. (#1159) 23 +* Create - Flow Designer: Editing a namespace used in a message definition automatically updates the message definition & transformations. 24 +* Create - Flow Designer: The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with \ instead of /. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain / again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 25 +* Manage - Monitoring: The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 26 +* All - Updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.