Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Giant Leap
	1	+207 - Aligned State

Author

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

Content

...	...	@@ -2,73 +2,100 @@
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 worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
	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		-== **3rd generation improvements** ==
	7	+== **State Generation** ==
8	8
9		-//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	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		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
	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		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
	26	+== **Metrics Storage Duration** ==
	27	+
	28	+
	29	+
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
	31	+== **Feedback Items** ==
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
	33	+//__Alerting manual pause__//
	34	+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.
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
	36	+//__Ordering of graphs in Manage__//
	37	+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).
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
	39	+//__UTC times in Grafana panels__//
	40	+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.
32	32
33		-//__Improved help text for network volumes__//
34		-With this release, we have improved the help text that explains network volumes and how to use them within our solution.
	42	+//__Update flow designer version__//
	43	+The framework used in the flow designer has been updated, improving performance.
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	45	+//__Carwash track TLS versions in logging__//
	46	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
37	37
38		-== **Feedback items ** ==
	48	+//__Moving channels in the flow designer__//
	49	+Moving already attached channels in the flow designer has been made sligthly easier.
39	39
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
	51	+//__Topic sizes description change__//
	52	+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.
42	42
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
	54	+//__Password change notification__//
	55	+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.
45	45
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
	57	+//__Password comparison__//
	58	+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.
48	48
49		-== **Bug fixes ** ==
	60	+//__Inactive user alerting__//
	61	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
50	50
51		-//__Consolidated upgrade process cloud template__//
52		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
	63	+//__Alphabetical sorting on user level in HTTP statistics__//
	64	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
53	53
54		-//__Ensure users can deploy release on environments they have edit rights on__//
55		-Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
56	56
	67	+== **Bug Fixes** ==
	68	+
	69	+//__Flow designer styling__//
	70	+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.
	71	+
	72	+//__Partial search for messages__//
	73	+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".
	74	+
	75	+//__Disk usage after cloud template update__//
	76	+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.
	77	+
	78	+//__Error handling migration__//
	79	+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.
	80	+
57	57	== **Fancy Forum Answers** ==
58	58
59	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	60
61		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	85	+* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
	86	+* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
	87	+* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
	88	+* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
	89	+* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
64	64
	91	+
65	65	== **Key takeaways** ==
66	66
67		-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:
	94	+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:
68	68
69	69	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70	* If you have feedback or ideas for us, talk to the Platypus
71		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	98	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73	73	* Check out the release notes [here]
74	74	* Start thinking about how the license tracker can aid your development
...	...	@@ -81,6 +81,6 @@
81	81	{{info}}
82	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	83
84		-~*~* Indicates a GEN3-only feature.
	111	+~*~* Indicates a next-generation-architecture only feature.
85	85	{{/info}})))((({{toc/}}))){{/container}}
86	86	{{/container}}