Changes for page 207 - Aligned State

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+203 - Fast Paced

Content

...	...	@@ -2,67 +2,32 @@
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 processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
6	6
7		-== **"Live" mode on flow testing** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
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	+== **Feedback Items** ==
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.
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
14	14
15		-Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
	18	+== **Bug Fixes** ==
16	16
17		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
	20	+//__Ensure no flow can be in a release twice__//
	21	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
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}}
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
22	22
23		-== **3rd generation improvements** ==
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.
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.
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.
33		-
34		-== **Feedback items ** ==
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.
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.
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.
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.
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"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
66	66
67	67	== **Key takeaways** ==
68	68
...	...	@@ -83,6 +83,6 @@
83	83	{{info}}
84	84	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
85	85
86		-~*~* Indicates a GEN3-only feature.
	51	+~*~* Indicates a next-generation-architecture only feature.
87	87	{{/info}})))((({{toc/}}))){{/container}}
88	88	{{/container}}