Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 45.1
edited by Erik Bakker
on 2022/11/21 12:00
Change comment: There is no comment for this version
To version 185.1
edited by Carlijn Kokkeler
on 2023/10/23 14:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,72 +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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.
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 -== **Store - Next phase** ==
7 +== **State Generation** ==
8 8  
9 -This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
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.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
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
12 12  
13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
14 14  
15 -== **New eMagiz Mendix Connector** ==
26 +== **Metrics Storage Duration** ==
27 +
28 +
29 +
16 16  
17 -This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
31 +== **Feedback Items** ==
18 18  
19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
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.
20 20  
21 -== **Flow version restore** ~* ==
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).
22 22  
23 -On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
42 +//__Update flow designer version__//
43 +The framework used in the flow designer has been updated, improving performance.
26 26  
27 -{{warning}}Note that the following restrictions apply when restoring to a previous version:
28 - * Changes made on definition and transformation level are **not** restored
29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
31 - * Your restored flow version will **not** be automatically committed to Deploy{{/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.
32 32  
33 -== **Feedback items ** ==
48 +//__Moving channels in the flow designer__//
49 +Moving already attached channels in the flow designer has been made sligthly easier.
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
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.
36 36  
37 -//__Improved help texts Kafka component__//
38 -The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
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.
39 39  
40 -//__Improved warning message when Message redelivery cannot be adequately executed__//
41 -We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
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.
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
60 +//__Inactive user alerting__//
61 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
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.
47 47  
48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
49 49  
50 50  == **Bug Fixes** ==
51 51  
52 -//__Update Swagger File when changing the order of entities in gateway message__//
53 -In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
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.
54 54  
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 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||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"]]
63 63  
91 +
64 64  == **Key takeaways** ==
65 65  
66 -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:
67 67  
68 68  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69 69  * If you have feedback or ideas for us, talk to the Platypus
70 -* 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.
71 71  * Clear your browser cache (Ctrl + Shift + Del)
72 72  * Check out the release notes [here]
73 73  * Start thinking about how the license tracker can aid your development
... ... @@ -80,6 +80,6 @@
80 80  {{info}}
81 81  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82 82  
83 -~*~* Indicates a GEN3-only feature.
111 +~*~* Indicates a next-generation-architecture only feature.
84 84  {{/info}})))((({{toc/}}))){{/container}}
85 85  {{/container}}