Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 289.1
edited by Carlijn Kokkeler
on 2024/08/12 11:58
Change comment: There is no comment for this version
To version 287.1
edited by Carlijn Kokkeler
on 2024/08/12 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,14 +3,10 @@
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
7 -
8 -====Bug fixes====
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 - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
14 -* 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.
15 -* 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.
16 -* 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.
6 +* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'.
7 +* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
8 +* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
9 +* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
10 +* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually.
11 +* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
12 +* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].