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 130.1
edited by Erik Bakker
on 2023/07/17 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - The Last Post
1 +201 - Be Informed
Content
... ... @@ -2,67 +2,59 @@
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 worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you.
6 6  
7 -== **"Live" mode on flow testing** ==
7 +== **Announcement - Release Properties** ==
8 +As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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 +== ** Deploy Architecture - Apply To Environment improvements ** ==
11 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
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.
13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
15 +== ** Breadcrumb navigation in eMagiz ** ==
16 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
14 14  
15 -Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
20 +== **Feedback Items** ==
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}}
22 +//__Improved layout of catalog page in Design__//
23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
22 22  
23 -== **3rd generation improvements** ==
25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
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.
28 +//__Additional help texts on Design Architecture__//
29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
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.
31 +//__Improved Audit Trail on several places__//
32 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
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.
34 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
33 33  
34 -== **Feedback items ** ==
37 +== **Bug Fixes** ==
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.
39 +//__Avoid clicking on other components while deleting another__//
40 +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.
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.
42 +//__Improved validation feedback in migrating to the next-generation architecture__//
43 +We have improved the validation feedback when migrating to the next-generation architecture.
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.
45 +//__Make sure that user credentials can be viewed with view rights__//
46 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
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.
48 +//__Refresh behavior within the deployment plan is fixed__//
49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
47 47  
48 -== **Bug fixes ** ==
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.
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.
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"]]
55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
66 66  
67 67  == **Key takeaways** ==
68 68