Skip to Content

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 281.2
edited by Carlijn Kokkeler
on 2023/12/04 15:08
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +210 - Deployment Delights
Content
... ... @@ -3,50 +3,58 @@
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!** We have...
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.
8 +== **Alerts** ==
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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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.
16 +== **Feedback Items** ==
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
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 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
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]]
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
32 32  
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28 +
29 +
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]]
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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.
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
41 41  
38 +//__Store message merging__//
39 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40 +
41 +//__View all store items__//
42 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
43 +
44 +//__Out of memory behavior__//
45 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46 +
47 +//__Max fetch size__//
48 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
49 +
50 +
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"]]
55 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
48 48  
49 -== **Key Takeaways** ==
57 +== **Key takeaways** ==
50 50  
51 51  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
52 52  
... ... @@ -54,9 +54,10 @@
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"]]
65 +* 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
68 +* Upgrade to the latest build number
60 60  * Keep making great integrations
61 61  
62 62  Let's stay in touch and till next time!
... ... @@ -64,6 +64,7 @@
64 64  {{info}}
65 65  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  
76 +~*~* Indicates a next-generation-architecture only feature.
67 67  {{/info}}
68 68  )))
69 69