Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 543.1
edited by Carlijn Kokkeler
on 2024/06/03 13:23
Change comment: There is no comment for this version
To version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +214 - System Symphony
Content
... ... @@ -3,45 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers 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 read about the details and the rest of our bug fixes!
6 +**Hi there, eMagiz developers!** In this release, ...
7 7  
8 8  == **Feedback Items** ==
9 -//__Cron triggers__//
10 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
10 +//__Update flows__//
11 +Support for deploying to on premise Windows machines has been delivered.
13 13  
14 -//__Design changes__//
15 -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.
13 +//__Image versions__//
14 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
16 +//__Adding multiple attributes__//
17 +It is now possible to add multiple existing attributes to an entity at once.
18 18  
19 +//__Monitoring graphs__//
20 +The monitoring graphs can now show data up to the last 30 days.
21 +
19 19  == **Bug Fixes** ==
20 -//__Trigger activation__//
21 -Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
22 22  
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.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
28 +//__Failover group refresh__//
29 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
27 27  
28 -//__Invalid memory configurations__//
29 -We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
30 30  
31 -//__Property value synchronization__//
32 -Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33 +//__Resource paths__//
34 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
33 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 -
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
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"]]
40 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
41 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
42 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
45 45  
46 46  == **Key Takeaways** ==
47 47  
... ... @@ -51,7 +51,7 @@
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 52  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
52 +* Check out the release notes [here]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
57 57  * Keep making great integrations