Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07-AlignedState1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.dfirdausy - Content
-
... ... @@ -1,77 +1,67 @@ 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 havedonemuchwork forstategeneration,sothatyoucan derivemoreinformationfromyourdata!Examplesare enrichment, aggregation,changedetection andduplicatedetection.Stategeneration functionality is onlyaccessibleformodels withan add-onstategenerationlicense.Nextto stategeneration,severalimprovementsregardingthealignmentofcomponentshavebeenmade.Moreover,performanceimprovementsand bugfixeshavebeen implemented. Lastly,achangeinthemetricsstorage durationhasbeenperformed.6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor. 6 6 7 -== **State Generation** == 8 +== **Feedback Items** == 9 +//__Retention duration and bytes in Capture__// 10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes. 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. 12 +//__Help text panel in Capture__// 13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 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). 15 +//__Adding tags in Capture__// 16 +In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 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`. 18 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 19 + 20 +//__Property value page__// 21 +Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page. 24 24 25 - Addedsupportfor`#JsonPath`usage in SpELexpressions.23 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 26 26 27 -//__ Newimageversion2.0.0__//28 - Theabovefunctionalitiesare featuresof the new imageversion2.0.0. Important to note isthat thelibrary used for Code Mappingshas been changed.Changedthe library used for Code Mappings.Any customerwith Gen3runtimes andcode mappingsis required to reset their infraflows priorto deploying on image2.0.0.25 +//__Improved text in Design architecture__// 26 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 29 29 30 -//__ Componentpages__//31 - Pagestoaddthenewcomponents havebeencreated. Forms havebeencreatednicelywith proper helptexts.TheEHCachecache managerhasbeen removed.28 +//__Adding attributes for a message definition__// 29 +We fixed an issue where your selected attributes were lost when navigating between paginations while adding more attributes to the entity in the pop-up shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model. 32 32 33 - == **Metrics StorageDuration** ==34 -We will change theretentionofmonitoringdataofdifferentenvironments.For minuteleveldata,itwillbekept fortest, acceptanceandproductionenvironments for5, 7 and30daysrespectively.Thentheminuteleveldata willbereducedtohourleveldatathenwillbestored fortest,acceptanceandproductionfor3, 6and12monthsrespectively.31 +//__Helptext for HTTP methods__// 32 +We improved the help text for the HTTP method field in the HTTP outbound gateway and HTTP outbound channel adapter flow components to provide clearer descriptions for different HTTP methods. Additionally, we implemented a validation for these components to prevent selecting the HTTP method 'PATCH' if an Apache HttpComponents REST template is not provided. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 34 +//__External links__// 35 +Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab. 37 37 38 -== **Feedback Items** == 37 +//__Test Message from Manage-Explore__// 38 +We improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 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. 40 +<Screenshot here> 42 42 43 -//__ Save andcancel buttonsplacement__//44 - Thesaveandcancelbuttonshavebeenplacedslightlyfurtherapartfromeachothertoavoidmisclicking.42 +//__Password property__// 43 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 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. 45 +== **Bug Fixes** == 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 - 47 +//__Event Processor Keystore and Trustore__// 52 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. 49 +We fixed an issue where the keystore location and the truststore location were generated incorrectly when creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture. 56 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 59 60 - 61 - 52 + 53 + 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"]] 58 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 59 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 60 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 61 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 71 71 63 +== **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] 71 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.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}} 81 +{{/info}} 82 +))) 83 + 84 +((( 85 +{{toc/}} 86 +))) 94 94 {{/container}} 88 +{{/container}}