Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 138.1
edited by Carlijn Kokkeler
on 2023/10/23 16:42
Change comment: There is no comment for this version
To version 249.1
edited by Carlijn Kokkeler
on 2024/05/21 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +221 - Swift Shift
Content
... ... @@ -1,46 +1,18 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +In the last sprint cycle, we have worked on .
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
4 4  
5 5  =====New features=====
6 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
7 7  
8 -=====Minor changes=====
7 +* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324)
8 +* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 +* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151)
10 +* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151)
11 +* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151)
12 +* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group.
13 +* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
9 9  
10 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
14 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
23 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
27 -
28 -
29 -
30 30  ====Bug fixes====
31 -
32 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
33 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
35 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
38 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
41 -
42 -
43 -
44 -=====Infra and image changes=====
45 -
46 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
16 +* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140)
17 +* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053)
18 +* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.