Wiki source code of 264 - Strict Separation
Last modified by Erik Bakker on 2026/03/23 11:20
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform. Last but not least, we have an update on our support for the old eMagiz Mendix connector. | ||
| 7 | |||
| 8 | == **Old eMagiz Mendix Connector End-Of-Life** == | ||
| 9 | |||
| 10 | {{warning}}Over a **[[year>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]]** ago we launched our new eMagiz Connector. Although many of our customers have already migrated, not all have taken that step since. Given that we need to move people away from the old functionality, we are now officially announcing that the old eMagiz Mendix Connector is labeled end-of-life as of **September 1st, 2026**. | ||
| 11 | |||
| 12 | Customers who don't migrate before that deadline risk losing connectivity between their eMagiz model and their Mendix app(s). | ||
| 13 | |||
| 14 | If you have questions please get in touch with [[our support department>>mailto:support@emagiz.com]] {{/warning}} | ||
| 15 | |||
| 16 | == **New Environment Template** == | ||
| 17 | |||
| 18 | As of this release, we have implemented new functionality for single-lane customers on our current architecture. This is released as part of a new [[environment template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. | ||
| 19 | |||
| 20 | {{info}}The following applies to this functionality: | ||
| 21 | * This is only released for single-lane models running in **our** cloud and on the **current** architecture. | ||
| 22 | * Adding/moving/deleting containers from machines will now not replace the underlying instances. This was true only for single lanes. Doublelanes do not have this behaviour and are not affected.{{/info}} | ||
| 23 | |||
| 24 | == **New User Management**~* == | ||
| 25 | |||
| 26 | As part of our continuous efforts to improve the user experience within our platform, we have overhauled our user management functionality in Deploy once you run on our latest API Gateway **and/or** Event Streaming offering. Part of this change is that the currently known buttons "Transfer from Design" and "Apply to environment" have been merged into one single functionality. On top of that, we now allow users to select which changes they want to apply at any given time, providing additional flexibility. While doing so, we ensured that related changes that must be applied in parallel are selectable as a single option. With this enhancement, you can more easily and safely customize configurations per environment. | ||
| 27 | |||
| 28 | [[image:Main.Images.Release Blog.WebHome@release-264-deploy-user-management-cherry-picking.png]] | ||
| 29 | |||
| 30 | == **Minor Changes** == | ||
| 31 | |||
| 32 | //__Deploy - Properties__// | ||
| 33 | When saving a property, we now perform an optimization check. These improvements help reduce redundancy and keep property configurations cleaner and easier to maintain. | ||
| 34 | * If other properties share the same name and value, we will recommend grouping them to improve manageability. | ||
| 35 | * If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list. | ||
| 36 | * If none of the linked runtimes use the property, we recommend removing it. | ||
| 37 | |||
| 38 | [[image:Main.Images.Release Blog.WebHome@release-264-deploy-properties-save.png]] | ||
| 39 | |||
| 40 | //__Deploy - Releases__// | ||
| 41 | It is no longer possible to deploy a release that contains runtimes not linked to any flows in the architecture. | ||
| 42 | |||
| 43 | [[image:Main.Images.Release Blog.WebHome@release-264-deploy-empty-architecture.png]] | ||
| 44 | |||
| 45 | == **Bug Fixes** == | ||
| 46 | |||
| 47 | //__Design - Import XSD__// | ||
| 48 | Added the ability to import XSD files with an element of type 'all'. | ||
| 49 | |||
| 50 | //__Design - Swagger Configuration__// | ||
| 51 | Errors related to generating the Swagger UI in eMagiz have been resolved. Users will no longer encounter errors when generating JSON (new cases). | ||
| 52 | * Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. | ||
| 53 | * An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed. | ||
| 54 | * Schema validation has been extended to help prevent configuration mistakes. Existing errors related to referencing or schema definitions in the request/response body may still be present. However, when opening the edit page and clicking Save, the extended validation will be triggered. If the configuration results in an error, the validation will indicate this so it can be corrected before saving. | ||
| 55 | |||
| 56 | //__Create - Flow Testing__// | ||
| 57 | Users will see a pop-up error message about their broken test case and be asked to fix it. For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer. | ||
| 58 | |||
| 59 | //__Deploy - Deployment Plan Execution__// | ||
| 60 | A manual step in the deployment plan is shown only once during deployment. | ||
| 61 | |||
| 62 | //__Manage - Alerting - Log Trigger Configuration__// | ||
| 63 | Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be resent. | ||
| 64 | |||
| 65 | === **Remarks** === | ||
| 66 | |||
| 67 | * We have removed part of our platform's functionality as it was not used anymore. | ||
| 68 | * We have updated our help text widget to align it with the new UI options in Mendix. | ||
| 69 | |||
| 70 | == **Fancy Forum Answers** == | ||
| 71 | |||
| 72 | As always, this is a gentle reminder to ask questions via the Q&A forum in the eMagiz iPaaS portal. This way, we can all benefit from the community's knowledge. | ||
| 73 | |||
| 74 | == **Key Takeaways** == | ||
| 75 | |||
| 76 | Thanks to all who helped build the product and those who tested and provided feedback to improve it. To end this post, here are some key takeaways for you: | ||
| 77 | |||
| 78 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 79 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 80 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 81 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 82 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.264 - Strict Separation.WebHome||target="blank"]] | ||
| 83 | * Start thinking about how the license tracker can aid your development | ||
| 84 | * Start thinking about major, minor, and patch | ||
| 85 | * Keep making great integrations | ||
| 86 | |||
| 87 | Let's stay in touch and till next time! | ||
| 88 | |||
| 89 | {{info}} | ||
| 90 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 91 | |||
| 92 | {{/info}} | ||
| 93 | ))) | ||
| 94 | |||
| 95 | ((( | ||
| 96 | {{toc/}} | ||
| 97 | ))) | ||
| 98 | {{/container}} | ||
| 99 | {{/container}} |