Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 414.1
edited by Erik Bakker
on 2024/03/11 14:49
on 2024/03/11 14:49
Change comment:
There is no comment for this version
To version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
on 2023/11/21 11:09
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 16-HackHeaven1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,98 +1,72 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 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- TLS versionsdeprecated**==5 +**Hi there, eMagiz developers!** We have done ..... 9 9 10 -Placeholder for info from Bas 7 +== **Next Generation Architecture Default** == 8 +With this release, the next generation architecture will become the default. New models will use this generation as default. 11 11 12 - {{info}}Text{{/info}}10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 13 13 14 -== **Announcement - Spring 6** == 12 +== **Cloud Template R11 - Single Lane** == 13 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here 15 15 16 - Placeholderforinfofrom Jelle15 +== **Cloud Template R13 - Double Lane** == 17 17 18 -{{warning}}Text{{/warning}} 19 19 20 -== **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 -== **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 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. 20 +//__Unused properties overview__// 21 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 22 +* Not used by any runtime that is in the Create phase release. 23 +* Not required by a flow that is in the Create phase release. 24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 50 50 51 -//__ Loadingbarwhen searching forlog entries__//52 -T oindicatetotheuserthateMagizis stillbusyretrievinglogentrieswe havenowadded a loadingbar tothelogentryoverviewuponpressing search.26 +//__Send build requests asynchronously__// 27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 53 53 54 -//__ Improved feedbackwhen deletingelementsfrom Capture__//55 -T o better specify to the user which integrationorystem the userintends to delete we haveimproved the textin the confirmation pop-up. Thisway wean providemoreinformationto theuserto avoidmistakes.29 +//__Queue explorer milliseconds__// 30 +The queue browser now displays milliseconds in the timestamps. 56 56 57 -//__ Enhancedfilteroptionsin Manage__//58 - Withthisreleasewehave addedfilteroptionson boththeAlertingtaband theTrigger configurationpop-up. Thisresultsinbeingabletofilter onStatus (Alerting)and Queues,Topics,Recipients,andmore(Triggerconfigurationpop-up)in these places.32 +//__Cancel and next buttons order__// 33 +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. 59 59 60 -//__ Copy propertynamesfromCreate__//61 - Thisreleaseunlocks thepossibilitytoeasilycopythenameof apropertyplaceholdersoitcanbeusedwhilstdeploying.35 +//__Unused images__// 36 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 62 62 63 -//__ Improved feedbackduringmigrationto the current-runtime architecture__//64 - Wehaveimprovedthefeedback shouldyou try to migrate theJMS beforeanyother runtimeunderCreate-> Settings.38 +//__Carwash logging__// 39 +A new logging feature enabling us to make better choices in encryption standards will be released. 65 65 66 -//__ Block user from makingchangesto theircloud whilst anotherupgradeis still in progress__//67 - We nowblocktheuser frommaking changes to their cloud configuration whenanotherupgradeisstillinprogress.41 +//__Static alerts queue consumers__// 42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 68 68 69 -//__Cron trigger validation__// 70 -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. 71 - 72 72 == **Bug Fixes** == 73 -//__Queue name validation__// 74 -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. 75 75 76 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 46 +//__Images rebuild__// 47 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped. 77 77 78 -//__ Removalfonramp__//79 - An issue has been fixed whereremovingan onrampthat waspreviouslylinkedtoa combinedentrywas impossible in theCreate phase.49 +//__Flow Designer connection line__// 50 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 80 80 81 -//__ eMagizlogin__//82 - In theloginscreen,userscan nowpress "enter"to logwhenthe usernamefieldisselected.Previously,thiswasonlythecaseforthepasswordfield.52 +//__Portal for migrated models__// 53 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 83 83 55 +//__Error channel inbounds__// 56 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 57 + 84 84 == **Fancy Forum Answers** == 85 85 86 86 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: 87 87 88 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 89 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 90 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 91 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 92 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 93 93 94 -== **Key Takeaways** == 95 95 68 +== **Key takeaways** == 69 + 96 96 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: 97 97 98 98 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -102,6 +102,7 @@ 102 102 * Check out the release notes [here] 103 103 * Start thinking about how the license tracker can aid your development 104 104 * Start thinking about major, minor, and patch 79 +* 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,11 +109,6 @@ 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 -{{/info}} 113 -))) 114 - 115 -((( 116 -{{toc/}} 117 -))) 87 +~*~* Indicates a next-generation-architecture only feature. 88 +{{/info}})))((({{toc/}}))){{/container}} 118 118 {{/container}} 119 -{{/container}}