Search: "deployment plan"

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.

In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work. Bug fixes Create - Flow Designer: We applied a new settings for the jms flow where the jms flow will try to shrink the journal files to 50 so it does not end up with a high amount of jms files which take too long to read.

In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work. ====Bug fixes==== * Create - Flow Designer: We applied a new settings for the jms flow where the jms flow will try to shrink the journal files to 50 so it does not end up with a high amount of jms files which take too long to read.

When you have made your decision, and assuming that your machines are already deployed and running, then you can move to the other page discussed in the next section. === 3.3 Deployment Plan === If this is the first time that you configure your failover setup, then the next step in Deploy is to check your Deployment Plan.

[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-balance-failover.png]] To make sure that this functionality works correctly, then this step should be placed at the end of your deployment plan (i.e., after the deployment of all runtimes).

[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-deployment-plan.png]] === 3.4 Deploy Release === Once you have configured your Deployment Plan, then it is time to create a new release for your updated flows in the Deploy>Release page.

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====New features==== * Added SpEL functions for: ** Encoding & decoding Base64, Hex and hmac. ** Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond). ** Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser). * Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily.

//__Refresh behavior within the deployment plan is fixed__// This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Bug fixes Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.

====Bug fixes==== * Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes. * Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed. * Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.

. (#958) Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982) Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990) Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972) Manage - Manage Dashboards: The screen loading speed is significantly improved for all models.

. (#982) * Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990) * Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972) * Manage - Manage Dashboards: The screen loading speed is significantly improved for all models.

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.

Deployment is done through the deployment plan 4. On premise runtime deployment through the eMagiz portal (after installing the control agent) eliminating the need to locally install runtimes ====Runtime specific updates==== 1.

. * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms === **Improvements** === * Performance Deployment plan When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU.