Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+207 - Aligned State

Content

...	...	@@ -2,50 +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 done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
	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		-== **Release Date Change** ==
8		-As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	7	+== **State Generation** ==
9	9
10		-== **Deployment Plan** ==
	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.
11	11
12		-//__Improved deployment plan to make the process better and more predictable__//
13		-The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
	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)
	22	+* 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`.
	23	+* Added support for `#JsonPath` usage in SpEL expressions
14	14
15		-{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
16	16
17		-//__Editing release properties__//
18		-With this release, it will be possible to change the description of a property by editing the property.
	26	+== **Metrics Storage Duration** ==
	27	+
	28	+
	29	+
19	19
20		-//__Container memory settings__//
21		-A change in memory settings triggers redeployment of the container now.
22		-
23		-//__Properties tab__//
24		-We have removed the deprecated tab Properties in the Deploy phase.
25		-
26		-//__Cleanup old images__//
27		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
28		-
29		-//__Performance improvements for loading releases__//
30		-Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
31		-
32		-== **Store Improvements** ==
33		-
34		-//__Message definition elements order__//
35		-We fixed an issue that the order of message definition elements was changed after being imported.
36		-
37		-//__Importing a store item with synchronous message definitions__//
38		-We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
39		-
40		-//__Importing store items containing static copies__//
41		-We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
42		-
43		-//__Importing store content__//
44		-We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
45		-
46		-//__Store disclaimer__//
47		-Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
48		-
49	49	== **Feedback Items** ==
50	50
51	51	//__Alerting manual pause__//