Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 596.1
edited by Carlijn Kokkeler
on 2024/07/16 12:24
Change comment: There is no comment for this version
To version 526.1
edited by Carlijn Kokkeler
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 -225 - TBD
1 +221 - Swift Shift
Content
... ... @@ -3,56 +3,52 @@
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!**
7 7  
8 -
9 9  == **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
9 +//__Q&A search__//
10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12 +//__Event catalog__//
13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
14 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
17 17  
18 -//__Design settings__//
19 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
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.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
22 22  
23 -//__Untested images__//
24 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
25 -
26 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
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".
27 27  
28 -//__Infinispan Cache Manager__//
29 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
30 -
31 -//__Infinispan Cache Manager error message__//
32 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
33 33  
34 -//__Flow bump__//
35 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
36 -
37 -IMAGE
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
38 38  
39 -//__Unused support objects__//
40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
43 -
44 -
45 45  == **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.
46 46  
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
47 47  
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.
48 48  
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.
49 49  
50 -
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||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"]]
56 56  
57 57  == **Key Takeaways** ==
58 58  
... ... @@ -62,7 +62,7 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 68  * Keep making great integrations