Search: "deploy architecture"

. (#643) Create - Transformation: For new transformers the default output data type is set to the destination attribute data type. Deploy - Architecture Planned cloud upgrades can be executed manually before the plan date.

This does not happen anymore and long messages can be written with no further inconvenience. (#635) Create - Message type: The message type’s display will be updated when you change the its display name in Capture phase or Design phase. (#656) Create - System Message: Improved creation of enumeration for xml definition attributes so that the enumeration is automatically coupled to the attribute. (#200) Deploy - Architecture: For new machines, size changes in design architecture were not applied to deploy architecture, until after the first deployment. (#521) Deploy - Manage: Leaving the API statistics page does not result in error messages. (#541) Design - Message Mapping: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) Create - Transformation: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) Design - Integrations: For the data pipeline integration, errors of message mapping will be ignored. (#592) Remarks Capture - Settings: Tags: Added Save button for when creating/editing a tag. (#247) Mendix Runtime has been upgraded to Mendix 9.12.3.

. (#643) * Create - Transformation: For new transformers the default output data type is set to the destination attribute data type. * Deploy - Architecture * Planned cloud upgrades can be executed manually before the plan date.

This does not happen anymore and long messages can be written with no further inconvenience. (#635) * Create - Message type: The message type’s display will be updated when you change the its display name in Capture phase or Design phase. (#656) * Create - System Message: Improved creation of enumeration for xml definition attributes so that the enumeration is automatically coupled to the attribute. (#200) * Deploy - Architecture: For new machines, size changes in design architecture were not applied to deploy architecture, until after the first deployment. (#521) * Deploy - Manage: Leaving the API statistics page does not result in error messages. (#541) * Design - Message Mapping: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) * Create - Transformation: Fix the bug which crashes the widget if the browser is resized from another tab (which doesn't contain the widget). (#655) * Design - Integrations: For the data pipeline integration, errors of message mapping will be ignored. (#592) ====Remarks==== * Capture - Settings: Tags: Added Save button for when creating/editing a tag. (#247) * Mendix Runtime has been upgraded to Mendix 9.12.3.

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

Update Steps Use the final R22 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 R22 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 R16 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 R16 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 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