Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01

From version 524.1
edited by Carlijn Kokkeler
on 2024/05/21 11:42
Change comment: There is no comment for this version
To version 363.1
edited by Carlijn Kokkeler
on 2024/01/29 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +213 - Joyful Journeys
Content
... ... @@ -3,48 +3,82 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved.
7 7  
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 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
9 +== **Pop-up Improvements** ==
10 +//__Property releases__//
11 +When a new property release is created, this property release can now be viewed and deleted.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
16 16  
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.
15 +//__Runtime deletion__//
16 +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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
18 +//__Wiretap & debug error messages__//
19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
24 24  
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".
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
31 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
32 32  
25 +== **Formatting & Alignments** ==
26 +
27 +//__Input fields__//
28 +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.
29 +
30 +//__UI improvements__//
31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
32 +
33 +//__Component changes reversion__//
34 +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.
35 +
36 +//__State generation statistics__//
37 +The state generation graphs will now show the correct number of cache hits and misses.
38 +
39 +//__Queue browser timestamps__//
40 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
41 +
42 +//__Addition and deletion of internal recipients__//
43 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
44 +
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 +//__Runtime overview image versions__//
61 +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.
62 +
33 33  == **Bug Fixes** ==
34 -//__XSD import__//
35 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
65 +//__Removal of onramp__//
66 +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 38  
39 -//__XSD import__//
40 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
68 +//__Runtime statistics details__//
69 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
41 41  
71 +//__Deployment prechecks__//
72 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
73 +
74 +
42 42  == **Fancy Forum Answers** ==
43 43  
44 44  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:
45 45  
46 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
47 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
79 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
80 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
81 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
48 48  
49 49  == **Key Takeaways** ==
50 50  
... ... @@ -54,7 +54,7 @@
54 54  * If you have feedback or ideas for us, talk to the Platypus
55 55  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
56 56  * Clear your browser cache (Ctrl + Shift + Del)
57 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
91 +* Check out the release notes [here]
58 58  * Start thinking about how the license tracker can aid your development
59 59  * Start thinking about major, minor, and patch
60 60  * Keep making great integrations