Skip to Content

Changes for page 202 - New Equilibrium

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

Summary

Details

Page properties
Content
... ... @@ -2,17 +2,17 @@
2 2  {{container layoutStyle="columns"}}(((
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 additional smaller feedback item coming from our hackathon efforts that are now released to you.
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 6  
7 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:
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 9  
10 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.
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 14  
15 -{{info}}For more information please check out the following microlearnings:
15 +{{info}}For more information, please check out the following microlearnings:
16 16  
17 17  * [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 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"]]
... ... @@ -22,50 +22,45 @@
22 22  {{/info}}
23 23  
24 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.
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 26  
27 27  [[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
28 28  
29 29  == **Feedback Items** ==
30 30  
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.
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.
33 33  
34 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).
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).
36 36  
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.
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.
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}}
40 +{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals. fundamental-magic-store.WebHome||target="blank"]]{{/info}}
41 41  
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.
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.
44 44  
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.
47 -
48 48  == **Bug Fixes** ==
49 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.
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.
52 52  
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.
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.
55 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.
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.
58 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.
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.
61 61  
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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:
65 65  
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"]]
63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
69 69  
70 70  == **Key takeaways** ==
71 71