Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 76.2
edited by Erik Bakker
on 2023/05/09 13:47
on 2023/05/09 13:47
Change comment:
Update document after refactoring.
To version 273.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 (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 197- PayAttention1 +225 - Pop-up Party - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,35 +1,26 @@ 1 - Here is ourfirst release of this quarter. We have delivered additionalminor (bug) fixes in thisreleaseandreleased the Live Flow testing feature.The last is a real improvement duringthedevelopment process of a flow. Furthermore,you will find several enhancements in working in nextGen environments.1 +During our recent sprint cycle 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 196-TheLastPost.WebHome||target=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=====5 +====New features==== 6 6 7 -* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected. 8 8 9 -=====Minor changes===== 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. 10 10 11 -* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly. 12 -* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases. 13 -* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues. 14 -* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items. 15 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690) 16 -* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921) 17 -* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel. 18 -* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions. 19 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix. 20 -* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401 if no API-Key was supplied. Please reset your entry flow to apply the fix. 21 -* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922) 22 -* Deploy - Releases: We reduced the time it takes to prepare a release before it can be deployed. The process of building runtime images has been optimized. 23 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible. 24 -* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543) 25 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run. 26 -* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel. 27 -* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895) 28 -* Administration - Overview: Contracts page removed. (#907) 29 29 30 30 ====Bug fixes==== 31 - 32 -* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations. 33 -* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages. 34 -* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) 35 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940) 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.