Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 282.1
edited by Carlijn Kokkeler
on 2023/12/04 15:08
Change comment: There is no comment for this version
To version 136.1
edited by Erik Bakker
on 2023/08/01 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +202 - New Equilibrium
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,66 +1,79 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
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 additional smaller feedback item coming from our hackathon efforts that are now released to you.
7 7  
8 -== **Alerts** ==
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, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
9 9  
10 -//__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
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. This to avoid mistakes when filling them in.
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, 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 a completely new release in Test and promote it to the Production environment.
12 12  
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 +{{info}}For more information please check out the following microlearnings:
15 15  
16 -== **Feedback Items** ==
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"]]
17 17  
18 -//__Container version overview__//
19 -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.
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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 manage graphs as we retrieve and show less fine-grained information when zooming out.
22 22  
23 -//__Unchanged containers__//
24 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
25 25  
26 -//__Rebuilding of images__//
27 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 +== **Feedback Items** ==
28 28  
31 +//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
32 +Without having edit 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 missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
29 29  
30 -== **Bug Fixes** ==
34 +//__Improved auditability on Deploy Architecture__//
35 +To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
37 +//__Test your own exported work__//
38 +We have now made it possible to test your own 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.
34 34  
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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}}
37 37  
38 -//__Store message merging__//
39 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
42 +//__Improved Audit Trail on several places__//
43 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
40 40  
41 -//__View all store items__//
42 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
45 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
46 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
43 43  
44 -//__Out of memory behavior__//
45 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
48 +== **Bug Fixes** ==
46 46  
47 -//__Max fetch size__//
48 -We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
49 -
50 +//__Avoid clicking on other components while deleting another__//
51 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
50 50  
53 +//__Improved validation feedback in migrating to the next-generation architecture__//
54 +We have improved the validation feedback when migrating to the next-generation architecture.
55 +
56 +//__Make sure that user credentials can be viewed with view rights__//
57 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
58 +
59 +//__Refresh behavior within the deployment plan is fixed__//
60 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
61 +
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
67 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
68 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
56 56  
57 57  == **Key takeaways** ==
58 58  
59 -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:
72 +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:
60 60  
61 61  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 65  * Check out the release notes [here]
66 66  * Start thinking about how the license tracker can aid your development
... ... @@ -73,12 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -~*~* Indicates a next-generation-architecture only feature.
77 -{{/info}}
78 -)))
79 -
80 -(((
81 -{{toc/}}
82 -)))
89 +~*~* Indicates a GEN3-only feature.
90 +{{/info}})))((({{toc/}}))){{/container}}
83 83  {{/container}}
84 -{{/container}}