Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-195 - Easter Party
	1	+227 - Fix Frenzy

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,34 +1,17 @@
1		-As a quarter has come to a close we went silent for a couple of weeks to plan ahead for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with good spirit after solving several smaller feedback items and bugs reported by you. In this and the upcoming release several of those stories will be included. On top of that we introduce various improvements to our API Gateway pattern and to our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the various improvements.
	1	+During our recent sprint cycle, we have ......
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4	4
5		-=====New features=====
	5	+====Minor changes====
	6	+* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
6	6
7		-* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8		-* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889)
9		-
10		-=====Minor changes=====
11		-
12		-* Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.
13		-* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors.
14		-* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
15		-* Deploy - User Management: Roles are sorted alphabetically. (#806)
16		-* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
17		-* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements.
18		-* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
19		-
20	20	====Bug fixes====
21		-
22		-* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
23		-* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
24		-* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
25		-* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
26		-* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
27		-* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
28		-* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet it occurred (#825)
29		-* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
30		-* Manage - Alerting: Editable column shows the correct value.
31		-
32		-====Remarks====
33		-
34		-* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours because of data migration. You will get an error stating that the version is incompatible with the selected feature until the migration is finished.
	9	+* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
	10	+* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
	11	+* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
	12	+* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
	13	+* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release.
	14	+* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
	15	+* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
	16	+* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
	17	+* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.