Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 93.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version
To version 235.1
edited by Erik Bakker
on 2025/03/24 09:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +241 - Wild West
Content
... ... @@ -1,27 +1,31 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
1 +In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and 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.200 - Uncharted Territories.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 -=====Minor changes=====
5 +====Minor Changes====
6 6  
7 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 -** For Kafka templates:
10 -*** Batch size: 200000
11 -*** Linger: 300
12 -** For Kafka message listener containers
13 -*** Fetch min. amount: 100000
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 **no longer allowed** in the technical name. The technical name can only consist of lowercase 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 creation. 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.
14 14  
15 -{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
16 -
17 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 -* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 -* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
21 -
22 22  ====Bug fixes====
23 23  
24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
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)