Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version
To version 239.1
edited by Erik Bakker
on 2025/04/07 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +242 - Stability Score
Content
... ... @@ -1,36 +1,18 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
1 +In the last sprint, we have released several items improving the stability of the platform across the various ILM phases. The biggest change we have is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] allowing models running on our current-generation architecture to better utilize their CPU within the cloud models. On top of that, we release various improvements in the platform regarding clarity and stability.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
4 4  
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.
5 +====New Features====
12 12  
13 -=====Major changes=====
7 +* Cloud - Templates: We have implemented a feature for Cloud models to be able to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
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.
9 +====Minor Changes====
16 16  
17 -=====Minor changes=====
11 +* Store - Overview: Statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
12 +* eMagiz Connector - Softcrow: Softcrow restoration is added for the eMagiz Connector.
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.
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  
16 +* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or move right buttons. (#1307)
17 +* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
18 +