Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
on 2024/01/29 14:49
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,74 +1,88 @@ 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!** In this release, several improvements for pop-ups have been achieved. 6 6 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}} 8 8 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! 9 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 11 11 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. 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 14 14 15 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 15 +//__Runtime deletion__// 16 +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. 16 16 17 - == **Cloud TemplateR11- SingleLane** ==18 -Th is releaseintroducesnewcloudtemplateforallour customersrunning in asingle-lanesetup on theextgenerationarchitecture. Thiscloud templateintroduces fastermachine boot up andimprovedauto-healing. Thecompletereleasenoteson thecloud templatecan befound here18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 19 19 20 - == **CloudTemplateR13 - Double Lane** ==21 -Th is releaseintroduces a new cloud templateforall ourcustomers runninginadouble-laneetuponthenextgenerationarchitecture. Thiscloud template introducesfastermachineboot up andimprovedauto-healing. The completereleasenotesonthe cloud templatecanbefound here21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 22 22 23 -== **Feedback Items** == 24 24 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. 25 +== **Formatting & Alignments** == 30 30 31 -//__ Send buildrequests asynchronously__//32 - The step indeploymentplanconcerningthepreparation of runtimeimageswillnow be executedmorequicklyandreliably.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. 33 33 34 -//__ Queueexplorermilliseconds__//35 - Thequeuebrowsernowdisplaysmillisecondsin the timestamps.30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 36 36 37 -//__ Cancelandnextbuttonsorder__//38 - Theorderof thecancelandnextbuttonswhen creating a newtriggerhas beenchanged toincreasealignmentacrossthe platform.Now,all cancelbuttons areplacedontherightofa 'next'or'save' button.33 +//__Runtime overview image versions__// 34 +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. 39 39 40 -//__ Unusedimages__//41 - When a releaseisremoved,therelated unusedimagesin the on-premisesmachines willberemoved aswell.36 +//__Component changes reversion__// 37 +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. 42 42 43 -//__ Carwashlogging__//44 - A newlogging feature enablingustomakebetterchoicesinncryptionstandardswill be released.39 +//__State generation statistics__// 40 +The state generation graphs will now show the correct number of cache hits and misses. 45 45 46 -//__ Static alerts queueconsumers__//47 -Alerting willnowonly generatealerts forqueuesthat arecreatedandmanagedbytheeMagiz JMSserver.42 +//__Queue browser timestamps__// 43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 48 48 45 +//__Addition and deletion of internal recipients__// 46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 47 + 48 + 49 +== **Feedback Items** == 50 + 51 +//__Update flows__// 52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 53 + 54 +//__Q&A forum search__// 55 +The option to search by pressing the Enter key has been added to the Q&A forum. 56 + 57 +//__Memory settings__// 58 +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. 59 + 60 +//__Runtime validation__// 61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 62 + 63 + 49 49 == **Bug Fixes** == 50 50 51 -//__ FlowDesigner connection line__//52 - In theFlow Designeran issue hasbeenfixedwhere theconnection linefordrawingchannelsdidworkwellwhenscrolling orzooming in/out on thecanvas.66 +//__Removal of onramp__// 67 +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). 53 53 54 -//__ Portal for migratedmodels__//55 -We fixed a rare case where aruntimecouldnotstart,orlogging,errors andmetricscould notbe seenin theportal for amodelthathad justmigratedto thenextgenerationarchitecture.69 +//__Runtime statistics details__// 70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 56 56 57 -//__ Errorchannel inbounds__//58 - We added a migrationstep, where we setthe errorchannelto “errorChannel”of all inboundsin a flow ifthecustomerrorhandling is settofalse.Before,the errorchannel wouldbeset to “errorChannel”onlyforthe firstinbound in anentry flow.72 +//__Deployment prechecks__// 73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 59 59 75 + 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 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"]] 80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 68 68 84 +== **Key Takeaways** == 69 69 70 -== **Key takeaways** == 71 - 72 72 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: 73 73 74 74 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -78,7 +78,6 @@ 78 78 * Check out the release notes [here] 79 79 * Start thinking about how the license tracker can aid your development 80 80 * Start thinking about major, minor, and patch 81 -* Upgrade to the latest build number 82 82 * Keep making great integrations 83 83 84 84 Let's stay in touch and till next time! ... ... @@ -86,6 +86,11 @@ 86 86 {{info}} 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 -~*~* Indicates a next-generation-architecture only feature. 90 -{{/info}})))((({{toc/}}))){{/container}} 102 +{{/info}} 103 +))) 104 + 105 +((( 106 +{{toc/}} 107 +))) 91 91 {{/container}} 109 +{{/container}}