Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/04/18 13:05
From version 193.1
edited by Carlijn Kokkeler
on 2023/10/23 15:06
Change comment: There is no comment for this version
To version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +214 - System Symphony
Content
... ... @@ -1,104 +1,48 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
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 +**Hi there, eMagiz developers!** In this release, ...
6 6  
7 -== **State Generation** ==
8 -
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.
16 -
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 -
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`.
24 -
25 -Added support for `#JsonPath` usage in SpEL expressions.
26 -
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.
29 -
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.
32 -
33 -
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.
36 -
37 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
38 -
39 39  == **Feedback Items** ==
40 40  
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.
10 +//__Update flows__//
11 +Support for deploying to on premise Windows machines has been delivered.
43 43  
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).
13 +//__Image versions__//
14 +The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
46 46  
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.
16 +//__Adding multiple attributes__//
17 +It is now possible to add multiple existing attributes to an entity at once.
49 49  
50 -//__Update flow designer version__//
51 -The framework used in the flow designer has been updated, improving performance.
19 +//__Monitoring graphs__//
20 +The monitoring graphs can now show data up to the last 30 days.
52 52  
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.
55 -
56 -//__Moving channels in the flow designer__//
57 -Moving already attached channels in the flow designer has been made sligthly easier.
58 -
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.
61 -
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.
64 -
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.
67 -
68 -//__Inactive user alerting__//
69 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
70 -
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.
73 -
74 -
75 75  == **Bug Fixes** ==
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
76 76  
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.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
79 79  
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".
28 +//__Failover group refresh__//
29 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
82 82  
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.
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
85 85  
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.
33 +//__Resource paths__//
34 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
88 88  
89 89  == **Fancy Forum Answers** ==
90 90  
91 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:
92 92  
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"]]
40 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
41 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
42 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
98 98  
44 +== **Key Takeaways** ==
99 99  
100 -== **Key takeaways** ==
101 -
102 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:
103 103  
104 104  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -108,7 +108,6 @@
108 108  * Check out the release notes [here]
109 109  * Start thinking about how the license tracker can aid your development
110 110  * Start thinking about major, minor, and patch
111 -* Upgrade to the latest build number
112 112  * Keep making great integrations
113 113  
114 114  Let's stay in touch and till next time!
... ... @@ -116,6 +116,11 @@
116 116  {{info}}
117 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]]
118 118  
119 -~*~* Indicates a next-generation-architecture only feature.
120 -{{/info}})))((({{toc/}}))){{/container}}
62 +{{/info}}
63 +)))
64 +
65 +(((
66 +{{toc/}}
67 +)))
121 121  {{/container}}
69 +{{/container}}