Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 785.1
edited by Carlijn Kokkeler
on 2024/11/18 11:56
Change comment: There is no comment for this version
To version 758.1
edited by Erik Bakker
on 2024/10/21 16:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +232 - Bug Busters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,27 +3,66 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
6 +**Hi there, eMagiz developers!** We did a hackathon again so we have a lot of bug fixes! The visibility of several buttons has been improved, search functionalities have been improved, and pop-ups have been corrected. Find out all below!
7 7  
8 8  == **Feedback Items** ==
9 -//__Error alerting__//
10 -Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
9 +//__Property name__//
10 +When creating a new property name for a new property value, it will automatically be selected for the new property value.
11 11  
12 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
12 +[[image:Main.Images.Release Blog.WebHome@release-232-propery-name.png]]
13 +
14 +== **Bug Fixes** ==
15 +//__Hidden Explore__//
16 +The 'Explore' button will no longer be hidden if there are no results when searching on a queue name in the queue browser.
17 +
18 +[[image:Main.Images.Release Blog.WebHome@release-232-explore-button.png]]
13 13  
14 -{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
20 +//__Delete container__//
21 +The 'Delete' button in the Containers overview is no longer visible for users without the required permissions.
15 15  
16 -{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
23 +[[image:Main.Images.Release Blog.WebHome@release-232-delete-container.png]]
17 17  
25 +//__Technical names__//
26 +It is no longer possible anymore to create machines with the same technical name.
27 +
28 +//__Failover systems__//
29 +When enabling or disabling our failover feature for a system, its connector container will no longer be moved to another machine if not required.
30 +
31 +//__Deploy architecture changes__//
32 +The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed.
33 +
34 +//__Code mappings search__//
35 +When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated. This has been fixed.
36 +
37 +[[image:Main.Images.Release Blog.WebHome@release-232-code-mappings.png]]
38 +
39 +//__Source filters__//
40 +Source filters will now display the attribute filter statement correctly.
18 18  
19 -== **Bug Fixes** ==
42 +[[image:Main.Images.Release Blog.WebHome@release-232-source-filters.png]]
20 20  
44 +//__Deploy rights__//
45 +We updated the user rights in a model such that in order to deploy a release in Deploy, you should have both edit rights in Deploy and Manage.
21 21  
47 +//__Zoom tooltip__//
48 +The tooltip in the Flow Designer now displays zoom in/out correctly.
49 +
50 +//__Conditional visibility__//
51 +The conditional visiblity of filtering operations of SMB, SFTP & FTP outbound gateways when using the 'remove' and 'get' operations has been improved.
52 +
53 +[[image:Main.Images.Release Blog.WebHome@release-232-conditional-filtering.png]]
54 +
55 +//__Landscape order across phases__//
56 +Integrations ans systems are now sorted in the same way across all phases.
57 +
58 +//__Datamodel relations__//
59 +When editing a relation in a datamodel, you are now prevented from breaking the relation.
60 +
22 22  == **Fancy Forum Answers** ==
23 23  
24 24  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:
25 25  
26 -* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
65 +* [[H2 Database on ESF Across Multiple Runtimes>>https://my.emagiz.com/p/question/172825635703991017||target="blank"]]
27 27  
28 28  == **Key Takeaways** ==
29 29  
... ... @@ -33,7 +33,7 @@
33 33  * If you have feedback or ideas for us, talk to the Platypus
34 34  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
35 35  * Clear your browser cache (Ctrl + Shift + Del)
36 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
75 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.232 - Bug Busters.WebHome||target="blank"]]
37 37  * Start thinking about how the license tracker can aid your development
38 38  * Start thinking about major, minor, and patch
39 39  * Keep making great integrations