Search: "deployment plan"

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"]]. ====Bug Fixes==== * Error messages with a lengthy message history will also be displayed. * Error messages with a stack trace larger than 32kb will also be displayed. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====Bug fixes==== * When using a SOAP outbound gateway with a custom SSL web service message sender, using key- and truststores, the truststores were not correctly used in the network communication, resulting in exceptions with ‘certificate_required’. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====Bug fixes==== * Externally uploaded JAR files were not loaded by the runtime, causing constructs where this was used, such as for providing database drivers or custom libraries that are used in Groovy scripts to throw an exception on startup. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====Bug fixes==== * The JMS server could fail to startup when migrating from the Spring 5 to the Spring 6 runtime in case a queue existed that at one point was auto-created, but no longer had a matching address setting. )))((({{toc/}}))){{/container}} {{/container}}

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"]]. ====Minor changes==== * Tracing errors in flow testing has been improved.

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.

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"]]. ====Bug fixes==== * SFTP session factories did not close their connection after it was complete.

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"]]. ====Bug fixes==== * We improved the out of memory behavior of next generation architecture runtimes.

//__Make preparation step in deployment plan visible__// For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan. {{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} //__3rd generation runtime debugger feedback__// We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.

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.