Search: "deploy architecture"

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

[[image:Main.Images.Release Blog.WebHome@release-231-manage-log-entries.png]] [[image:Main.Images.Release Blog.WebHome@release-231-flowtest-logs.png]] == **Bug Fixes** == //__Unused properties__// We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. //__Router deletion__// Router containers for failover that were deleted from the Deploy Architecture, are now cleaned up completely from the environment. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

//__Removed specific dependencies between Deploy Architecture and Releases__// In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.

This action can be found in Deploy Architecture, when right clicking on the white canvas. * We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture.

Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. == **Deploy Architecture - Apply To Environment improvements ** == As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture.

In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise. //__Empty runtime feedback when deploying a release (or setting the release as active)__// To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.

//__Deploy architecture changes__// The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed.

This allows you to transfer them from Design Architecture to Deploy Architecture to be utilized in future deployments. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

These prechecks can be executed via Deploy > Architecture. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.