Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 410.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 287.1
edited by Carlijn Kokkeler
on 2023/12/04 15:48
on 2023/12/04 15:48
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-Hack Heaven1 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,89 +2,60 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 [[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, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes. 7 7 8 - ==**Announcement-TLS1.0and1.1deprecated**==6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving. 9 9 10 - Placeholderfor info from Bas8 +== **Alerts** == 11 11 12 -{{info}}{{/info}} 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 13 13 14 -== **Announcement - Spring 6** == 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 15 15 16 -Placeholder for info from Jelle 17 - 18 -{{warning}}{{/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 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 they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier. 47 47 48 -//__ Improved handling of optionality inJSONonlists__//49 - Previously,eMagiz would alwayscreatea JSON array if your data modelxpecteda list.This would leadtounexpectedand undesirablebehaviorofthemessage as empty arrays arenot alwaysacceptedbyexternal parties.Withthisreleasewehavechangedthe way in which we generatetheJSON output should therebean empty listin theoutput.Consequently the empty list will **not** be partof theoutputanymoreasdesired.18 +//__Container version overview__// 19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 50 50 51 -//__Loading bar when searching for log entries__// 52 -To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 53 53 54 -//__ Improvedfeedback whendeletingelements from Capture__//55 - To betterspecifytotheuserwhich integrationorystemtheuserintendsto deletewe haveimprovedthetextin theconfirmation pop-up. Thiswaywecan providemoreinformationto theuser to avoidmistakes.23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 56 56 57 -//__ Enhanced filter optionsinManage__//58 - With this releasewehave addedfilteroptionson bothheAlerting tab andthe Trigger configurationpop-up. This results inbeingabletofilter onStatus (Alerting) and Queues,Topics,Recipients, and more(Triggerconfigurationpop-up)intheseplaces.26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 59 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. 29 +== **Bug Fixes** == 62 62 31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 63 63 64 -== **Bug Fixes** == 65 -//__Queue name validation__// 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. 34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 67 67 68 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 37 +//__View all store items__// 38 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 69 69 70 -//__ Removalof onramp__//71 - Anissue has beenfixedwhereremovinganonrampthat waspreviouslylinkedto acombined entrywas impossiblein theCreatephase.40 +//__Out of memory behavior__// 41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 72 72 73 -//__ eMagizlogin__//74 - In thelogin screen,userscannowpress"enter"tologinwhentheusernamefieldisselected. Previously,this wasonlytheaseforthepassword field.43 +//__Max fetch size__// 44 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 75 75 76 76 == **Fancy Forum Answers** == 77 77 78 78 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: 79 79 80 -* [[e MagizMendixKafkaModuleIssue(Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]81 -* [[ SFTP+Privatekey notworking>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]82 -* [[ Attributenameisnotallowedtostart with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]83 -* [[ HowdoI changethedefaultcontent-typefrom ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]84 -* [[ PreparingImagefor<runtime>failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 85 85 86 -== **Key Takeaways** == 87 87 57 +== **Key takeaways** == 58 + 88 88 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: 89 89 90 90 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -94,6 +94,7 @@ 94 94 * Check out the release notes [here] 95 95 * Start thinking about how the license tracker can aid your development 96 96 * Start thinking about major, minor, and patch 68 +* Upgrade to the latest build number 97 97 * Keep making great integrations 98 98 99 99 Let's stay in touch and till next time! ... ... @@ -101,6 +101,7 @@ 101 101 {{info}} 102 102 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 103 103 76 +~*~* Indicates a next-generation-architecture only feature. 104 104 {{/info}} 105 105 ))) 106 106