Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 574.21
edited by Danniar Firdausy
on 2024/07/01 15:17
Change comment: There is no comment for this version
To version 550.1
edited by Carlijn Kokkeler
on 2024/06/05 09:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -224 - Summer Sonata
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,46 +3,45 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
6 +**Hi there, eMagiz developers!** This release, we have worked to allow cron triggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
7 7  
8 8  == **Feedback Items** ==
9 -//__Retention duration and bytes in Capture__//
10 -The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
9 +//__Design changes__//
10 +If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
11 11  
12 -//__Help text panel in Capture__//
13 -Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
14 -
15 -//__Property value page__//
16 -Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
19 -
20 20  == **Bug Fixes** ==
21 -//__Adding tags in Capture__//
22 -In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon.
15 +//__Cron triggers__//
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
25 25  
26 -//__External links__//
27 -Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab.
20 +//__Trigger activation__//
21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
28 28  
29 -//__Adding attributes for a message definition__//
30 -In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
31 31  
32 -//__View XSLT__//
33 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
34 34  
35 -//__Multipart/form-data HTTP request__//
36 -The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
37 37  
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33 +
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
36 +
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
38 +
38 38  == **Fancy Forum Answers** ==
39 39  
40 40  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:
41 41  
42 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
43 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
44 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
45 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
46 46  
47 47  == **Key Takeaways** ==
48 48  
... ... @@ -52,7 +52,7 @@
52 52  * If you have feedback or ideas for us, talk to the Platypus
53 53  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 54  * Clear your browser cache (Ctrl + Shift + Del)
55 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
56 56  * Start thinking about how the license tracker can aid your development
57 57  * Start thinking about major, minor, and patch
58 58  * Keep making great integrations