Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 275.1
edited by CarlijnKokkeler
on 2023/12/04 14:34
Change comment: There is no comment for this version
To version 526.1
edited by CarlijnKokkeler
on 2024/05/21 11:44
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,46 +3,54 @@
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** ==
9 -
10 -
11 -
12 -
13 -
14 14  == **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.
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
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 18  
19 -//__Container version overview__//
20 -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.
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
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 23  
24 -//__Unchanged containers__//
25 -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 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
26 26  
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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".
29 29  
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
30 30  
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
33 +
31 31  == **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.
32 32  
33 -//__Runtime metrics processing__//
34 -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]]
35 35  
36 -//__Deployment plan__//
37 -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.
38 38  
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.
45 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
50 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
51 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
44 44  
45 -== **Key takeaways** ==
53 +== **Key Takeaways** ==
46 46  
47 47  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:
48 48  
... ... @@ -50,10 +50,9 @@
50 50  * If you have feedback or ideas for us, talk to the Platypus
51 51  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 52  * Clear your browser cache (Ctrl + Shift + Del)
53 -* Check out the release notes [here]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
54 54  * Start thinking about how the license tracker can aid your development
55 55  * Start thinking about major, minor, and patch
56 -* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,7 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a next-generation-architecture only feature.
65 65  {{/info}}
66 66  )))
67 67