199 - Home Improvements

{{container layoutStyle="columns"}}(((

[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]

**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.

6

7

== **Next generation improvements and bug fixes** ==

8

9

//__Enhanced overview of the HTTP Statistics__//

10

As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.

11

12

//__Reason why runtime cannot start is now in the vast majority of cases reported back__//

13

In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.

14

15

{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}

16

17

//__Forced congestion control__//

18

To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.

19

20

21

//__Improved validation errors on the invalid configuration of HTTP outbound components__//

22

This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.

23

24

//__Improved migration behavior__//

25

This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:

26

A smoother migration of your JMS (and backup JMS) process.

27

Shortening of names that otherwise would be too long, additional feedback given to the user.

28

Feedback when the migration process is finished.

29

30

//__Additional checks when deploying__//

31

This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.

32

33

== **Store Improvements** ==

34

35

== **Event Streaming - Certificate Management** ==

36

37

== **Fancy Forum Answers** ==

38

39

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:

40

41

* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]

42

* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]

43

44

== **Key takeaways** ==

45

46

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:

47

48

* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]

49

* If you have feedback or ideas for us, talk to the Platypus

50

* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.

51

* Clear your browser cache (Ctrl + Shift + Del)

52

* Check out the release notes [here]

53

* Start thinking about how the license tracker can aid your development

54

* Start thinking about major, minor, and patch

55

* Upgrade to the latest build number

56

* Keep making great integrations

57

58

Let's stay in touch and till next time!

59

60

61

~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]

62

63

~*~* Indicates a GEN3-only feature.

64

{{/info}})))((({{toc/}}))){{/container}}

65

Wiki source code of 199 - Home Improvements

Navigation

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}(((
		3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
		4
		5	Hi there, eMagiz developers! In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
		6
		7	== Next generation improvements and bug fixes ==
		8
		9	//__Enhanced overview of the HTTP Statistics__//
		10	As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
		11
		12	//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
		13	In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
		14
		15	{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome\|\|target="blank"]]{{/info}}
		16
		17	//__Forced congestion control__//
		18	To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
		19
		20
		21	//__Improved validation errors on the invalid configuration of HTTP outbound components__//
		22	This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
		23
		24	//__Improved migration behavior__//
		25	This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
		26	A smoother migration of your JMS (and backup JMS) process.
		27	Shortening of names that otherwise would be too long, additional feedback given to the user.
		28	Feedback when the migration process is finished.
		29
		30	//__Additional checks when deploying__//
		31	This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
		32
		33	== Store Improvements ==
		34
		35	== Event Streaming - Certificate Management ==
		36
		37	== Fancy Forum Answers ==
		38
		39	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:
		40
		41	* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852\|\|target="blank"]]
		42	* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717\|\|target="blank"]]
		43
		44	== Key takeaways ==
		45
		46	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:
		47
		48	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		49	* If you have feedback or ideas for us, talk to the Platypus
		50	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
		51	* Clear your browser cache (Ctrl + Shift + Del)
		52	* Check out the release notes [here]
		53	* Start thinking about how the license tracker can aid your development
		54	* Start thinking about major, minor, and patch
		55	* Upgrade to the latest build number
		56	* Keep making great integrations
		57
		58	Let's stay in touch and till next time!
		59
		60	{{info}}
		61	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		62
		63	~~ Indicates a GEN3-only feature.
		64	{{/info}})))((({{toc/}}))){{/container}}
		65	{{/container}}