Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 523.1
edited by Carlijn Kokkeler
on 2024/05/21 11:29
Change comment: There is no comment for this version
To version 282.1
edited by Carlijn Kokkeler
on 2023/12/04 15:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +210 - Deployment Delights
Content
... ... @@ -3,42 +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 +== **Alerts** ==
9 +
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.
12 +
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 +
8 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.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.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.
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.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
24 24  
29 +
25 25  == **Bug Fixes** ==
26 -//__XSD import__//
27 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
28 28  
29 -[[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.
30 30  
31 -//__XSD import__//
32 -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.
33 33  
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 +
34 34  == **Fancy Forum Answers** ==
35 35  
36 36  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:
37 37  
38 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
39 -* [[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"]]
40 40  
41 -== **Key Takeaways** ==
57 +== **Key takeaways** ==
42 42  
43 43  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:
44 44  
... ... @@ -46,9 +46,10 @@
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 47  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
65 +* Check out the release notes [here]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
68 +* Upgrade to the latest build number
52 52  * Keep making great integrations
53 53  
54 54  Let's stay in touch and till next time!
... ... @@ -56,6 +56,7 @@
56 56  {{info}}
57 57  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
58 58  
76 +~*~* Indicates a next-generation-architecture only feature.
59 59  {{/info}}
60 60  )))
61 61