Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
on 2024/01/29 14:41
Change comment:
There is no comment for this version
To version 248.1
edited by Carlijn Kokkeler
on 2023/11/21 11:37
on 2023/11/21 11:37
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 13-JoyfulJourneys1 +209 - Max Verstappen - Content
-
... ... @@ -1,82 +1,74 @@ 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 5 6 -**Hi there, eMagiz developers!** This release ....5 +**Hi there, eMagiz developers!** We have done ..... 7 7 8 -== **Pop-up Improvements** == 9 -//__Property releases__// 10 -When a new property release is created, this property release can now be viewed and deleted. 7 +{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}} 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 9 +== **Quicker Deployment Plan** == 10 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now! 13 13 14 - //__Runtimedeletion__//15 -Wh endeletingaruntime, the errormessagethatsdisplayed is more descriptive. The error messageswillnow include thenames ofheflowsthatrunonthecontainer.12 +== **Next Generation Architecture Default** == 13 +With this release, the next generation architecture will become the default. New models will use this generation as default. 16 16 17 -//__Wiretap & debug error messages__// 18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 15 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 19 19 20 - //__Actionmessages__//21 -Th eformattingofactionmessagesregardingchangesinretentionbytes/hourshasbeen improved. Theactionmessagewillnow displaythe correct,actualbehaviour.17 +== **Cloud Template R11 - Single Lane** == 18 +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 22 22 23 -== **User Journey** == 24 -//__Update flows__// 25 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 20 +== **Cloud Template R13 - Double Lane** == 21 +This release introduces a new cloud template for all our customers running in a double-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 26 26 27 -//__Input fields__// 28 -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. 29 - 30 -//__UI improvements__// 31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 32 - 33 -//__Q&A forum search__// 34 -The option to search by pressing the Enter key has been added to the Q&A forum. 35 - 36 36 == **Feedback Items** == 37 37 38 -//__Memory settings__// 39 -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. 25 +//__Unused properties overview__// 26 +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: 27 +* Not used by any runtime that is in the Create phase release. 28 +* Not required by a flow that is in the Create phase release. 29 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 40 40 41 -//__ Runtimevalidation__//42 - Validationforruntimesthataremoved fromonpremisestothe cloud orviceversahas beenimproved.31 +//__Send build requests asynchronously__// 32 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 43 43 44 -//__ Runtimeoverviewimage versions__//45 - Insight into inventedand actual deploymentshasbeen improved. If the releaseversionnumberonruntimes isdifferent compared with the release,thisisshown in theruntimeoverview.34 +//__Queue explorer milliseconds__// 35 +The queue browser now displays milliseconds in the timestamps. 46 46 47 -== **Bug Fixes** == 37 +//__Cancel and next buttons order__// 38 +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. 48 48 49 -//__ Removalof onramp__//50 -We fixedanissuewhere it wasnot possible toremove the lastonramp linkedto asplitted entry(thatwas anall-entrybefore).40 +//__Unused images__// 41 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 51 51 52 -//__C omponent changesreversion__//53 - Intheflow designerabug could occurwherethechanges toa componentwouldberevertedif theeditingpop-up would bekept openforsome minutes without havingsavedthe changesyet. Thishasbeenfixed.43 +//__Carwash logging__// 44 +A new logging feature enabling us to make better choices in encryption standards will be released. 54 54 55 -//__Stat egenerationtatistics__//56 - Thestate generationraphswill nowshowthecorrectnumberofcachehitsand misses.46 +//__Static alerts queue consumers__// 47 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 57 57 58 -//__Runtime statistics details__// 59 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 49 +== **Bug Fixes** == 60 60 61 -//__ Queue browser timestamps__//62 - Alltimestampformattinginthequeuebrowser isnowalignedtoyyyy-MM-ddHH:mm:ss.SSS.51 +//__Flow Designer connection line__// 52 +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. 63 63 64 -//__ Deploymentprechecks__//65 - Duringdeployments precheckswillbedoneon runtimesthat stillhave tobedeployedfromdeployarchitecture.54 +//__Portal for migrated models__// 55 +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. 66 66 67 -//__ Additionand deletionof internalrecipients__//68 - Internalrecipientsare nowaddedanddeletedcorrectly. Before,an internalrecipientcould beaddedandthereafter deletedautomaticallywhenrefreshingthepage.57 +//__Error channel inbounds__// 58 +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. 69 69 70 70 == **Fancy Forum Answers** == 71 71 72 72 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: 73 73 74 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 64 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 65 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 66 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 67 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 77 77 78 -== **Key Takeaways** == 79 79 70 +== **Key takeaways** == 71 + 80 80 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: 81 81 82 82 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -86,6 +86,7 @@ 86 86 * Check out the release notes [here] 87 87 * Start thinking about how the license tracker can aid your development 88 88 * Start thinking about major, minor, and patch 81 +* Upgrade to the latest build number 89 89 * Keep making great integrations 90 90 91 91 Let's stay in touch and till next time! ... ... @@ -93,11 +93,6 @@ 93 93 {{info}} 94 94 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 95 95 96 -{{/info}} 97 -))) 98 - 99 -((( 100 -{{toc/}} 101 -))) 89 +~*~* Indicates a next-generation-architecture only feature. 90 +{{/info}})))((({{toc/}}))){{/container}} 102 102 {{/container}} 103 -{{/container}}