Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 110.1
edited by Erik Bakker
on 2023/05/05 10:25
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 -196 - The Last Post
1 +202 - New Equilibrium
Content
... ... @@ -2,67 +2,70 @@
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 work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
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.
6 6  
7 -== **"Live" mode on flow testing** ==
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 8  
9 -With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
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.
10 10  
11 -By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
15 +{{info}}For more information please check out the following microlearnings:
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
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"]]
14 14  
15 -Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.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.
18 18  
19 -{{info}}* The following restrictions apply for this functionality
20 - ** "Live" mode can only be activated on HTTP outbound gateway components
21 - ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/info}}
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
22 22  
23 -== **3rd generation improvements** ==
29 +== **Feedback Items** ==
24 24  
25 -//__Event Streaming statistics completion__//
26 -In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
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.
27 27  
28 -//__Deployments on next generation architecture__//
29 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
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).
30 30  
31 -//__Clean queues option__//
32 -This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
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.
33 33  
34 -== **Feedback items ** ==
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}}
35 35  
36 -//__On-premise containers are started upon slot wakeup__//
37 -With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
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.
38 38  
39 -//__Resource path is shown to the user__//
40 -You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
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.
41 41  
42 -//__Flow designer improvements__//
43 -With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
48 +== **Bug Fixes** ==
44 44  
45 -//__Improved capabilities of a company contact__//
46 -With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
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 47  
48 -== **Bug fixes ** ==
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.
49 49  
50 -//__Optional API parameters are handled correctly__//
51 -Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
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.
52 52  
53 -//__Without CDM rights nothing related to any data model can be edited anymore__//
54 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
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.
55 55  
56 -//__Improved sorting of Design and Deploy archticture__//
57 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
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 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
64 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
65 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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"]]
66 66  
67 67  == **Key takeaways** ==
68 68