Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
on 2024/01/29 14:48
Change comment:
There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2022/11/21 13:48
on 2022/11/21 13: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 - 213-JoyfulJourneys1 +188 - Close Encounters - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,94 +1,88 @@ 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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community. 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 +== **3rd generation runtime bolstering** == 11 11 12 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-213-joyful-journeys-property-release.png]]9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 13 13 14 -//__ Runtimedeletion__//15 -Wh endeletingaruntime, theerrormessagethat isdisplayedis moredescriptive.The error messages willnow includehenamesofheflows thatrun onthecontainer.11 +//__Migration of JMS backup configuration improved__// 12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime. 16 16 17 -//__ Wiretap&debugerror messages__//18 - Theerrormessagesthatmaybe displayedwhenusingwiretapsandthedebuggerave beenimproved,thesearenowmore userfriendly.14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 19 19 20 -//__A ctionmessages__//21 -Th e formatting of action messagesregardingchanges in retentionbytes/hourshasbeenimproved.Theactionmessagewillnowdisplay thecorrect, actualbehaviour.17 +//__Autogenerated exits can be deployed at once__// 18 +This release has fixed a bug that prevented you from deploying an exit flow correctly. 22 22 23 -== **Formatting & Alignments** == 20 +//__Code mapping functionality available on 3rd generation runtime__// 21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality. 24 24 25 -//__I nput fields__//26 - Multiple inputfieldshavebeen updatedsuchthat theyexpand whenthe amount ofcharactersexceedsthedefaultsize. Theseupdateswere donetocaterto largeexpressions.23 +//__Improved the performance when activating a release__// 24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release. 27 27 28 -//__ UIimprovements__//29 - UIimprovementsfor staticinputcomponents have beendone andthe tooltipfor optional/requiredtoggleshasbeenimproved.26 +//__Failing runtimes won't be restarted indefinitely anymore__// 27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped. 30 30 31 -//__Runtime overview image versions__// 32 -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. 29 +== **Exportable Release Audit** ~* == 33 33 34 -//__Component changes reversion__// 35 -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. 31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 36 36 37 -//__State generation statistics__// 38 -The state generation graphs will now show the correct number of cache hits and misses. 33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]] 39 39 40 -//__Queue browser timestamps__// 41 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 35 +{{warning}}Note that the following restrictions apply when exporting an audit document: 36 + * Works **only** for releases that are promoted and made active on **Production** 37 + * You will **only** see changes made during the **current** calendar year 38 + * On the first of April all objects of the **last** calendar year will be **removed**. 39 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}} 42 42 43 -//__Addition and deletion of internal recipients__// 44 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 41 +== **Feedback items ** == 45 45 46 - ==**FeedbackItems**==43 +We have also solved other feedback items besides the flow designer's critical updates. 47 47 48 -//__ Updateflows__//49 - In Create> Resources,abutton"Updateflows"hasbeenaddedtoupdateversions ofallflowsinwhicharesourceisused.45 +//__Improved naming convention on Store related pages__// 46 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 50 50 51 -//__ Q&Aforumsearch__//52 - Theoption tosearchby pressingtheEnterkeyhasbeenadded to theQ&Aforum.48 +//__Press "Enter" to search on multiple pages__// 49 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 53 53 54 -//__Memory settings__// 55 -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. 51 +* Deploy → Deployment Plan 52 +* Deploy → Properties → History 53 +* Deploy → User Management → Roles 54 +* Manage → Error Messages → Error Messages 55 +* Manage → Error Messages → Flows with Error Messages 56 +* Manage → Error Messages → Exceptions of Error Messages 57 +* Manage → Log Entries 58 +* Manage → Alerts 59 +* Manage → Triggers 60 +* Manage → Tags – Cant find (only Gen2) 61 +* Manage → Notifications 62 +* Manage → Notification Settings 63 +* Manage → Data Usage → History 64 +* Manage → Code mappings → All tabs 56 56 57 -//__Runtime validation__// 58 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 59 - 60 - 61 -== **Bug Fixes** == 62 - 63 -//__Removal of onramp__// 64 -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). 65 - 66 -//__Runtime statistics details__// 67 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 68 - 69 -//__Deployment prechecks__// 70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 71 - 72 - 73 73 == **Fancy Forum Answers** == 74 74 75 75 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: 76 76 77 -* [[ What istheeMagizcontrol tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]78 -* [[ Deletingconnector without flowsgiveserror>>https://my.emagiz.com/p/question/172825635703696657]]79 -* [[ Howtouse aflowtest withpath properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]70 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 71 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 72 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 80 80 81 -== **Key Takeaways** ==74 +== **Key takeaways** == 82 82 83 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:76 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 84 84 85 85 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 * If you have feedback or ideas for us, talk to the Platypus 87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 88 88 * Clear your browser cache (Ctrl + Shift + Del) 89 89 * Check out the release notes [here] 90 90 * Start thinking about how the license tracker can aid your development 91 91 * Start thinking about major, minor, and patch 85 +* Upgrade to the latest build number 92 92 * Keep making great integrations 93 93 94 94 Let's stay in touch and till next time! ... ... @@ -96,11 +96,6 @@ 96 96 {{info}} 97 97 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 98 98 99 -{{/info}} 100 -))) 101 - 102 -((( 103 -{{toc/}} 104 -))) 93 +~*~* Indicates a GEN3-only feature. 94 +{{/info}})))((({{toc/}}))){{/container}} 105 105 {{/container}} 106 -{{/container}}