Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 187.1
edited by Carlijn Kokkeler
on 2023/10/23 14:45
on 2023/10/23 14:45
Change comment:
There is no comment for this version
To version 363.1
edited by Carlijn Kokkeler
on 2024/01/29 14:50
on 2024/01/29 14:50
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 +213 - Joyful Journeys - Content
-
... ... @@ -1,97 +1,87 @@ 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 donemuch work for state generation, so that you can derive more information from your data! Examplesareenrichment, aggregation, change detection and duplicatedetection. State generation functionality isonly accessible for models with an add-on state generation license. Next to state generation, several improvementsregarding the alignment ofcomponents have been made. Moreover,performance improvements and bug fixes have beenimplemented. Lastly, achangein themetrics storageduration has been performed.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 6 6 7 -== **State Generation** == 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. 9 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 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-blog-213-joyful-journeys-property-release.png]] 22 22 23 - Added support for SpEL property accessors for XML and JSON, meaningthat you can readmessagepayloads in SpELexpressions easily. Forexample,to retrieve the value for 'id' inthe following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.24 - Addedsupportfor`#JsonPath`usage inSpELexpressions15 +//__Runtime deletion__// 16 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 25 25 18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 26 26 27 -== **Metrics Storage Duration** == 28 - 29 - 30 - 21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 31 31 32 -== **Feedback Items** == 33 33 34 -//__Alerting manual pause__// 35 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 25 +== **Formatting & Alignments** == 36 36 37 -//__ Ordering of graphsin Manage__//38 - ThegraphsinManage are noworderedaccordingtoimportance.This meansthatruntimestatisticsare sorted by "ProcessCPU usage" (highestfirst),queuestatistics are sortedby "Messagesin queue"(highestfirst),andHTTP statisticsaresorted by "Unsuccessfulrequests" (highest first).27 +//__Input fields__// 28 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions. 39 39 40 -//__U TCtimes in Grafanapanels__//41 - AllGrafanapanelsnowshow UTCtimes,whichare normallyusedinMagiz,insteadof local(browser)time zones. This way, it iseasier tomatchgraphswith loggingeventsoralerts.30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 42 42 43 -//__ Update flow designerversion__//44 - The framework used in the flow designerhasbeenupdated,improving performance.33 +//__Component changes reversion__// 34 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 45 45 46 -//__ CarwashtrackTLS versionsin logging__//47 - Anewlogging featurewillbe released, enablingustomake betterchoices in deprecatingoldencryptionstandards.36 +//__State generation statistics__// 37 +The state generation graphs will now show the correct number of cache hits and misses. 48 48 49 -//__ Moving channels in theflowdesigner__//50 - Moving alreadyattachedchannelsin theflowdesignerhasbeenmade sligthlyeasier.39 +//__Queue browser timestamps__// 40 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 51 51 52 -//__ Topic sizesdescriptionchange__//53 -In hechangedescription(and History) when alteringthetopicsizeof atopictheewandoldvaluewereswitched around creatingconfusion,thishas been resolved.42 +//__Addition and deletion of internal recipients__// 43 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 54 54 55 -//__Password change notification__// 56 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 57 57 58 -//__Password comparison__// 59 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 46 +== **Feedback Items** == 60 60 61 -//__ Inactiveuser alerting__//62 -Ina ctivatedusers arenowremoved fromallalert settings(included“disabled“settings)to avoidundesirablenotifications.48 +//__Update flows__// 49 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 63 63 64 -//__A lphabeticalsorting onuserlevel in HTTPstatistics__//65 - Variables3rd generationruntimesHTTP statisticsdetail pagesarenowsortedcaseinsensitive.51 +//__Q&A forum search__// 52 +The option to search by pressing the Enter key has been added to the Q&A forum. 66 66 54 +//__Memory settings__// 55 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 67 67 57 +//__Runtime validation__// 58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 59 + 60 +//__Runtime overview image versions__// 61 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 62 + 68 68 == **Bug Fixes** == 69 69 70 -//__ Flowdesignerstyling__//71 - Thestylingoftheflowdesigner'sleftcomponentpanelhasbeenestructured,solvingararebug which wouldbreakthestylingof certainfunctionalities.65 +//__Removal of onramp__// 66 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 72 72 73 -//__ Partialsearchfor messages__//74 - Itisnowpossibleto searchonmessagespartiallyinManageMonitoring.Forexample,a searchforUptimecanbedoneby searchingfor"up" "time" "ptim".68 +//__Runtime statistics details__// 69 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 75 75 76 -//__D isk usageafter cloud templateupdate__//77 - Inthe last cloudtemplateupdate there was anissue with diskperformance.Thishasbeenresolvedin this release.You canmanuallyupgradeyourcloudtemplate,orrelyonautomaticupdates.71 +//__Deployment prechecks__// 72 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 78 78 79 -//__Error handling migration__// 80 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 81 81 82 82 == **Fancy Forum Answers** == 83 83 84 84 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: 85 85 86 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 87 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 88 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 89 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 90 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 79 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 80 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 81 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 91 91 83 +== **Key Takeaways** == 92 92 93 -== **Key takeaways** == 94 - 95 95 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: 96 96 97 97 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -101,7 +101,6 @@ 101 101 * Check out the release notes [here] 102 102 * Start thinking about how the license tracker can aid your development 103 103 * Start thinking about major, minor, and patch 104 -* Upgrade to the latest build number 105 105 * Keep making great integrations 106 106 107 107 Let's stay in touch and till next time! ... ... @@ -109,6 +109,11 @@ 109 109 {{info}} 110 110 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 111 111 112 -~*~* Indicates a next-generation-architecture only feature. 113 -{{/info}})))((({{toc/}}))){{/container}} 101 +{{/info}} 102 +))) 103 + 104 +((( 105 +{{toc/}} 106 +))) 114 114 {{/container}} 108 +{{/container}}