Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 280.1
edited by Carlijn Kokkeler
on 2023/12/04 15:00
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 -209 - Deployment Delights
1 +221 - Swift Shift
Content
... ... @@ -3,56 +3,55 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Release Maintenance** ==
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.
9 9  
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 10  
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
11 11  
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.
12 12  
23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
13 13  
14 -== **Feedback Items** ==
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".
15 15  
16 -//__Container version overview__//
17 -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.
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
20 20  
21 -//__Unchanged containers__//
22 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 -
24 -//__Rebuilding of images__//
25 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26 -
27 -
28 28  == **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.
29 29  
30 -//__Runtime metrics processing__//
31 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
32 32  
33 -//__Deployment plan__//
34 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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.
35 35  
36 -//__Store message merging__//
37 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
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.
38 38  
39 -//__View all store items__//
40 -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.
41 -
42 -//__Out of memory behavior__//
43 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 -
45 -//__Max fetch size__//
46 -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.
47 -
48 -
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
54 54  
55 -== **Key takeaways** ==
54 +== **Key Takeaways** ==
56 56  
57 57  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:
58 58  
... ... @@ -60,10 +60,9 @@
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 61  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 -* Check out the release notes [here]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
64 64  * Start thinking about how the license tracker can aid your development
65 65  * Start thinking about major, minor, and patch
66 -* Upgrade to the latest build number
67 67  * Keep making great integrations
68 68  
69 69  Let's stay in touch and till next time!
... ... @@ -71,7 +71,6 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 -~*~* Indicates a next-generation-architecture only feature.
75 75  {{/info}}
76 76  )))
77 77