Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 196.1
edited by Carlijn Kokkeler
on 2023/10/23 15:25
Change comment: There is no comment for this version
To version 476.1
edited by Carlijn Kokkeler
on 2024/04/23 13:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +219 - Creation Carousel
Content
... ... @@ -1,77 +1,58 @@
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!** This release, we introduce new environment templates for Docker single and double lane. Moreover, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
6 6  
7 -== **State Generation** ==
8 +== **Environment Template R13 Docker - Single Lane** ==
9 +This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]].
8 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.
11 +== **Environment Template R15 Docker - Double Lane** ==
12 +This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]].
16 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).
14 +== **Feedback Items** ==
22 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`.
16 +//__eMagiz Mendix connector__//
17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
24 24  
25 -Added support for `#JsonPath` usage in SpEL expressions.
19 +//__Improved OpenAPI import__//
20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
26 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.
22 +== **Bug Fixes** ==
23 +//__Error handling__//
24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
29 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.
26 +//__Volume mapping passwords__//
27 +Passwords for network volumes are hidden on the machine after deployment.
32 32  
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 +//__Create integration removal__//
30 +When removing an integration from Create, the Create phase is now correctly updated.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
32 +//__Legacy statistics__//
33 +Legacy pages are now correctly hidden when running on the current runtime architecture.
37 37  
38 -== **Feedback Items** ==
35 +//__Unused properties__//
36 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
39 39  
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.
38 +//__Enumeration values__//
39 +Enumeration values for event processors can now be edited in Create.
42 42  
43 -//__Save and cancel buttons placement__//
44 -The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
41 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
45 45  
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.
43 +//__SFTP sessions__//
44 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
48 48  
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.
51 -
52 -
53 -== **Bug Fixes** ==
54 -//__Topic and event-processor names__//
55 -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.
56 -
57 -//__System alignment__//
58 -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.
59 -
60 -
61 -
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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:
65 65  
66 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
67 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
68 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
69 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
70 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
50 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
51 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
52 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
71 71  
54 +== **Key Takeaways** ==
72 72  
73 -== **Key takeaways** ==
74 -
75 75  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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -78,10 +78,9 @@
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 79  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a next-generation-architecture only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
72 +{{/info}}
73 +)))
74 +
75 +(((
76 +{{toc/}}
77 +)))
94 94  {{/container}}
79 +{{/container}}