Search: "deploy architecture"

Update Steps Use the final R18 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline of December 14th, 2025

**Update Steps** * Use the final R18 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline of December 14th, 2025

Update Steps Use the final R29 template (non-service affecting)(duration: < 5 minutes) User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems Remarks Deadline is December 14th, 2025

**Update Steps** * Use the final R29 template (non-service affecting)(duration: < 5 minutes) * User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems **Remarks** Deadline is December 14th, 2025

Update Steps Use the final R7 template (non service affecting) (duration: 4 minutes) User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all images have been installed according to the active release.

**Update Steps** * Use the final R7 template (non service affecting) (duration: 4 minutes) * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all images have been installed according to the active release. ** Check if messages pass through the bus by verifying a critical message flow in external systems.

User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

User actions after applying the final template: Check if all runtimes are up via the runtime dashboard or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the model by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime dashboard or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the model by verifying a critical message flow in external systems

//__Show values on the runtime level in Deploy Architecture__// We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.

{{/info}} == **Bug Fixes** == //__Gain the ability again to configure certificates in Deploy Architecture again__// In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. //__Ensure that differing container configurations deploy the correct configuration__// When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes.

Create - Settings: Added support for gen3 upgrade/downgrade when splitting the gateway exit gates depending on the destination container. Deploy - Architecture: Creating routes with a port number that is not unique per machine are blocked. (#647) Model - Permissions: Model contacts can toggle their CDM edit rights. (#642) Bug fixes Login - MFA: Fix for enter key was not working on MFA screen to verify your MFA code after entering the code incorrectly first time. (#651) Homepage: Improved performance of loading the questions which contain high quality images. (#496) Design - Architecture: Topic storages' configured size can not be increased more than what you are contractually allowed to use. (#635) Create - Flow Designer After un-transferring integrations that share a combined entry flow, all of their auto-generated components are removed from the entry connector. (#488) Performance is improved significantly We fix an issue that you cannot start or stop the flow designer when you have been opened the transformation screen. Create - Transformation: refresh button has been reintroduced Deploy - Architecture: The machines have been sorted by their configurated order. (#468) Remarks Mendix Runtime has been upgraded to Mendix 9.12.2.

. * Create - Settings: Added support for gen3 upgrade/downgrade when splitting the gateway exit gates depending on the destination container. * Deploy - Architecture: Creating routes with a port number that is not unique per machine are blocked. (#647) * Model - Permissions: Model contacts can toggle their CDM edit rights. (#642) ==== Bug fixes ==== * Login - MFA: Fix for enter key was not working on MFA screen to verify your MFA code after entering the code incorrectly first time. (#651) * Homepage: Improved performance of loading the questions which contain high quality images. (#496) * Design - Architecture: Topic storages' configured size can not be increased more than what you are contractually allowed to use. (#635) * Create - Flow Designer ** After un-transferring integrations that share a combined entry flow, all of their auto-generated components are removed from the entry connector. (#488) ** Performance is improved significantly ** We fix an issue that you cannot start or stop the flow designer when you have been opened the transformation screen. * Create - Transformation: refresh button has been reintroduced * Deploy - Architecture: The machines have been sorted by their configurated order. (#468) ==== Remarks ==== * Mendix Runtime has been upgraded to Mendix 9.12.2.

User actions after applying the final template: Check if all runtimes are reachable by Deploy Architecture. Check if all flows have been installed according to the active release.

. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.

User actions after applying the final template: Check if all runtimes are up via the runtime overview or Deploy Architecture Check if all runtimes have been installed according to the active release Check if messages pass through the bus by verifying a critical message flow in external systems

* User actions after applying the final template: ** Check if all runtimes are up via the runtime overview or Deploy Architecture ** Check if all runtimes have been installed according to the active release ** Check if messages pass through the bus by verifying a critical message flow in external systems