235 - Last Log

(((

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

**Hi there, eMagiz developers!** In this release, our new log alerting will be available! Please find out more about it [[here>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome||target="blank"]]. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).

7

8

{{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}

9

10

== **Feedback Items** ==

11

//__Log alerting__//

12

We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.

13

14

15

* **Please take into consideration the following migration actions**:

16

* All existing log message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.

17

* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:

18

** The ‘Description’ field has been replaced by the new ‘Instructions’ field (note: the 'Description' field no longer exists).

19

** The values of the old description field will be transferred into the instructions field

20

* Additionally, a new field, ‘Name’, has been introduced for identification purposes. The ‘Name’ field will be included in email notifications when a trigger is activated.

21

** This field will be automatically populated with a default name (e.g., "Log Trigger 1").

22

** **Users are advised to review and update these names to appropriately reflect each trigger's purpose.**

23

* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for **all** log types.

24

* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.

25

26

27

{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your log-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}

28

29

{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}

30

31

//__Tooltip alerting__//

32

We have improved the visibility of titles of larger columns in the new Alerting page.

33

34

//__SMB improvements__//

35

Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:

36

* It is now possible to add a local filter to the SMB inbound channel adapter.

37

* It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adapter, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.

38

39

[[image:Main.Images.Release Blog.WebHome@release-235-local-filter.png]]

40

[[image:Main.Images.Release Blog.WebHome@release-235-request-handler.png]]

41

42

//__Mendix connector support__//

43

We no longer support our legacy Mendix connector (< version 4.x).

44

45

== **Bug Fixes** ==

46

//__Resource buttons__//

47

The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode.

48

49

[[image:Main.Images.Release Blog.WebHome@release-235-resources.png]]

50

51

//__Performance improvement__//

52

The performance of selecting a runtime when editing properties in Deploy has been improved.

53

54

//__Flowtest errors__//

55

The error that is sometimes thrown while switching between traces in flowtester is fixed.

56

57

== **Fancy Forum Answers** ==

58

59

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:

60

61

* [[Access a WSDL in your browser>>https://my.emagiz.com/p/question/172825635704016587||target="blank"]]

62

* [[Operation is not present in wsdl>>https://my.emagiz.com/p/question/172825635704016691||target="blank"]]

63

* [[Code Mappings on Gen3 error during restart ISPN000323>>https://my.emagiz.com/p/question/172825635704016854||target="blank"]]

64

* [[How to add Basic Authentication on a soap webservice?>>https://my.emagiz.com/p/question/172825635704017021||target="blank"]]

65

66

== **Key Takeaways** ==

67

68

Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:

69

70

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

71

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

72

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

73

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

74

* Check out the release notes [[here>>doc:Main.Release Information.Portal.235 - Last Log.WebHome||target="blank"]]

75

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

76

* Start thinking about major, minor, and patch

77

* Keep making great integrations

78

79

Let's stay in touch and till next time!

80

81

82

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

)))

(((

)))

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}
		3	(((
		4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
		5
		6	Hi there, eMagiz developers! In this release, our new log alerting will be available! Please find out more about it [[here>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome\|\|target="blank"]]. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
		7
		8	{{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
		9
		10	== Feedback Items ==
		11	//__Log alerting__//
		12	We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3\|\|target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
		13
		14	{{info}}
		15	* Please take into consideration the following migration actions:
		16	* All existing log message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3\|\|target="blank"]] architecture models will be automatically migrated to the new alerting feature.
		17	* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
		18	** The ‘Description’ field has been replaced by the new ‘Instructions’ field (note: the 'Description' field no longer exists).
		19	** The values of the old description field will be transferred into the instructions field
		20	* Additionally, a new field, ‘Name’, has been introduced for identification purposes. The ‘Name’ field will be included in email notifications when a trigger is activated.
		21	** This field will be automatically populated with a default name (e.g., "Log Trigger 1").
		22	Users are advised to review and update these names to appropriately reflect each trigger's purpose.**
		23	* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for all log types.
		24	* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.
		25	{{/info}}
		26
		27	{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your log-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
		28
		29	{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-log-alerting.WebHome\|\|target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
		30
		31	//__Tooltip alerting__//
		32	We have improved the visibility of titles of larger columns in the new Alerting page.
		33
		34	//__SMB improvements__//
		35	Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:
		36	* It is now possible to add a local filter to the SMB inbound channel adapter.
		37	* It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adapter, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.
		38
		39	[[image:Main.Images.Release Blog.WebHome@release-235-local-filter.png]]
		40	[[image:Main.Images.Release Blog.WebHome@release-235-request-handler.png]]
		41
		42	//__Mendix connector support__//
		43	We no longer support our legacy Mendix connector (< version 4.x).
		44
		45	== Bug Fixes ==
		46	//__Resource buttons__//
		47	The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode.
		48
		49	[[image:Main.Images.Release Blog.WebHome@release-235-resources.png]]
		50
		51	//__Performance improvement__//
		52	The performance of selecting a runtime when editing properties in Deploy has been improved.
		53
		54	//__Flowtest errors__//
		55	The error that is sometimes thrown while switching between traces in flowtester is fixed.
		56
		57	== Fancy Forum Answers ==
		58
		59	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:
		60
		61	* [[Access a WSDL in your browser>>https://my.emagiz.com/p/question/172825635704016587\|\|target="blank"]]
		62	* [[Operation is not present in wsdl>>https://my.emagiz.com/p/question/172825635704016691\|\|target="blank"]]
		63	* [[Code Mappings on Gen3 error during restart ISPN000323>>https://my.emagiz.com/p/question/172825635704016854\|\|target="blank"]]
		64	* [[How to add Basic Authentication on a soap webservice?>>https://my.emagiz.com/p/question/172825635704017021\|\|target="blank"]]
		65
		66	== Key Takeaways ==
		67
		68	Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
		69
		70	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		71	* If you have feedback or ideas for us, talk to the Platypus
		72	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
		73	* Clear your browser cache (Ctrl + Shift + Del)
		74	* Check out the release notes [[here>>doc:Main.Release Information.Portal.235 - Last Log.WebHome\|\|target="blank"]]
		75	* Start thinking about how the license tracker can aid your development
		76	* Start thinking about major, minor, and patch
		77	* Keep making great integrations
		78
		79	Let's stay in touch and till next time!
		80
		81	{{info}}
		82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		83
		84	{{/info}}
		85	)))
		86
		87	(((
		88	{{toc/}}
		89	)))
		90	{{/container}}
		91	{{/container}}

Wiki source code of 235 - Last Log