Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 7-Aligned State1 +220 - Patch Parade - Content
-
... ... @@ -1,113 +1,84 @@ 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!** Wehave donemuchwork forstategeneration,sothatyoucanderivemore information fromyourdata!Examplesareenrichment, aggregation,changedetectionand duplicatedetection.Stategenerationfunctionalityis onlyaccessibleformodels withanadd-onstategenerationlicense.Nextto stategeneration,severalimprovementsregardingthe alignmentofcomponentshavebeen made. Moreover,performanceimprovements and bug fixeshavebeen implemented. Lastly, a change in the metrics storage duration has been performed.6 +**Hi there, eMagiz developers!** In the last few weeks, we worked hard on solving several feedback items and bug fixes. On top of that, we have released a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Without further ado, let us look at our improvements and bug fixes below. 6 6 7 -== ** StateGeneration~*~***==8 +== **Feedback Items** == 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. 10 +//__Integration pattern information__// 11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration. 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). 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 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`. 15 +//__Message queue history__// 16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase. 24 24 25 - Added support for `#JsonPath` usagein SpELexpressions.18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 26 26 27 -//__ New imageversion 2.0.0__//28 - Theabovefunctionalitiesare features of thenew image version 2.0.0. Important to noteis that thelibrary usedfor CodeMappings has beenchanged. Changed the library usedfor Code Mappings. Any customerwithGen3 runtimesand code mappingsisrequiredto reset their infraflows priorto deploying on image 2.0.0.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 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. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 32 32 33 - == **MetricsStorageDuration** ==34 - We will changetheretentionof monitoringdataof different environments. For minuteleveldata, it will be kept fortest,acceptanceand productionenvironments for7, 14 and 30 daysrespectively. Thentheminuteleveldata willbe reducedtohour level datathenwill be storedfor test,acceptanceandproductionfor 3, 6 and12 months respectively.25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release- blog-207-aligned-state-metrics-storage.png]]28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 37 37 38 -== **Feedback Items** == 30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 39 39 40 -//__ Importfrom store__//41 - Thebutton'ImportfromStore'inDesign willdirectlyopenthe store insteadof showinga pop asking whetherthestoreshouldbeopened.33 +//__Machine deletion__// 34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 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. 36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.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. 38 +== **Bug Fixes** == 39 +//__Annotation styling__// 40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 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. 42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 51 51 52 -//__ Datasinkpage__//53 - Thedata sink pagehasbeenmovedtothe “Explore” tab.44 +//__Filter rejection warnings__// 45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 54 54 55 -//__Unused images removal__// 56 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 57 57 58 -//__ Flow Designerperformance__//59 - Performance improvementsfortheFlow Designerhavebeenimplemented.49 +//__Manage Explore__// 50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 60 60 61 -//__Pr opertieswithspecial characters__//62 - Whena user would migrateto gen3and deploy theirrelease containingpropertieswithspecialcharacters,certainflowscouldnot findthecorrect valuestopropertiesanymore orcouldnotfind the propertiesaltogether.With thisrelease, special characters such as a backslashdonot break properties afterdeployment.52 +//__Page refreshing__// 53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 63 63 64 -//__ Hidden flow fragements__//65 - Whenimportingitemsfromthestore,flowfragmentsthat are hiddenindesign will belistedundertheversionsincreate.55 +//__JMS header handling__// 56 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. 66 66 67 -//__ Resources disappearances__//68 - Resourceswould disappearintheflow designerwhenpressing Cancelon selectinga newresource.Withthis release,resources withouta namewill nottriggererrormessageswhenusersselectcomponents.58 +//__Message redelivery__// 59 +An issue has been fixed where large messages would be shown at the bottom of the Redelivery page instead of the right side of the page. 69 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. 61 +//__Deployment plan__// 62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 73 73 74 -//__ Highlightingresources__//75 - Theperformance ofhighlightingresourcesofselectedcomponentsisimprovedinRead onlymode.64 +//__Overview pages__// 65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 76 76 77 -== **Bug Fixes** == 67 +//__Memory check__// 68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines. 78 78 79 -//__ Topicand event-processornames__//80 -The stylingofthe eventstreamingcanvasintheCreateandDeployphaseshasbeenalteredslightlytomaketopic andevent-processor namesmorereadable.70 +//__Copy password__// 71 +The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. 81 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 99 == **Fancy Forum Answers** == 100 100 101 101 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: 102 102 103 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 104 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 105 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 106 -* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 77 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 78 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]] 107 107 80 +== **Key Takeaways** == 108 108 109 -== **Key takeaways** == 110 - 111 111 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: 112 112 113 113 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -114,10 +114,9 @@ 114 114 * If you have feedback or ideas for us, talk to the Platypus 115 115 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 116 116 * Clear your browser cache (Ctrl + Shift + Del) 117 -* Check out the release notes [here] 88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]] 118 118 * Start thinking about how the license tracker can aid your development 119 119 * Start thinking about major, minor, and patch 120 -* Upgrade to the latest build number 121 121 * Keep making great integrations 122 122 123 123 Let's stay in touch and till next time! ... ... @@ -125,6 +125,11 @@ 125 125 {{info}} 126 126 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 127 127 128 -~*~* Indicates a next-generation-architecture only feature. 129 -{{/info}})))((({{toc/}}))){{/container}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 130 130 {{/container}} 105 +{{/container}}