Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00

From version 823.1
edited by Carlijn Kokkeler
on 2024/12/02 10:19
Change comment: There is no comment for this version
To version 765.1
edited by Carlijn Kokkeler
on 2024/11/04 10:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - Last Log
1 +233 - TBD
Content
... ... @@ -3,36 +3,66 @@
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 -{{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
9 -
10 10  == **Feedback Items** ==
11 -//__Log alerting__//
12 -We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
9 +//__Support object alert__//
10 +If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
13 13  
14 -{{info}}
15 -* **Please take into consideration the following migration actions**:
16 -* All existing log message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
17 -* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
18 -** The ‘Description’ field has been replaced by the new ‘Instructions’ field (note: the 'Description' field no longer exists).
19 -** The values of the old description field will be transferred into the instructions field
20 -* Additionally, a new field, ‘Name’, has been introduced for identification purposes. The ‘Name’ field will be included in email notifications when a trigger is activated.
21 -** This field will be automatically populated with a default name (e.g., "Log Trigger 1").
22 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose.**
23 -* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for **all** log types.
24 -* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.
25 -{{/info}}
12 +[[image:Main.Images.Release Blog.WebHome@release-233-support-object-alert.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]]
26 26  
20 +//__Delete container__//
21 +The 'Delete' button in the Containers overview is no longer visible for users without the required permissions.
27 27  
28 -== **Bug Fixes** ==
23 +[[image:Main.Images.Release Blog.WebHome@release-232-delete-container.png]]
29 29  
25 +//__Technical names__//
26 +It is no longer possible anymore to create machines with the same technical name.
30 30  
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.
41 +
42 +[[image:Main.Images.Release Blog.WebHome@release-232-source-filters.png]]
43 +
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.
46 +
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 and 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 +
31 31  == **Fancy Forum Answers** ==
32 32  
33 33  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:
34 34  
35 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
65 +* [[H2 Database on ESF Across Multiple Runtimes>>https://my.emagiz.com/p/question/172825635703991017||target="blank"]]
36 36  
37 37  == **Key Takeaways** ==
38 38  
... ... @@ -42,7 +42,7 @@
42 42  * If you have feedback or ideas for us, talk to the Platypus
43 43  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44 44  * Clear your browser cache (Ctrl + Shift + Del)
45 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
75 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.232 - Bug Busters.WebHome||target="blank"]]
46 46  * Start thinking about how the license tracker can aid your development
47 47  * Start thinking about major, minor, and patch
48 48  * Keep making great integrations