Search: "deploy architecture"

. (#1544) XML to EDI transformer EDI to XML transformer XML to UN/EDIFACT transformer UN/EDIFACT to XML transformer Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.

Bug fixes Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456) Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559) Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532) Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523) Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511) Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.

. (#1544) ** XML to EDI transformer ** EDI to XML transformer ** XML to UN/EDIFACT transformer ** UN/EDIFACT to XML transformer * Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine. * Manage - Statistics: We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards. ====Bug fixes==== * Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456) * Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559) * Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532) * Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523) * Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511) * Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.

. (#857) Design - Message Mapping: Users can now refresh their Design message mappings. (#848) Deploy - Architecture (Routes): Various help texts have been updated on this pop-up to better clarify what these fields are used for. (#1536) Bug fixes Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager. Prevent auto-fill on specific fields by renaming labels Applied styling to hide the Keeper button in input fields where undesired. Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646) Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful.

. (#857) * Design - Message Mapping: Users can now refresh their Design message mappings. (#848) * Deploy - Architecture (Routes): Various help texts have been updated on this pop-up to better clarify what these fields are used for. (#1536) ==== Bug fixes ==== * Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager. ** Prevent auto-fill on specific fields by renaming labels ** Applied styling to hide the Keeper button in input fields where undesired. * Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646) * Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful.

Minor changes Event Streaming - Data Retention: When DSH retention time is changed on the company level, deleting the topic by excluding it in Design > Architecture and applying the change in Deploy > Architecture and including it again in Design > Architecture and applying the change in Deploy > Architecture results in the retention time being updated in DSH.

This ensures that when you select a flow, the correct one opens as expected. Deploy - Architecture: We have fixed a bug for DSH-enabled event streaming models, which may have prematurely lost read/write access to deleting topics if the topic was still in use in the active release.

. ==== Minor changes ==== * Event Streaming - Data Retention: When DSH retention time is changed on the company level, deleting the topic by excluding it in Design > Architecture and applying the change in Deploy > Architecture and including it again in Design > Architecture and applying the change in Deploy > Architecture results in the retention time being updated in DSH. ** Note that this action will delete the topic and therefore will result in **data loss**. * Design - System: Importing an Open Specification V2 has been deprecated, and it’s not supported anymore at eMagiz. * Design - System Message: Users can go from Design to the Create phase for all message types. (#1699) * Create - Flow testing: The properties that start with “emagiz.dsh“ are provided with a value automatically in the background. * Deploy - Releases: In case of activating a new release and there is trouble at the step of creating new certificates, the previous valid certificate will be reused. ==== Bug fixes ==== * Create - Flow Designer: Users are correctly redirected to their request/response message based on the XSD they are selecting in the flow. (#1555) * Create - Transformation: Value mappings for a “string to enumeration” transformer are now visible after reopening the window. (#1715) * Create - System Message: The navigation from Create to Design has been fixed for event streaming.

This ensures that when you select a flow, the correct one opens as expected. * Deploy - Architecture: We have fixed a bug for DSH-enabled event streaming models, which may have prematurely lost read/write access to deleting topics if the topic was still in use in the active release. * Deploy - Releases: We have fixed a bug for DSH-event streaming-enabled models, where updating one flow connecting to the DSH event streaming broker would result in containers hosting other such flows to be redeployed unintentionally as well. * Deploy - Unused Properties: Users can select multiple properties across pages and delete the selections all at once. (#1730) * Manage - Topic Triggers: All DSH topics have topic triggers.

Key concepts == With cloud template, we mean: A Cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting, for instance) are available for your environment.

All changes can be handled with a single push of a button, but it may become harder to isolate the root cause when an issue occurs. So keep your Deploy Architecture as current as possible.{{/info}} * Duration of the upgrade ** A Cloud template upgrade will take between 5 and 15 minutes, depending on the size of the slot in terms of machines.

Regardless of the type of environment (Test, Acceptance, or Production) * Double lane Cloud template upgrades are non-service affecting. * Keep your Deploy architecture current - less risk of the impact of Cloud template upgrade issues. == 5.

The properties' history is on the Deploy phase's History page. Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966) Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.

Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913) Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973) Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero." Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.

The properties' history is on the Deploy phase's History page. * Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966) * Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.

The speed of creating the dialog to enter the component’s name is also improved. * Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913) * Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973) * Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero." * Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text. * Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839) * Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).

. (#983) Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979) Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown.

These changes can be applied to the environment or reverted. (#828) Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.

. (#983) * Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979) * Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown.

These changes can be applied to the environment or reverted. (#828) ** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release. ** Changes with a direct effect will not be listed (for example, restarting a machine).

It is still possible to provide a custom type. (#1711) Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708) Bug fixes Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320) Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534) Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571) Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668) Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059) Deploy - eMagiz Connector: Resolved the issue where, in some edge cases, downloading the latest release when staring the eMagiz Connector could lead to an error, preventing the connector from starting.

It is still possible to provide a custom type. (#1711) * Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708) ==== Bug fixes ==== * Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320) * Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534) * Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571) * Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668) * Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059) * Deploy - eMagiz Connector: Resolved the issue where, in some edge cases, downloading the latest release when staring the eMagiz Connector could lead to an error, preventing the connector from starting.

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

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