Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 191.1
edited by Carlijn Kokkeler
on 2023/10/23 15:01
on 2023/10/23 15:01
Change comment:
There is no comment for this version
To version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
on 2024/03/11 15:13
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07-AlignedState1 +216 - Hack Heaven - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,104 +1,115 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 + 6 +**Hi there, eMagiz developers!** As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes. 4 4 5 - **Hithere, eMagiz developers!**We have done much work for state generation, so that youcanderivemoreinformationfromyour data! Examples are enrichment, aggregation, change detection and duplicate detection.Stategeneration functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvementsregarding the alignmentof componentshave been made. Moreover,performanceimprovements and bug fixes have been implemented. Lastly, achange inthemetrics storagedurationhas been performed.8 +== ** Announcement - TLS versions deprecated** == 6 6 7 - == **StateGeneration**==10 +Placeholder for info from Bas 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 +{{info}}Text{{/info}} 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 +== **Announcement - Spring 6** == 22 22 23 - Added support for SpEL propertyaccessors for XML and JSON, meaning that you can read message payloads in SpELexpressionseasily. For example, to retrieve the valuefor'id' inthefollowingJSON String: `{"id":"123"}`, this SpEL expressionsuffices: `payload.id`.16 +Placeholder for info from Jelle 24 24 25 - Added support for `#JsonPath` usageinSpELexpressions.18 +{{warning}}Text{{/warning}} 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. 20 +== **Infra flow selection** == 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. 22 +This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually. 32 32 24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 33 33 34 -== **Metrics Storage Duration** == 35 - 36 - 37 - 26 +In edit mode, you can select a new version via the right-click option, which you already use for other flows. 38 38 39 - == **FeedbackItems** ==28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 40 40 41 -//__Alerting manual pause__// 42 -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. 30 +We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release. 43 43 44 -//__Ordering of graphs in Manage__// 45 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 46 46 47 -//__UTC times in Grafana panels__// 48 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 34 +== **Multiple environments selection** == 49 49 50 -//__Update flow designer version__// 51 -The framework used in the flow designer has been updated, improving performance. 36 +{{warning}}The following is only applicable under the following conditions: 37 + * Windows 2022 server 38 + * At least one port opened (as a consequence of a hosted web service){{/warning}} 52 52 53 -//__Carwash track TLS versions in logging__// 54 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 40 +When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine. 55 55 56 -//__Moving channels in the flow designer__// 57 -Moving already attached channels in the flow designer has been made sligthly easier. 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 58 58 59 -//__Topic sizes description change__// 60 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 44 +== **Feedback Items** == 45 +//__Easier component selection in flow designer__// 46 +The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier. 61 61 62 -//__ Passwordchangenotification__//63 - Whenanaccount passwordchange requestismade,even whenthis fails,a mailntto the accountownertoinformtheowner about the action.48 +//__Improved handling of optionality in JSON on lists__// 49 +Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties. 64 64 65 -//__Password comparison__// 66 -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. 51 +With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired. 67 67 68 -//__ Inactiveuseralerting__//69 - Inactivatedusersarenow removedfromallalertsettings(included“disabled“settings)toavoidundesirablenotifications.53 +//__Loading bar when searching for log entries__// 54 +To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search. 70 70 71 -//__ Alphabeticalsortingon userlevel inHTTPstatistics__//72 - Variablesinthe3rdgeneration runtimesHTTPstatisticsdetailpagesarenowsortedcase insensitive.56 +//__Improved feedback when deleting elements from Capture__// 57 +To better specify to the user which integration or system the user intends to delete, we have improved the text in the confirmation pop-up. This way, we can provide more information to the user to avoid mistakes. 73 73 59 +//__Enhanced filter options in Manage__// 60 +With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places. 74 74 62 +//__Copy property names from Create__// 63 +This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying. 64 + 65 +//__Improved feedback during migration to the current runtime architecture__// 66 +Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order. 67 + 68 +//__Block user from making changes to their cloud while another upgrade is still in progress__// 69 +We now block users from changing their cloud configuration when another upgrade is ongoing. 70 + 71 +//__Cron trigger validation__// 72 +We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression. 73 + 75 75 == **Bug Fixes** == 75 +//__Making Edit (and View) the default action when configuring parameters__// 76 +We have made the Edit (and View) button the default action when configuring parameters in a transformation. 76 76 77 -//__ Flow designerstyling__//78 - Thestyling of theflow designer'sleftcomponentpanel has beenrestructured, solvingararebugwhichwouldbreak thestylingof certainfunctionalities.78 +//__Property configuration pop-up resized__// 79 +We have resized the property configuration overviews to make the property value better readable. 79 79 80 -//__ Partial search formessages__//81 - It isnowpossibleto search onmessagespartially inManage Monitoring. Forexample,a searchforUptime can bedonebysearchingfor "up" "time" "ptim".81 +//__Alphabetically sorted components in the flow designer__// 82 +As of this release, we now sort the components alphabetically in the flow designer. 82 82 83 -//__ Diskusageafter cloudtemplateupdate__//84 - Inthelastcloudtemplate update therewas anssuewith disk performance. Thishasbeenresolvedin thisrelease.Youcan manuallyupgradeyourcloud template,orrelyon automaticupdates.84 +//__Improved sorting on runtime overview__// 85 +As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake. 85 85 86 -//__ Error handlingmigration__//87 - If thereisno custom error handling, when migrating to Gen3,theerror channel to“errorChannel” isnly createdforthefirstinboundin an entry flow. Thishas been fixed by addinga migration step, wherewe set the errorchannelfall inboundsinflow to “errorChannel” if the customrror handling is set to false.87 +//__Improved sorting on catalog overview__// 88 +As of this release, we now sort the topics in the catalog by name. 88 88 90 +//__Styling fix on rich text editors__// 91 +Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors. 92 + 93 +//__Styling fix on release edit__// 94 +As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header." 95 + 96 +//__Removed false-positive alerts on transformations__// 97 +When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation. 98 + 99 +//__Event Streaming Graphs - view thirty days back__// 100 +Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further. 101 + 102 +//__Improved helptext__// 103 +We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 104 + 89 89 == **Fancy Forum Answers** == 90 90 91 91 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: 92 92 93 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 94 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 95 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 96 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 97 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 109 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 98 98 111 +== **Key Takeaways** == 99 99 100 -== **Key takeaways** == 101 - 102 102 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: 103 103 104 104 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -108,7 +108,6 @@ 108 108 * Check out the release notes [here] 109 109 * Start thinking about how the license tracker can aid your development 110 110 * Start thinking about major, minor, and patch 111 -* Upgrade to the latest build number 112 112 * Keep making great integrations 113 113 114 114 Let's stay in touch and till next time! ... ... @@ -116,6 +116,11 @@ 116 116 {{info}} 117 117 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 118 118 119 -~*~* Indicates a next-generation-architecture only feature. 120 -{{/info}})))((({{toc/}}))){{/container}} 129 +{{/info}} 130 +))) 131 + 132 +((( 133 +{{toc/}} 134 +))) 121 121 {{/container}} 136 +{{/container}}