Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 93.1
edited by Erik Bakker
on 2023/03/14 08:28
Change comment: There is no comment for this version
To version 197.1
edited by Carlijn Kokkeler
on 2023/10/23 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Big Leap
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,73 +2,121 @@
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).
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.
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 -//__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.
25 +Added support for `#JsonPath` usage in SpEL expressions.
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.
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.
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.
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.
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.
33 +== **Metrics Storage Duration** ==
34 +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.
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.
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
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.
38 +== **Feedback Items** ==
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}}
40 +//__Import from store__//
41 +The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
37 37  
38 -== **Feedback items ** ==
43 +//__Save and cancel buttons placement__//
44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
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.
46 +//__User session times__//
47 +The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
42 42  
43 -//__User Roles are sorted alphabetically__//
44 -All user roles under User Management are now also sorted alphabetically.
49 +//__Cancel and next buttons order//
50 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
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.
52 +//__Data sink page__//
53 +The data sink page has been moved to the “Explore” tab.
48 48  
49 -== **Bug fixes ** ==
55 +//__Unused images removal__//
56 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
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.
58 +//__Flow Designer performance__//
59 +Performance improvements for the Flow Designer have been implemented.
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.
61 +//__Properties with special characters__//
62 +When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
56 56  
64 +//__Hidden flow fragements__//
65 +When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
66 +
67 +//__Resources disappearances__//
68 +Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
69 +
70 +//__Error channel for all inbounds__//
71 +If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
72 +We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
73 +
74 +//__Highlighting resources__//
75 +The performance of highlighting resources of selected components is improved in Read only mode.
76 +
77 +== **Bug Fixes** ==
78 +
79 +//__Topic and event-processor names__//
80 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
81 +
82 +//__System alignment__//
83 +The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
84 +
85 +//__Error checking__//
86 +Besides checking error header, the error trigger is now configured to check if an error message contains a term.
87 +
88 +//__Alerting__//
89 +For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
90 +For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
91 +The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
92 +
93 +//__Unused containers__//
94 +Containers are set inactive when they are unused and removed in Design.
95 +
96 +//__Error popups when promoting a release version__//
97 +We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
98 +
99 +//__Memory leak__//
100 +A memory leak when using gen 3 metrics has been fixed.
101 +
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"]]
106 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
107 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
108 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
109 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
110 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
64 64  
112 +
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:
115 +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.
119 +* 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.
132 +~*~* Indicates a next-generation-architecture only feature.
85 85  {{/info}})))((({{toc/}}))){{/container}}
86 86  {{/container}}