241 - Wild West

(((

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

**Hi there, eMagiz developers!** In this release, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new runtime image containing a much-needed improvement regarding deployment executions when working with state generation and code mappings, along with various improvements in our underlying code.

7

8

== **Property Comparison** ==

9

10

As of this release, you can compare properties between two releases via the compare properties functionality in Deploy -> Releases. This allows you to quickly compare which property values have been changed, altered, or deleted. On top of that, it provides information on which user executed this change so you can confirm with that person whether that is expected. Note that this functionality only works on **activated** releases, so it should be utilized from an audit perspective and **cannot** be used to validate property changes in preparation before activating the release.

11

12

{{info}}The following applies to this functionality:

13

* The functionality only works for releases created **after** this release.

14

* The more properties a model has, the longer it takes to show results.

15

* The functionality only works on **activated** releases.{{/info}}

16

17

== **New Runtime Image** ==

18

19

As announced on our [[status page>>https://status.emagiz.com/incidents/b84m6sv0n6n8||target="blank"]], we will release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] as part of this release. The main changes within the runtime image are

20

21

* Updated our Java runtime version from Java 17.0.10 to Java 17.0.13. This is primarily a security update involving cipher suite changes, as outlined in the remarks below.

22

* Updated Spring boot from version 3.2.2 to 3.4.1.

23

* We have marked the OAuth2 grant type ‘password’ as deprecated, which will be removed with the introduction of OAuth 2.1. It can still be used, but a warning will be given when configured. To prevent the need to migrate to another OAuth grant type in the future, we encourage you to switch to one of the other grant types.

24

* The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed.

25

26

Please find out more [[here>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]].

27

28

{{warning}}We recommend evaluating custom Groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.**{{/warning}}

29

30

== **Hackathon Efforts** ==

31

32

=== Minor Changes ===

33

34

//__Improved copy behavior for Q&A questions__//

35

To simplify the act of copying a link to a question, we have slightly altered the current functionality so that you can copy the link to your clipboard with a single click. We have also ensured that the UI is consistent across the platform.

36

37

[[image:Main.Images.Release Blog.WebHome@release-241-qa-copy-button.png]]

38

39

//__Removal of remark field when creating a new integration__//

40

We have removed a free text field called "Remarks" when creating a new integration, as that field was rarely used and was not visible across the platform after you had pressed "Save."

41

42

//__Display name character limitations better shown__//

43

In eMagiz we have set limits on the allowed length of various input fields. One example is the display name given to components within the Flow Designer. We now inform the user of how many characters (out of the 64 characters maximum) can be defined by the user when the user exceeds the limit of 64 characters.

44

45

//__Improved information when deleting message defintions from Create -> Resources__//

46

We now inform the user which specific transformation, including relevant metadata, prevents you from deleting a message definition under Create -> Resources.

47

48

[[image:Main.Images.Release Blog.WebHome@release-241-delete-behavior-create-resources.png]]

=== Bug Fixes ===

//__Emptying the name of a system in Capture is not allowed anymore__//

53

We have ensured that you can no longer empty the system name of an existing system in Capture and subsequently store the system.

54

55

//__Improved resilience when creating and editing message definitions__//

56

Various changes have been introduced on the message definition level that improves the platform's resilience in cases where users become so enthusiastic that they click many times to execute the same action. With this, we prevent a user from causing duplicates or errors when executing the same action repeatedly.

57

58

//__Custom examples for request messages are shown in Swagger__//

59

With this release, we also ensure that when you define a custom example message in your Swagger UI, it will be displayed for both request and response messages.

60

61

//__Improved input validation on multiple runtime option__//

62

You will see a nice validation error when activating the "multiple runtimes" option without filling in a value in the "multiple runtimes" input field.

63

64

//__Correct naming of browser page for Create -> Components__//

65

We have correctly named the browser page when navigating Create -> Components.

66

67

//__User confirmation improvements when deleting wiretaps__//

68

We have improved the necessary user confirmation when deleting wiretaps within the Flow Designer. This way, you only need to confirm the deletion once instead of twice.

69

70

//__Property description updates__//

71

You can now update the property description even when an existing property description is already present. Do note that the property description is related to the property placeholder and is, therefore, the same across environments.

72

73

//__Naming improvement auto-created components API Gateway__//

74

When adding a new API Gateway passthrough operation to your Create phase, we now have a new default name given to the "REST Template" support object that aligns with other components in the flow.

75

76

//__Queue Browser - Switch environment__//

77

When switching between environments A (i.e., Test) and B (i.e., Acceptance), the queue browser overview is refreshed correctly, so we show the correct information, avoiding confusion.

78

79

== **Minor Changes** ==

80

81

//__Disallow use of hyphens in technical names across the platform__//

82

For new systems, message types, machines, tenants, and models, hyphens are no longer allowed in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.

83

84

//__Deployment Plan improvements - Execution__//

85

We have improved the stability of the deployment plan execution for all models running on the current-generation architecture.

86

87

== **Bug Fixes** ==

88

//__Loading bar addition when adding a system__//

89

We have added a loading bar when a user adds a system. This indicates to the user that the action is being handled, and as a result, there is no need to click again.

90

91

//__Create -> Add Integrations improvements__//

92

With this release, we bring two improvements to the removal functionality under Create -> Add Integrations.

93

94

* Users can untransfer a flow even when there is a property attached to the flow.

95

* When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.

96

97

//__Environment Template improvement__//

98

We fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.

99

100

== **Fancy Forum Answers** ==

101

102

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:

103

104

* [[SFTP: "Failed to obtained pooled item | Failed to create SFTP session" - too many sessions>>https://my.emagiz.com/p/question/172825635704080533||target="blank"]]

105

106

== **Key Takeaways** ==

107

108

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:

109

110

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

111

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

112

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

113

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

114

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

115

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

116

* Start thinking about major, minor, and patch

117

* Keep making great integrations

118

119

Let's stay in touch and till next time!

120

121

122

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

)))

(((

)))

Wiki source code of 241 - Wild West

Navigation

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, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new runtime image containing a much-needed improvement regarding deployment executions when working with state generation and code mappings, along with various improvements in our underlying code.
		7
		8	== Property Comparison ==
		9
		10	As of this release, you can compare properties between two releases via the compare properties functionality in Deploy -> Releases. This allows you to quickly compare which property values have been changed, altered, or deleted. On top of that, it provides information on which user executed this change so you can confirm with that person whether that is expected. Note that this functionality only works on activated releases, so it should be utilized from an audit perspective and cannot be used to validate property changes in preparation before activating the release.
		11
		12	{{info}}The following applies to this functionality:
		13	* The functionality only works for releases created after this release.
		14	* The more properties a model has, the longer it takes to show results.
		15	* The functionality only works on activated releases.{{/info}}
		16
		17	== New Runtime Image ==
		18
		19	As announced on our [[status page>>https://status.emagiz.com/incidents/b84m6sv0n6n8\|\|target="blank"]], we will release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome\|\|target="blank"]] as part of this release. The main changes within the runtime image are
		20
		21	* Updated our Java runtime version from Java 17.0.10 to Java 17.0.13. This is primarily a security update involving cipher suite changes, as outlined in the remarks below.
		22	* Updated Spring boot from version 3.2.2 to 3.4.1.
		23	* We have marked the OAuth2 grant type ‘password’ as deprecated, which will be removed with the introduction of OAuth 2.1. It can still be used, but a warning will be given when configured. To prevent the need to migrate to another OAuth grant type in the future, we encourage you to switch to one of the other grant types.
		24	* The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed.
		25
		26	Please find out more [[here>>doc:Main.Release Information.Runtime Images.V330.WebHome\|\|target="blank"]].
		27
		28	{{warning}}We recommend evaluating custom Groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.**{{/warning}}
		29
		30	== Hackathon Efforts ==
		31
		32	=== Minor Changes ===
		33
		34	//__Improved copy behavior for Q&A questions__//
		35	To simplify the act of copying a link to a question, we have slightly altered the current functionality so that you can copy the link to your clipboard with a single click. We have also ensured that the UI is consistent across the platform.
		36
		37	[[image:Main.Images.Release Blog.WebHome@release-241-qa-copy-button.png]]
		38
		39	//__Removal of remark field when creating a new integration__//
		40	We have removed a free text field called "Remarks" when creating a new integration, as that field was rarely used and was not visible across the platform after you had pressed "Save."
		41
		42	//__Display name character limitations better shown__//
		43	In eMagiz we have set limits on the allowed length of various input fields. One example is the display name given to components within the Flow Designer. We now inform the user of how many characters (out of the 64 characters maximum) can be defined by the user when the user exceeds the limit of 64 characters.
		44
		45	//__Improved information when deleting message defintions from Create -> Resources__//
		46	We now inform the user which specific transformation, including relevant metadata, prevents you from deleting a message definition under Create -> Resources.
		47
		48	[[image:Main.Images.Release Blog.WebHome@release-241-delete-behavior-create-resources.png]]
		49
		50	=== Bug Fixes ===
		51
		52	//__Emptying the name of a system in Capture is not allowed anymore__//
		53	We have ensured that you can no longer empty the system name of an existing system in Capture and subsequently store the system.
		54
		55	//__Improved resilience when creating and editing message definitions__//
		56	Various changes have been introduced on the message definition level that improves the platform's resilience in cases where users become so enthusiastic that they click many times to execute the same action. With this, we prevent a user from causing duplicates or errors when executing the same action repeatedly.
		57
		58	//__Custom examples for request messages are shown in Swagger__//
		59	With this release, we also ensure that when you define a custom example message in your Swagger UI, it will be displayed for both request and response messages.
		60
		61	//__Improved input validation on multiple runtime option__//
		62	You will see a nice validation error when activating the "multiple runtimes" option without filling in a value in the "multiple runtimes" input field.
		63
		64	//__Correct naming of browser page for Create -> Components__//
		65	We have correctly named the browser page when navigating Create -> Components.
		66
		67	//__User confirmation improvements when deleting wiretaps__//
		68	We have improved the necessary user confirmation when deleting wiretaps within the Flow Designer. This way, you only need to confirm the deletion once instead of twice.
		69
		70	//__Property description updates__//
		71	You can now update the property description even when an existing property description is already present. Do note that the property description is related to the property placeholder and is, therefore, the same across environments.
		72
		73	//__Naming improvement auto-created components API Gateway__//
		74	When adding a new API Gateway passthrough operation to your Create phase, we now have a new default name given to the "REST Template" support object that aligns with other components in the flow.
		75
		76	//__Queue Browser - Switch environment__//
		77	When switching between environments A (i.e., Test) and B (i.e., Acceptance), the queue browser overview is refreshed correctly, so we show the correct information, avoiding confusion.
		78
		79	== Minor Changes ==
		80
		81	//__Disallow use of hyphens in technical names across the platform__//
		82	For new systems, message types, machines, tenants, and models, hyphens are no longer allowed in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
		83
		84	//__Deployment Plan improvements - Execution__//
		85	We have improved the stability of the deployment plan execution for all models running on the current-generation architecture.
		86
		87	== Bug Fixes ==
		88	//__Loading bar addition when adding a system__//
		89	We have added a loading bar when a user adds a system. This indicates to the user that the action is being handled, and as a result, there is no need to click again.
		90
		91	//__Create -> Add Integrations improvements__//
		92	With this release, we bring two improvements to the removal functionality under Create -> Add Integrations.
		93
		94	* Users can untransfer a flow even when there is a property attached to the flow.
		95	* When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
		96
		97	//__Environment Template improvement__//
		98	We fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
		99
		100	== Fancy Forum Answers ==
		101
		102	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:
		103
		104	* [[SFTP: "Failed to obtained pooled item \| Failed to create SFTP session" - too many sessions>>https://my.emagiz.com/p/question/172825635704080533\|\|target="blank"]]
		105
		106	== Key Takeaways ==
		107
		108	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:
		109
		110	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		111	* If you have feedback or ideas for us, talk to the Platypus
		112	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
		113	* Clear your browser cache (Ctrl + Shift + Del)
		114	* Check out the release notes [[here>>doc:Main.Release Information.Portal.241 - Wild West.WebHome\|\|target="blank"]]
		115	* Start thinking about how the license tracker can aid your development
		116	* Start thinking about major, minor, and patch
		117	* Keep making great integrations
		118
		119	Let's stay in touch and till next time!
		120
		121	{{info}}
		122	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
		123
		124	{{/info}}
		125	)))
		126
		127	(((
		128	{{toc/}}
		129	)))
		130	{{/container}}
		131	{{/container}}