Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
Change comment: There is no comment for this version
To version 194.1
edited by Carlijn Kokkeler
on 2023/10/23 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +207 - Aligned State
Content
... ... @@ -1,82 +1,103 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
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.
7 7  
8 -== **Pop-up Improvements** ==
9 -//__Property releases__//
10 -When a new property release is created, this property release can now be viewed and deleted.
7 +== **State Generation** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
13 13  
14 -//__Runtime deletion__//
15 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
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).
16 16  
17 -//__Wiretap & debug error messages__//
18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
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`.
19 19  
20 -//__Action messages__//
21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
25 +Added support for `#JsonPath` usage in SpEL expressions.
22 22  
23 -== **User Journey** ==
24 -//__Update flows__//
25 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
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.
26 26  
27 -//__Input fields__//
28 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
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.
29 29  
30 -//__UI improvements__//
31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
33 +== **Metrics Storage Duration** ==
34 +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.
32 32  
33 -//__Q&A forum search__//
34 -The option to search by pressing the Enter key has been added to the Q&A forum.
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
35 35  
36 36  == **Feedback Items** ==
37 37  
38 -//__Memory settings__//
39 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
40 +//__Alerting manual pause__//
41 +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.
40 40  
41 -//__Runtime validation__//
42 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
43 +//__Ordering of graphs in Manage__//
44 +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).
43 43  
44 -//__Runtime overview image versions__//
45 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
46 +//__UTC times in Grafana panels__//
47 +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.
46 46  
47 -== **Bug Fixes** ==
49 +//__Update flow designer version__//
50 +The framework used in the flow designer has been updated, improving performance.
48 48  
49 -//__Removal of onramp__//
50 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
52 +//__Carwash track TLS versions in logging__//
53 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
51 51  
52 -//__Component changes reversion__//
53 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
55 +//__Moving channels in the flow designer__//
56 +Moving already attached channels in the flow designer has been made sligthly easier.
54 54  
55 -//__State generation statistics__//
56 -The state generation graphs will now show the correct number of cache hits and misses.
58 +//__Topic sizes description change__//
59 +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.
57 57  
58 -//__Runtime statistics details__//
59 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
61 +//__Password change notification__//
62 +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.
60 60  
61 -//__Queue browser timestamps__//
62 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
64 +//__Password comparison__//
65 +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.
63 63  
64 -//__Deployment prechecks__//
65 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
67 +//__Inactive user alerting__//
68 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
66 66  
67 -//__Addition and deletion of internal recipients__//
68 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
70 +//__Alphabetical sorting on user level in HTTP statistics__//
71 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
69 69  
73 +
74 +== **Bug Fixes** ==
75 +
76 +//__Flow designer styling__//
77 +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.
78 +
79 +//__Partial search for messages__//
80 +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".
81 +
82 +//__Disk usage after cloud template update__//
83 +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.
84 +
85 +//__Error handling migration__//
86 +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.
87 +
70 70  == **Fancy Forum Answers** ==
71 71  
72 72  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:
73 73  
74 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
92 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
93 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
94 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
95 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
96 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
77 77  
78 -== **Key Takeaways** ==
79 79  
99 +== **Key takeaways** ==
100 +
80 80  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:
81 81  
82 82  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -86,6 +86,7 @@
86 86  * Check out the release notes [here]
87 87  * Start thinking about how the license tracker can aid your development
88 88  * Start thinking about major, minor, and patch
110 +* Upgrade to the latest build number
89 89  * Keep making great integrations
90 90  
91 91  Let's stay in touch and till next time!
... ... @@ -93,11 +93,6 @@
93 93  {{info}}
94 94  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95 95  
96 -{{/info}}
97 -)))
98 -
99 -(((
100 -{{toc/}}
101 -)))
118 +~*~* Indicates a next-generation-architecture only feature.
119 +{{/info}})))((({{toc/}}))){{/container}}
102 102  {{/container}}
103 -{{/container}}