Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 139.1
edited by Erik Bakker
on 2023/08/01 14:28
Change comment: There is no comment for this version
To version 546.1
edited by CarlijnKokkeler
on 2024/06/03 13:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +222 - Flee Frustration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,79 +1,59 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
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!
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
9 -
10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 -* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12 -* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13 -* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
14 -
15 -{{info}}For more information, please check out the following microlearnings:
16 -
17 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
20 -
21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 -{{/info}}
23 -
24 -== ** Manage - Next generation graphs improvements ** ==
25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
26 -
27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
28 -
29 29  == **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.
30 30  
31 -//__Improved editability when testing in eMagiz without Edit rights in Create__//
32 -Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
33 33  
34 -//__Improved auditability on Deploy Architecture__//
35 -To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
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.
36 36  
37 -//__Test your own exported store content__//
38 -We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
39 39  
40 -{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
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.
41 41  
42 -//__Improved comparison of flows in the releases overview__//
43 -We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
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.
44 44  
45 -== **Bug Fixes** ==
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
46 46  
47 -//__Improved validation on XPath header enricher__//
48 -To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
49 49  
50 -//__Cancel behavior on flow testing property overview fixed__//
51 -We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
52 52  
53 -//__Cancel behavior on flow fragment level when exporting store content__//
54 -We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
55 55  
56 -//__Adding numbers on containers in Deploy Architecture__//
57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
58 58  
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||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"]]
64 64  
65 -== **Key takeaways** ==
46 +== **Key Takeaways** ==
66 66  
67 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
48 +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:
68 68  
69 69  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  * If you have feedback or ideas for us, talk to the Platypus
71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72 72  * Clear your browser cache (Ctrl + Shift + Del)
73 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
74 74  * Start thinking about how the license tracker can aid your development
75 75  * Start thinking about major, minor, and patch
76 -* Upgrade to the latest build number
77 77  * Keep making great integrations
78 78  
79 79  Let's stay in touch and till next time!
... ... @@ -81,6 +81,11 @@
81 81  {{info}}
82 82  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 83  
84 -~*~* Indicates a GEN3-only feature.
85 -{{/info}})))((({{toc/}}))){{/container}}
64 +{{/info}}
65 +)))
66 +
67 +(((
68 +{{toc/}}
69 +)))
86 86  {{/container}}
71 +{{/container}}