Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 816.1
edited by Carlijn Kokkeler
on 2024/12/02 09:51
Change comment: There is no comment for this version
To version 847.1
edited by Erik Bakker
on 2025/01/27 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - TBD
1 +237 - Fabulous Flow
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Release Blogs.WebHome
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,59 +3,68 @@
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 focused on improving the flow back and forth between the various phases in eMagiz by solving several feedback items related to Design, Create, and Design and the interaction between these three phases. We have also improved the memory calculation for all runtimes running on a Windows machine. Moreover, we have updated the styling of our graphs in the Manage phase.
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}}
8 +== **Runtime Memory Update (Windows Machines Only)** ==
9 +
10 +As part of this release, we will update the underlying memory calculations for all runtimes running on a Windows machine. Consequently, these runtimes will have a slightly increased memory footprint on your machine.
9 9  
10 -== **Feedback Items** ==
11 -//__Error alerting__//
12 -Error alerting 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"]] several 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.
13 -
14 14  {{info}}
15 -Please take into consideration the following migration actions:
16 -* All existing error 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., "Error Trigger 1").
22 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
23 -* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
24 -** "Check header" is disabled.
25 -** "Check error message" is enabled.
26 -** The "Error message contains" field includes only a single character.
27 -* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
13 +* **Please take into consideration the following**:
14 +* The new memory settings will take effect on the **first** deployment you will execute after **this** release.
15 +** When executing this deployment, you will see a pop-up notifying you of the **new** used memory. Here, you can also see whether the new **used** memory exceeds the available memory.
16 +* Should the **used** memory increase the available memory (as determined by eMagiz), you can manually override this setting in Design -> Architecture under the "Edit machine" option by filling in the memory field.
28 28  
29 -{{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}}
18 +[[image:Main.Images.Release Blog.WebHome@release-237-manual-override-memory-on-prem.png]]
30 30  
31 -{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
20 +* Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
21 +{{/info}}
22 +
23 +== **Certificate Update** ==
24 +
25 +As announced on our [[status page>>https://status.emagiz.com/incidents/4wb8tt5x9v95||target="blank"]], we will update our emagizcloud certificate as part of this release. Should you encounter any problems, please get in touch with our [[support department>>mailto:support@emagiz.com]]!
32 32  
33 -//__Attribute selection__//
34 -When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
27 +== **Minor changes** ==
28 +//__SMB component improvements__//
29 +Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter.
37 37  
38 -//__Runtime image__//
39 -We have removed some deprecated components from our runtime image.
40 -* TCP support object 'Byte array text length header (de)serializer'
41 -* Mikrotik service activator
31 +//__EDI Components - Styling Update__//
32 +The styling of the following components has been updated.
42 42  
43 -Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
34 +* XML to EDI transformer
35 +* EDI to XML transformer
36 +* XML to UN/EDIFACT transformer
37 +* UN/EDIFACT to XML transformer
38 +
39 +//__Manage Statistics UI Update__//
40 +We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
44 44  
45 -{{warning}}We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.
46 -* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
47 -* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
48 -* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
42 +[[image:Main.Images.Release Blog.WebHome@release-237-ui-changes-manage-statistics.png]]
49 49  
50 50  == **Bug Fixes** ==
51 -//__Failover container__//
52 -The failover container will now be shown correctly.
45 +//__Import from Store - Design__//
46 +The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. This is to avoid broken transformations within the Create phase of eMagiz.
53 53  
48 +//__Removing integrations from Create__//
49 +When the last integration is removed from a system in create, the container infra flows are also removed from the create phase release.
50 +
51 +//__Flow Test Logging - Navigation__//
52 +We have improved the navigation of the logging shown on the flow test level in Create.
53 +
54 +//__Create Phase - Synchronization process updated__//
55 +The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase.
56 +
57 +//__Update on search functionality in "Start/Stop flows" overview__//
58 +Searching in the start/stop flows overview and the queue browser can now be done from any page in the overviews.
59 +
60 +//__Windows line break fix__//
61 +If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.
62 +
54 54  == **Fancy Forum Answers** ==
55 55  
56 56  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:
57 57  
58 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
67 +* [[Issue with importing XSD into eMagiz, replacing '=ref' references>>https://my.emagiz.com/p/question/172825635704054981||target="blank"]]
59 59  
60 60  == **Key Takeaways** ==
61 61  
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
77 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.237 - Fabulous Flow.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Keep making great integrations