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.

Among these improvements, we have improved the performance of the deployment plan, and we made sure that you can analyze your XML validation errors from the Manage Dashboard once more.

==**Import definition with multiple namespace from the store**== On top of that, we have made it possible that when you import a message definition from the store that contains multiple namespaces (typical for EDI), eMagiz will automatically import all namespaces and link the namespaces to the correct entities and attributes of your system message. == **Bug fixes ** == See below for all bug fixes that are solved with this release //__Deployment plan improvements__// Previously, when you tried to execute your deployment plan (especially in larger environments), this could take a while. Both in terms of opening and managing the deployment plan. With this release, we have made structural changes that will improve the opening and execution of the deployment plan.

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

Message Redelivery - admin logs improved to better analyze issues when they occur Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed Bug fixes Deploy - Deployment plan. Performance of page to deploy a release increased significantly Store - Import resources was incorrectly done in specific cases, which is now fixed Store - Target namespace will be imported when importing an XML Message Definition Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.

. * Message Redelivery - admin logs improved to better analyze issues when they occur * Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality * Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed ====Bug fixes==== * Deploy - Deployment plan. Performance of page to deploy a release increased significantly * Store - Import resources was incorrectly done in specific cases, which is now fixed * Store - Target namespace will be imported when importing an XML Message Definition * Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. * Store - Importing items from the store sometimes resulted in invalid JMS connection factories.

. * 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.

. (#785) Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems.

Bug fixes Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly.

. (#785) * Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. * Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems.

====Bug fixes==== * Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) * Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) * Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly.

The complete list is as follows. * Deploy → Deployment Plan * Deploy → Properties → History * Deploy → User Management → Roles * Manage → Error Messages → Error Messages * Manage → Error Messages → Flows with Error Messages * Manage → Error Messages → Exceptions of Error Messages * Manage → Log Entries * Manage → Alerts * Manage → Triggers * Manage → Tags – Cant find (only Gen2) * Manage → Notifications * Manage → Notification Settings * Manage → Data Usage → History * Manage → Code mappings → All tabs == **Bug fixes ** == //__Loading problems of Deployment plan execution overview__// We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

Deploy - Check properties: Informative error messages when saving or creating a property. (#576) Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.

Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.

. (#576) * Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps. * Deploy - Architecture: Added reset feature for 3rd generation runtimes. ====Bug fixes==== * Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows. * Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances. * Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. * Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) * Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. * Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.

//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.

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.