Search: "deploy architecture"

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 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

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 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.

Update Steps Use the final R17 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 R17 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.

Update Steps Use the final R8 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 R8 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.

Please learn more about our Runtime Image release notes. Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889) Minor changes Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.

Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) Deploy - User Management: Roles are sorted alphabetically. (#806) Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup.

Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]]. * Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889) ====Minor changes==== * Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information. * Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors. * Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807) * Deploy - User Management: Roles are sorted alphabetically. (#806) * Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup.

Update Steps Use the final template (non-service affecting) 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.

**Update Steps** * Use the final template (non-service affecting) * 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 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 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.