Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 96.1
edited by Erik Bakker
on 2023/06/22 13:26
on 2023/06/22 13:26
Change comment:
There is no comment for this version
To version 239.1
edited by Erik Bakker
on 2025/04/07 09:25
on 2025/04/07 09:25
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 00-Uncharted Territories1 +242 - Stability Score - Content
-
... ... @@ -1,27 +1,18 @@ 1 -In the last sprint cycle, wefocusedonimproving various aspectsoftheportalfunctionality.Among others,we focusedonthenext-generation architectureand others.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.2 00-Uncharted Territories.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]]. 4 4 5 -==== =Minorchanges=====5 +====New Features==== 6 6 7 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar. 8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are: 9 -** For Kafka templates: 10 -*** Batch size: 200000 11 -*** Linger: 300 12 -** For Kafka message listener containers 13 -*** Fetch min. amount: 100000 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 - {{warning}}The existing Kafka components in yourflows will automatically be updated withthe new best practice values. To make deployingthese changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}9 +====Minor Changes==== 16 16 17 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 18 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. 19 -* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information. 20 -* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore. 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. 21 21 22 22 ====Bug fixes==== 23 23 24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957) 25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet. 26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956) 27 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964) 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 +