Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 411.1
edited by Erik Bakker
on 2024/03/11 14:39
on 2024/03/11 14:39
Change comment:
There is no comment for this version
To version 409.1
edited by Carlijn Kokkeler
on 2024/02/28 13:19
on 2024/02/28 13:19
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 -21 6-HackHeaven1 +215 - Tiny Tales - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,64 +3,17 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Aspartofouralignmentweekwealsohada hackathoneventfocusing ona wide arrayofreported feedbackontheportal. Themajorityofthereleaseblogwillbefocused onthis. On topofthat welaunchnewfunctionality thatmakes it easiertotransformto JSON, toselectinfra flowsin arelease,andmakesitpossible todeploymultiple agentstoa single machinethat adheresto specific conditions.Furthermore,severalannouncementswillbe made viathisreleaseblog(andotherchannels)to betterprepareyourodelforupcomingmajorchanges.6 +**Hi there, eMagiz developers!** This release blog is small because we have been busy working on items that will be released later. For this release, the event streaming graph has been improved. Moreover, some bug fixes have been done. The validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected. 7 7 8 -== ** Announcement - TLS 1.0 and 1.1 deprecated** == 9 - 10 -Placeholder for info from Bas 11 - 12 -{{info}}Text{{/info}} 13 - 14 -== **Announcement - Spring 6** == 15 - 16 -Placeholder for info from Jelle 17 - 18 -{{warning}}Text{{/warning}} 19 - 20 -== ** Updated release functionality - Infra flow selection** == 21 - 22 -This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level. 23 - 24 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 25 - 26 -When you are in edit mode you can select a new version via the right-click option as you were used to for other flows. 27 - 28 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 29 - 30 -On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release. 31 - 32 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 33 - 34 -== ** Updated deploy functionality on-premise - Multiple environments selection** == 35 - 36 -{{warning}}The following is only applicable under the following conditions: 37 - * Windows 2022 server 38 - * Atleast one port opened (as a consequence of a hosted web service){{/warning}} 39 - 40 -When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine. 41 - 42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 43 - 44 44 == **Feedback Items** == 45 -//__ Easier component selectionin flow designer__//46 -The area selectorthroughwhichyou canselectoneor morecomponentshasimprovedto allowfor aneasierselection ofsaidcomponentswhen they are displayedclosedto theedgeof thecanvas. Byexpanding theareayoucan select theselectionofthesecomponents will become much easier.9 +//__Improved event streaming graph__// 10 +The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. 47 47 48 -//__Improved handling of optionality in JSON on lists__// 49 -Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired. 12 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]] 50 50 51 -//__ Loading barwhensearchingforlogentries__//52 - Toindicate totheuserthateMagizis stillbusy retrievinglogentrieswe havenowaddeda loadingbarto the logentryoverviewuponpressingsearch.14 +//__Flow versions auto deletion__// 15 +Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. 53 53 54 -//__Improved feedback when deleting elements from Capture__// 55 -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. 56 - 57 -//__Enhanced filter options in Manage__// 58 -With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places. 59 - 60 -//__Copy property names from Create__// 61 -This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying. 62 - 63 - 64 64 == **Bug Fixes** == 65 65 //__Queue name validation__// 66 66 The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.