Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 273.1
edited by CarlijnKokkeler
on 2023/12/04 14:28
Change comment: There is no comment for this version
To version 548.1
edited by CarlijnKokkeler
on 2024/06/03 16:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +222 - Flee Frustration
Content
... ... @@ -3,42 +3,47 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
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 find out about the details and the rest of our bug fixes!
7 7  
8 -== **Release Maintenance** ==
8 +== **Feedback Items** ==
9 +//__Cron triggers__//
10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
9 9  
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
10 10  
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.
11 11  
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
12 12  
19 +== **Bug Fixes** ==
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.
13 13  
14 -== **Feedback Items** ==
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.
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
18 18  
19 -//__Container version overview__//
20 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
23 23  
24 -//__Unchanged containers__//
25 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
26 26  
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
29 29  
30 - The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
31 -== **Bug Fixes** ==
32 -
33 -
34 -
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
40 40  
41 -== **Key takeaways** ==
46 +== **Key Takeaways** ==
42 42  
43 43  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
44 44  
... ... @@ -46,10 +46,9 @@
46 46  * If you have feedback or ideas for us, talk to the Platypus
47 47  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
48 48  * Clear your browser cache (Ctrl + Shift + Del)
49 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
50 50  * Start thinking about how the license tracker can aid your development
51 51  * Start thinking about major, minor, and patch
52 -* Upgrade to the latest build number
53 53  * Keep making great integrations
54 54  
55 55  Let's stay in touch and till next time!
... ... @@ -57,7 +57,6 @@
57 57  {{info}}
58 58  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  
60 -~*~* Indicates a next-generation-architecture only feature.
61 61  {{/info}}
62 62  )))
63 63