Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 358.1
edited by Carlijn Kokkeler
on 2024/01/29 14:19
on 2024/01/29 14:19
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 09-MaxVerstappen1 +213 - Joyful Journeys - Content
-
... ... @@ -1,72 +1,65 @@ 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!** Wehavedone.....6 +**Hi there, eMagiz developers!** This release .... 6 6 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. 9 9 10 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-next-gen-default.png]]9 +== **Feedback Items** == 11 11 12 - == **Cloud TemplateR11 - SingleLane** ==13 - This release introducesa newcloud template forallour customersrunning in a single-lanetupon the next generationarchitecture. This cloud templateintroducesfaster machineboot upand improved auto-healing. The completerelease notesonthecloud templatecanbe foundhere11 +//__Property releases__// 12 +When a new property release is created, this property release can now be viewed and deleted. 14 14 15 - ==**Cloud TemplateR13DoubleLane** ==14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 16 16 16 +//__Runtime deletion__// 17 +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. 17 17 18 -== **Feedback Items** == 19 +//__Update flows__// 20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 19 19 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. 22 +//__Input fields__// 23 +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. 25 25 26 -//__ Send buildrequestsasynchronously__//27 - Thestepin thedeploymentplanconcerning thepreparation ofruntime imageswillnowbe executedmorequicklyand reliably.25 +//__Memory settings__// 26 +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. 28 28 29 -//__ Queueexplorer milliseconds__//30 - Thequeuebrowsernowdisplaysmillisecondsinthetimestamps.28 +//__Runtime validation__// 29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 31 31 32 -//__ Canceland next buttonsorder__//33 - Theorderof the canceland next buttons whencreatinganewtrigger hasbeenchangedtoincreasealignmentacrosstheplatform.Now, all cancel buttonsareplacedontheright ofa'next'or'save' button.31 +//__UI improvements__// 32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 34 34 35 -//__ Unused images__//36 - Whena releaseis removed,therelatedunusedimageson-premisesmachineswillberemovedaswell.34 +//__Q&A forum search__// 35 +The option to search by pressing the Enter key has been added to the Q&A forum. 37 37 38 -//__ Carwashlogging__//39 - A newlogging featureenablingus tomakebetterchoicesinencryptionstandardswillbe released.37 +//__Wiretap & debug error messages__// 38 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 40 40 41 -//__ Staticalerts queueconsumers__//42 - Alertingwillnowonly generate alertsforqueuesthatarecreatedand managedbythe eMagizJMSserver.40 +//__Runtime overview image versions__// 41 +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. 43 43 44 44 == **Bug Fixes** == 44 +//__Action messages__// 45 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 45 45 46 -//__ Imagesrebuild__//47 -We fixed an issue wh ich causedthereleasepreparation steptotakelongertimethannecessaryandcaused themachinedeploymentstepstoexecutewhentheycouldbeskipped.47 +//__Removal of onramp__// 48 +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). 48 48 49 -//__ Flow Designerconnectionline__//50 -In the FlowDesigner anissuehas been fixed where the connectionlinefordrawingchannelsdidworkwellwhenscrollingorzoomingin/outon the canvas.50 +//__Component changes reversion__// 51 +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. 51 51 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. 54 - 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 - 58 58 == **Fancy Forum Answers** == 59 59 60 60 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: 61 61 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"]] 57 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 58 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 59 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 66 66 61 +== **Key Takeaways** == 67 67 68 -== **Key takeaways** == 69 - 70 70 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: 71 71 72 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -76,7 +76,6 @@ 76 76 * Check out the release notes [here] 77 77 * Start thinking about how the license tracker can aid your development 78 78 * Start thinking about major, minor, and patch 79 -* Upgrade to the latest build number 80 80 * Keep making great integrations 81 81 82 82 Let's stay in touch and till next time! ... ... @@ -84,6 +84,11 @@ 84 84 {{info}} 85 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 87 -~*~* Indicates a next-generation-architecture only feature. 88 -{{/info}})))((({{toc/}}))){{/container}} 79 +{{/info}} 80 +))) 81 + 82 +((( 83 +{{toc/}} 84 +))) 89 89 {{/container}} 86 +{{/container}}