Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 195.1
edited by Carlijn Kokkeler
on 2023/10/23 15:13
on 2023/10/23 15:13
Change comment:
There is no comment for this version
To version 416.1
edited by Carlijn Kokkeler
on 2024/03/25 11:42
on 2024/03/25 11:42
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07 -Aligned State1 +217 - Template Tango - Content
-
... ... @@ -1,70 +1,56 @@ 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!** 6 6 7 -== **State Generation** == 8 +== **Cloud Template R12 Docker - Single Lane** == 9 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here. 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 +== **Cloud Template R14 Docker - Double Lane** == 12 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here. 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** == 15 +//__Custom trigger__// 16 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger. 22 22 23 - Added support for SpEL propertyaccessors for XMLand JSON,meaningthat you can read messagepayloadsin SpELexpressionseasily. Forexample, toretrievehevalue for 'id' inthefollowingJSON String: `{"id":"123"}`, this SpELexpression suffices: `payload.id`.18 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 24 24 25 -Added support for `#JsonPath` usage in SpEL expressions. 20 +//__Copy to clipboard buttons__// 21 +Copy to clipboard buttons have been added to various pages: 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. 23 + * Deploy agent pop-up 24 + * Create - Flow designer: Properties 25 + * Deploy - Property releases: Property details 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. 27 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 32 32 33 - == **Metrics StorageDuration** ==34 - Manage - Monitoring:We will changethe retentionof monitoringdata of differentenvironments.Forminutelevel data, itwill be kept for test,acceptanceandproductionenvironmentsfor5, 7 and 30 daysrespectively.Thentheminuteleveldatawillbe reducedtohourlevel data thenwill betoredfortest,acceptanceand productionfor 3, 6 and 12 months respectively.29 +//__Remove H2 database__// 30 +For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following: 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 32 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 33 +* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. 34 +* For on-premise runtimes, only a reset of the runtime is needed. 37 37 38 - == **FeedbackItems** ==36 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 39 39 40 -//__Import from store__// 41 -Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened. 42 - 43 -//__Save and cancel buttons__// 44 -The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking. 45 - 46 -//__User session times__// 47 -Manage - Monitoring: 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. 48 - 49 - 50 - 51 51 == **Bug Fixes** == 39 +//__Runtime overview improvements__// 40 +The runtime overview has been improved regarding checks on the runtime version. 52 52 53 - 54 - 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 -* [[ JSONWebTokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]60 -* [[ Determining container sizes&readingarchitecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]61 -* [[ SFTP connectivity-supportedalgorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]62 -* [[ Deploypropertyreleaseresultsinmissingflowsinruntime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]63 -* [[ MessageDeliveryException:Dispatcherhas nosubscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]46 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 47 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 48 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 49 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 50 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 64 64 52 +== **Key Takeaways** == 65 65 66 -== **Key takeaways** == 67 - 68 68 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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -74,7 +74,6 @@ 74 74 * Check out the release notes [here] 75 75 * Start thinking about how the license tracker can aid your development 76 76 * Start thinking about major, minor, and patch 77 -* Upgrade to the latest build number 78 78 * Keep making great integrations 79 79 80 80 Let's stay in touch and till next time! ... ... @@ -82,6 +82,11 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a next-generation-architecture only feature. 86 -{{/info}})))((({{toc/}}))){{/container}} 70 +{{/info}} 71 +))) 72 + 73 +((( 74 +{{toc/}} 75 +))) 87 87 {{/container}} 77 +{{/container}}