Search: "deployment plan"

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. 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.

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. * Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. * 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.

Minor Changes Deploy - Releases: Improved performance for deploying releases using the deployment plan. Capture - Requirements Designer: The requirements designer got a visual refresh.

. ==== Minor Changes ==== * Deploy - Releases: Improved performance for deploying releases using the deployment plan. * Capture - Requirements Designer: The requirements designer got a visual refresh.

For this fix, a new runtime image has been released. Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)

For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. * Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315) * Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287) * Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122) * Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)

Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model.

. * Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) * Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model. * Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310) * Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture.

. (#1423) Deploy - Architecture: The helptext of volume mappings has been improved. (#1405) Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

. (#1405) * Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan. * Deploy - History: We added logging for when properties are deleted from the unused properties screen. (#1428) * Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview.

. (#572) When a cloud slot change is pending, you will be notified. (#606) Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

. (#606) * Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) * Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]. == **Bug Fixes** == //__Queues with illegal characters__// Existing queues with illegal characters will not generate errors anymore.

Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more here. Minor changes Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.

Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].

Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.

. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment.

//__Failover__// Several improvements for our failover functionality have been done: * We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.