Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 66.1
edited by Erik Bakker
on 2023/04/13 14:27
Change comment: There is no comment for this version
To version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +241 - Wild West
Content
... ... @@ -1,44 +1,31 @@
1 -As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
1 +In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +====Minor Changes====
6 6  
7 -We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
8 -When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties. These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered.
9 -If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
7 +* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8 +* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608)
9 +* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually.
10 +* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 +* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12 +* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
10 10  
11 -A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
12 -
13 -{{info}}Important to note is that
14 -* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
15 -* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
16 -* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
17 -* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
18 -
19 -=====Minor changes=====
20 -
21 -* General - Control Tower: Changed several generic triggers for more predictable behavior.
22 -* Administration - License Tracker: The license tracker has been updated for new license models and features.
23 -* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
24 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
25 -* Design - API Gateway: Default HTTP responses are generated automatically (#417)
26 -* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
27 -* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
28 -* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
29 -* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
30 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
31 -* Deploy - Architecture: Certificates only editable by system admin.
32 -* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
33 -
34 34  ====Bug fixes====
35 35  
36 -* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
37 -* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
38 -* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
39 -* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
40 -* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
41 -
42 -====Remarks====
43 -
44 -* Deploy - Releases: We removed the existing snapshots of release property values.
16 +* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17 +* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18 +* Design - Message Definition: small improvements are introduced:
19 +** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20 +** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21 +* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in 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 are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24 +* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
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 a property description in place. (#1526)
29 +* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now 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 that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)