Wiki source code of 242 - Stability Score
Last modified by Erik Bakker on 2025/04/08 16:42
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!** In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our most significant change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better control their resource management within the cloud models. In addition, we released various improvements in the platform regarding clarity and stability. | ||
| 7 | |||
| 8 | == **New Cloud Template** == | ||
| 9 | |||
| 10 | As of this release, we have implemented a feature allowing cloud models to better control resource management within your production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. | ||
| 11 | |||
| 12 | {{info}}The following applies to this functionality: | ||
| 13 | * This is only released for models running in **our** cloud and on the **current-generation** architecture. | ||
| 14 | * The functionality will be made available as part of a new cloud template and can be updated via the default [[upgrade>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained||target="blank"]] functionality.{{/info}} | ||
| 15 | |||
| 16 | === **Minor Changes** === | ||
| 17 | |||
| 18 | //__Store usage overview__// | ||
| 19 | To improve our insights into the store's usage across models, we have introduced a new overview, accessible by users with Store privileges, to see where a certain store item is being used. | ||
| 20 | |||
| 21 | //__Softcrow eMagiz Connector__// | ||
| 22 | We have created an add-on for our eMagiz Connector as part of our softcrow procedure. | ||
| 23 | |||
| 24 | //__Adding/Removing Attributes - Easier Way__// | ||
| 25 | We have adapted the add attribute pop-up while designing message definitions in such a way that you can use this pop-up to quickly add **and remove** attributes as well as define on attribute level whether the attributes are optional or not. | ||
| 26 | |||
| 27 | [[image:Main.Images.Release Blog.WebHome@release-242-add-remove-attributes.png]] | ||
| 28 | |||
| 29 | == **Bug Fixes** == | ||
| 30 | //__Moving components in Create -> Transformations__// | ||
| 31 | We now allow the movement of aggregator components freely in the order of transformation components, especially in correlation with filter operations. | ||
| 32 | |||
| 33 | [[image:Main.Images.Release Blog.WebHome@release-242-moving-components.png]] | ||
| 34 | |||
| 35 | //__Removed joda.time mentions from help texts__// | ||
| 36 | Given that we do not support references to joda.time anymore since our release of our latest [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] (version 3.3.0) we have now also removed all references to this option in help texts across the platform. | ||
| 37 | |||
| 38 | //__Dropped support for HTML in alerting emails__// | ||
| 39 | We have removed the possibility for our users to add any HTML code within any free text fields in our trigger overview for the current-generation architecture to avoid that this could potentially be used to send malicious content to the recipients of the email via our platform. | ||
| 40 | |||
| 41 | == **Fancy Forum Answers** == | ||
| 42 | |||
| 43 | As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: | ||
| 44 | |||
| 45 | * [[Blob Storage - 403 Server failed to authenticate the request>>https://my.emagiz.com/p/question/172825635704093317||target="blank"]] | ||
| 46 | |||
| 47 | == **Key Takeaways** == | ||
| 48 | |||
| 49 | Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: | ||
| 50 | |||
| 51 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 52 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 53 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 54 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 55 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.242 - Stability Score.WebHome||target="blank"]] | ||
| 56 | * Start thinking about how the license tracker can aid your development | ||
| 57 | * Start thinking about major, minor, and patch | ||
| 58 | * Keep making great integrations | ||
| 59 | |||
| 60 | Let's stay in touch and till next time! | ||
| 61 | |||
| 62 | {{info}} | ||
| 63 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 64 | |||
| 65 | {{/info}} | ||
| 66 | ))) | ||
| 67 | |||
| 68 | ((( | ||
| 69 | {{toc/}} | ||
| 70 | ))) | ||
| 71 | {{/container}} | ||
| 72 | {{/container}} |