Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 236.1
edited by Erik Bakker
on 2025/03/24 14:42
on 2025/03/24 14:42
Change comment:
There is no comment for this version
To version 283.1
edited by Erik Bakker
on 2025/10/09 09:19
on 2025/10/09 09:19
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -24 1-WildWest1 +254 - Other One - Content
-
... ... @@ -1,35 +1,22 @@ 1 - In the lastsprint, wehave releasedalot interms ofusability improvementswhile workingwithinthe variousphasesofeMagiz andwhen deployingyourhard work to theenvironmentofyourchoice.As a result,wehaveaseriesofimprovementsandbug fixesforyou toenjoycomingoutofthehackathon.Ontopofthat, we releaseanew [[runtimeimage>>doc:Main.Release Information.RuntimeImages.V330.WebHome||target="blank"]]containinga much-needed improvement regarding deployment executions when working with stategeneration and code mappings on top of various improvementsin our underlyingcode.1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to update our underlying libraries. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.24 1-WildWest.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.254 - Other One.WebHome||target="blank"]]. 4 4 5 -====Minor Changes====5 +==== Minor changes ==== 6 6 7 -* Overall-Q&A Forum:When viewingaquestion, youcan noweasilycopy thelinktothequestiontoyourclipboard (#1471)8 -* Capture -Add Integration:Removedthe ‘remarks’fieldfromthe‘New Integration’screenin Capturebecausethisfieldwas notvisibleenoughin the rest oftheportal. (#1608)9 -* Capture /Design: For new systems, messagetypes, machines,tenants,and models, hyphens are **no longerallowed** inthe technical name. The technical name canonly consistof lowercase letters anddigitsand muststart with a letter.This alsoapplies to systems, message types, andtenants that have not yetbeentransferred fromdesigntocreation.The portal will give anerror message while transferring, andthehyphenhastobe removed manually.10 -* Create-Flowdesigner:Displaynamecharacterlimitationsarevisible in thevalidationfeedbackwhenadding newflow components(#1554)11 -* Create - Resources:When trying to deletea messagedefinition,the portalshowswhichtransformation(s)use this messagedefinition andshouldbedeleted aswell (#1616)12 -* Deploy - DeploymentPlanExecution:Wehaveimprovedthestabilityofthedeploymentplan procedure.7 +* General - Cloud Template: A new [[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of **cloud** we offer, is available that updates underlying libraries. 8 +* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400) 9 +* Capture - Settings - Integrations: Update column label to be more consistent (#1710) 10 +* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163) 11 +* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711) 12 +* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708) 13 13 14 -====Bug fixes==== 14 +==== Bug fixes ==== 15 15 16 -* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228) 17 -* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562) 18 -* Design - Message Definition: Two minor improvements are introduced: 19 -** The widget prevents users from adding the same message attribute within a message definition multiple times. 20 -** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame. 21 -* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597) 22 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513) 23 -* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590) 24 -* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned. 25 -* Create - Components: The browser page now displays the correct page title (#1509) 26 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549) 27 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560) 28 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526) 29 -* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly. 30 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408) 31 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550) 16 +* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320) 17 +* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534) 18 +* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571) 19 +* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668) 20 +* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059) 32 32 33 -====Remarks==== 34 34 35 -* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.