Wiki source code of 249 - Amendment Avalanche
Last modified by Erik Bakker on 2025/07/14 08:06
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 is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform. | ||
| 7 | |||
| 8 | == **eMagiz Connector Image Update** == | ||
| 9 | |||
| 10 | The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH.. | ||
| 11 | |||
| 12 | {{info}}The following applies to this functionality: | ||
| 13 | * All users running the new eMagiz Connector will receive this update with their next release. | ||
| 14 | * If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you.{{/info}} | ||
| 15 | |||
| 16 | == **License Tracker - Additional Functionality** == | ||
| 17 | |||
| 18 | You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. | ||
| 19 | |||
| 20 | [[image:Main.Images.Release Blog.WebHome@release-249-license-tracker-additional-functionality.png]] | ||
| 21 | |||
| 22 | == **Minor Changes** == | ||
| 23 | |||
| 24 | //__Event Streaming - User Management__// | ||
| 25 | When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly. | ||
| 26 | |||
| 27 | {{info}}This functionality applies to both the old and new event broker.{{/info}} | ||
| 28 | |||
| 29 | //__Design - Message Definitions__// | ||
| 30 | The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. | ||
| 31 | |||
| 32 | [[image:Main.Images.Release Blog.WebHome@release-249-design-message-definition-description-overview.png]] | ||
| 33 | |||
| 34 | //__Circuit Breaker - Configuration__// | ||
| 35 | The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. | ||
| 36 | |||
| 37 | //__Create - Flow Testing__// | ||
| 38 | * Within the flow testing functionality we have made the following changes. | ||
| 39 | ** The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. | ||
| 40 | ** Each trace entry in the "Traces" overview now contains a timestamp. | ||
| 41 | |||
| 42 | //__Capture - Deletion__// | ||
| 43 | Deleting systems/integrations/tenants in Capture now shows a progress bar. | ||
| 44 | |||
| 45 | //__Deploy - Unused Properties__// | ||
| 46 | For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. | ||
| 47 | * Context is added to guide users through the following actions. | ||
| 48 | * Performance has improved significantly. As a result, the process takes less time than before. | ||
| 49 | |||
| 50 | //__Deploy - Releases__// | ||
| 51 | Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. | ||
| 52 | |||
| 53 | //__Deploy - Containers__// | ||
| 54 | Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. | ||
| 55 | |||
| 56 | == **Bug Fixes** == | ||
| 57 | |||
| 58 | //__Create - Add Integrations__// | ||
| 59 | We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases. | ||
| 60 | * Re-transferring integrations to Deploy. | ||
| 61 | * Untransfering the last integration of a system. | ||
| 62 | |||
| 63 | //__Create - Flow Designer__// | ||
| 64 | Within the flow designer we fixed the following bugs. | ||
| 65 | * The user can now completely read the alerts in the flow designer with a hover text. | ||
| 66 | * The "Allow empty array" checkbox in Create can now be used without it throwing an error. | ||
| 67 | * We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create. | ||
| 68 | |||
| 69 | //__Manage - Alerting__// | ||
| 70 | Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. | ||
| 71 | |||
| 72 | == **Fancy Forum Answers** == | ||
| 73 | |||
| 74 | As always, this is a gentle reminder to ask questions via the Q&A forum, which is available in the eMagiz iPaaS portal. This way, we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: | ||
| 75 | |||
| 76 | * [[Unable to resolve classes in groovy script>>https://my.emagiz.com/p/question/172825635704144577||target="blank"]] | ||
| 77 | * [[API Gateway: Recognizing an incoming user based on API key>>https://my.emagiz.com/p/question/172825635704157437||target="blank"]] | ||
| 78 | |||
| 79 | == **Key Takeaways** == | ||
| 80 | |||
| 81 | 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: | ||
| 82 | |||
| 83 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 84 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 85 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 86 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 87 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.249 - Amendment Avalanche.WebHome||target="blank"]] | ||
| 88 | * Start thinking about how the license tracker can aid your development | ||
| 89 | * Start thinking about major, minor, and patch | ||
| 90 | * Keep making great integrations | ||
| 91 | |||
| 92 | Let's stay in touch and till next time! | ||
| 93 | |||
| 94 | {{info}} | ||
| 95 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 96 | |||
| 97 | {{/info}} | ||
| 98 | ))) | ||
| 99 | |||
| 100 | ((( | ||
| 101 | {{toc/}} | ||
| 102 | ))) | ||
| 103 | {{/container}} | ||
| 104 | {{/container}} |