Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-186 - Daemon Switch
	1	+207 - Aligned State

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -2,137 +2,108 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have hit the ground running in this quarter by not only focusing on larger features but also spend a substantial chunk of time on focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to a first set of models. So let us dive into all we have to offer this time!
	5	+**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
6	6
7		-== **New monitoring stack** ==
	7	+== **State Generation** ==
8	8
9		-This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of what these changes entail please check out the following microlearnings.
	9	+//__New components__//
	10	+The following components have been added:
	11	+* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
	12	+* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
	13	+* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
	14	+* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
	15	+* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
10	10
11		-* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
12		-* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
13		-* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]]
14		-* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]]
	17	+//__SpEL functions & JSON__//
	18	+Added SpEL functions for:
	19	+* Encoding & decoding Base64, Hex and hmac.
	20	+* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
	21	+* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
15	15
16		-{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter please contact us at productmanagement@emagiz.com to discuss the possibilities{{/info}}
	23	+Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
17	17
18		-== **Transformation Improvements** ==
	25	+Added support for `#JsonPath` usage in SpEL expressions.
19	19
20		-//__Toggle between Design and Create__//
21		-This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design.
	27	+//__New image version 2.0.0__//
	28	+The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
22	22
23		-//__Improved Transformation options for booleans__//
24		-On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks.
	30	+//__Component pages__//
	31	+Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
25	25
26		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
27	27
28		-== **Feedback items ** ==
	34	+== **Metrics Storage Duration** ==
	35	+Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
29	29
30		-Apart from the key updates around functionality, we have also solved other feedback items.
	37	+[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
31	31
32		-//__Correctly define the size of a cloud slot when creating it for the first time__//
33		-Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted.
	39	+== **Feedback Items** ==
34	34
35		-//__Updated infographic Capture__//
36		-As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
	41	+//__Alerting manual pause__//
	42	+A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
37	37
38		-//__Updated error feedback in Design__//
39		-Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown.
	44	+//__Ordering of graphs in Manage__//
	45	+The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
40	40
41		-//__Improved styling of Topic Storage in Design Architecture__//
42		-When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone.
	47	+//__UTC times in Grafana panels__//
	48	+All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
43	43
44		-//__Improved styling of error feedback on User Management in Deploy__//
45		-With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
	50	+//__Update flow designer version__//
	51	+The framework used in the flow designer has been updated, improving performance.
46	46
47		-//__Show only the ten latest flow versions when selecting a flow version in a Release__//
48		-To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
	53	+//__Carwash track TLS versions in logging__//
	54	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
49	49
50		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
	56	+//__Moving channels in the flow designer__//
	57	+Moving already attached channels in the flow designer has been made sligthly easier.
51	51
52		-//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__//
53		-Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification.
	59	+//__Topic sizes description change__//
	60	+In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
54	54
55		-//__Clear API Gateway System message__//
56		-With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level.
	62	+//__Password change notification__//
	63	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
57	57
58		-//__Additional information in Property History__//
59		-To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes.
	65	+//__Password comparison__//
	66	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
60	60
61		-//__Save Tag when ready__//
62		-With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model.
	68	+//__Inactive user alerting__//
	69	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
63	63
64		-//__View deployment step information when having view rights__//
65		-With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment.
	71	+//__Alphabetical sorting on user level in HTTP statistics__//
	72	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
66	66
67		-//__Validating external recipients in notification settings__//
68		-Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values.
69	69
70		-//__Automatically link enumeration list to attribute__//
71		-When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually.
72		-
73		-//__Approve and go to environment__//
74		-With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment.
75		-
76		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
77		-
78		-//__Remove irrelevant information on a runtime in Design Architecture__//
79		-We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below.
80		-
81		-[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
82		-
83		-//__Add question about message redelivery in Capture__//
84		-When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution.
85		-
86		-//__Prevent pressing “Apply to environment” multiple times leading to conflicts__//
87		-With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period.
88		-
89		-//__Add “State” to the topic details in Deploy Architecture__//
90		-Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched.
91		-
92		-//__Improved stability of logging on the Gen3 Architecture__//
93		-With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally.
94		-
95	95	== **Bug Fixes** ==
96	96
97		-//__Various updates when importing store items in Design including a transformation__//
98		-With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
	77	+//__Flow designer styling__//
	78	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
99	99
100		-//__Opening flow testing widget in specific circumstances was not working__//
101		-With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.”
	80	+//__Partial search for messages__//
	81	+It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
102	102
103		-//__Improved styling when adding a large message to a flow test__//
104		-With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message.
	83	+//__Disk usage after cloud template update__//
	84	+In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
105	105
106		-//__Errors on the UI do not keep following me__//
107		-Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete.
	86	+//__Error handling migration__//
	87	+If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
108	108
109		-//__Navigating back to the transformation in Create works again__//
110		-With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see.
111		-
112		-//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__//
113		-With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz.
114		-
115		-//__Selecting tags when drawing a line in Capture__//
116		-We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture.
117		-
118		-//__Remove invalid selection when configuring a cron trigger via the tooling__//
119		-With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution.
120		-
121	121	== **Fancy Forum Answers** ==
122	122
123		-As always, a gentle reminder to all 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:
	91	+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:
124	124
125		-* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
126		-* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
127		-* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
	93	+* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
	94	+* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
	95	+* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
	96	+* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
	97	+* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
128	128
	99	+
129	129	== **Key takeaways** ==
130	130
131		-Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	102	+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:
132	132
133		-* If you have questions surrounding our Program Increment Planning, please get in touch with
	104	+* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
134	134	* If you have feedback or ideas for us, talk to the Platypus
135		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	106	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
136	136	* Clear your browser cache (Ctrl + Shift + Del)
137	137	* Check out the release notes [here]
138	138	* Start thinking about how the license tracker can aid your development
...	...	@@ -143,8 +143,8 @@
143	143	Let's stay in touch and till next time!
144	144
145	145	{{info}}
146		-~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	117	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
147	147
148		-~*~* Indicates a GEN3-only feature.
	119	+~*~* Indicates a next-generation-architecture only feature.
149	149	{{/info}})))((({{toc/}}))){{/container}}
150	150	{{/container}}