Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 412.1
edited by Erik Bakker
on 2024/03/11 14:48
Change comment: There is no comment for this version
To version 192.1
edited by CarlijnKokkeler
on 2023/10/23 15:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,98 +1,104 @@
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 -
6 -**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
7 7  
8 -== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
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.
9 9  
10 -Placeholder for info from Bas
7 +== **State Generation** ==
11 11  
12 -{{info}}Text{{/info}}
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 -== **Announcement - Spring 6** ==
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 -Placeholder for info from Jelle
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 -{{warning}}Text{{/warning}}
25 +Added support for `#JsonPath` usage in SpEL expressions.
19 19  
20 -== ** Updated release functionality - Infra flow selection** ==
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.
21 21  
22 -This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
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.
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25 25  
26 -When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
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 +
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
39 +== **Feedback Items** ==
29 29  
30 -On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
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.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
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).
33 33  
34 -== ** Updated deploy functionality on-premise - Multiple environments selection** ==
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.
35 35  
36 -{{warning}}The following is only applicable under the following conditions:
37 - * Windows 2022 server
38 - * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
50 +//__Update flow designer version__//
51 +The framework used in the flow designer has been updated, improving performance.
39 39  
40 -When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
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.
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
56 +//__Moving channels in the flow designer__//
57 +Moving already attached channels in the flow designer has been made sligthly easier.
43 43  
44 -== **Feedback Items** ==
45 -//__Easier component selection in flow designer__//
46 -The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
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.
47 47  
48 -//__Improved handling of optionality in JSON on lists__//
49 -Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
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.
50 50  
51 -//__Loading bar when searching for log entries__//
52 -To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
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.
53 53  
54 -//__Improved feedback when deleting elements from Capture__//
55 -To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes.
68 +//__Inactive user alerting__//
69 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
56 56  
57 -//__Enhanced filter options in Manage__//
58 -With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
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.
59 59  
60 -//__Copy property names from Create__//
61 -This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
62 62  
63 -//__Improved feedback during migration to the current-runtime architecture__//
64 -We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
65 -
66 -//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
67 -We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
68 -
69 -//__Cron trigger validation__//
70 -We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
71 -
72 72  == **Bug Fixes** ==
73 -//__Queue name validation__//
74 -The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
75 75  
76 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
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.
77 77  
78 -//__Removal of onramp__//
79 -An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
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".
80 80  
81 -//__eMagiz login__//
82 -In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
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.
83 83  
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.
88 +
84 84  == **Fancy Forum Answers** ==
85 85  
86 86  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:
87 87  
88 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
89 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
90 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
91 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
92 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||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"]]
93 93  
94 -== **Key Takeaways** ==
95 95  
100 +== **Key takeaways** ==
101 +
96 96  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:
97 97  
98 98  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -102,6 +102,7 @@
102 102  * Check out the release notes [here]
103 103  * Start thinking about how the license tracker can aid your development
104 104  * Start thinking about major, minor, and patch
111 +* Upgrade to the latest build number
105 105  * Keep making great integrations
106 106  
107 107  Let's stay in touch and till next time!
... ... @@ -109,11 +109,6 @@
109 109  {{info}}
110 110  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111 111  
112 -{{/info}}
113 -)))
114 -
115 -(((
116 -{{toc/}}
117 -)))
119 +~*~* Indicates a next-generation-architecture only feature.
120 +{{/info}})))((({{toc/}}))){{/container}}
118 118  {{/container}}
119 -{{/container}}