Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 525.1
edited by Carlijn Kokkeler
on 2024/05/21 11:43
Change comment: There is no comment for this version
To version 291.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
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,52 +3,62 @@
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, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
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’ 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 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
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 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
26 +//__Improved deployment process__//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
33 33  
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31 +
34 34  == **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.
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
39 39  
40 -//__XSD import__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
37 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
42 42  
40 +//__View all store items__//
41 +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.
42 +
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
45 +
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
48 +
43 43  == **Fancy Forum Answers** ==
44 44  
45 45  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:
46 46  
47 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
48 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
49 49  
50 -== **Key Takeaways** ==
51 51  
60 +== **Key takeaways** ==
61 +
52 52  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:
53 53  
54 54  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -55,9 +55,10 @@
55 55  * If you have feedback or ideas for us, talk to the Platypus
56 56  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57 57  * Clear your browser cache (Ctrl + Shift + Del)
58 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
68 +* Check out the release notes [here]
59 59  * Start thinking about how the license tracker can aid your development
60 60  * Start thinking about major, minor, and patch
71 +* Upgrade to the latest build number
61 61  * Keep making great integrations
62 62  
63 63  Let's stay in touch and till next time!
... ... @@ -65,6 +65,7 @@
65 65  {{info}}
66 66  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
67 67  
79 +~*~* Indicates a next-generation-architecture only feature.
68 68  {{/info}}
69 69  )))
70 70