Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
Change comment: There is no comment for this version
To version 527.1
edited by Carlijn Kokkeler
on 2024/05/21 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +221 - Swift Shift
Content
... ... @@ -3,80 +3,53 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Pop-up Improvements** ==
9 -//__Property releases__//
10 -When a new property release is created, this property release can now be viewed and deleted.
8 +== **Feedback Items** ==
9 +//__Q&A search__//
10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
12 +//__Event catalog__//
13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
13 13  
14 -//__Runtime deletion__//
15 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
16 16  
17 -//__Wiretap & debug error messages__//
18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
17 +//__Attribute placements__//
18 +Some improvements regarding the placement of attributes have been done:
19 +* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add new attribute.
20 +* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
21 +* 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.
19 19  
20 -//__Action messages__//
21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
22 22  
23 -== **Formatting & Alignments** ==
25 +//__Failover & grouping__//
26 +Some improvements regarding the widgets for failover and grouping have been done:
27 +* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 +* 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".
24 24  
25 -//__Input fields__//
26 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
27 27  
28 -//__UI improvements__//
29 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
30 30  
31 -//__Runtime overview image versions__//
32 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
33 -
34 -//__Component changes reversion__//
35 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
36 -
37 -//__State generation statistics__//
38 -The state generation graphs will now show the correct number of cache hits and misses.
39 -
40 -//__Queue browser timestamps__//
41 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
42 -
43 -//__Addition and deletion of internal recipients__//
44 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
45 -
46 -== **Feedback Items** ==
47 -
48 -//__Update flows__//
49 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
50 -
51 -//__Q&A forum search__//
52 -The option to search by pressing the Enter key has been added to the Q&A forum.
53 -
54 -//__Memory settings__//
55 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
56 -
57 -//__Runtime validation__//
58 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
59 -
60 -
61 61  == **Bug Fixes** ==
35 +//__XSD import__//
36 +When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
62 62  
63 -//__Removal of onramp__//
64 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
65 65  
66 -//__Runtime statistics details__//
67 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
40 +//__Container deletion__//
41 +The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
68 68  
69 -//__Deployment prechecks__//
70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
43 +//__Scope properties__//
44 +We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
71 71  
72 -
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
77 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
78 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
79 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
50 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
80 80  
81 81  == **Key Takeaways** ==
82 82  
... ... @@ -86,7 +86,7 @@
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 87  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 88  * Clear your browser cache (Ctrl + Shift + Del)
89 -* Check out the release notes [here]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
90 90  * Start thinking about how the license tracker can aid your development
91 91  * Start thinking about major, minor, and patch
92 92  * Keep making great integrations