Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 94.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 226.1
edited by Erik Bakker
on 2025/02/10 09:31
on 2025/02/10 09:31
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 +238 - Preparation Paraside - Content
-
... ... @@ -1,27 +1,12 @@ 1 -In the last sprint cycle, we focused on improvingvariousaspects of theportal functionality.Among others, wefocusedon the next-generation architectureand others.1 +In the last sprint, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform. 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.238 - Preparation Paradise.WebHome||target="blank"]]. 4 4 5 -==== =Minorchanges=====5 +====Minor Changes==== 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 +* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system. 8 +* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]]. 14 14 15 - 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. 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) 12 +* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)