Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 148.1
edited by Erik Bakker
on 2023/08/15 13:54
on 2023/08/15 13:54
Change comment:
There is no comment for this version
To version 540.1
edited by CarlijnKokkeler
on 2024/06/03 13:04
on 2024/06/03 13:04
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 03- FastPaced1 +222 - Flee Frustration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,49 +1,52 @@ 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!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Release Properties - Early Feedback** == 8 -The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties. 9 - 10 10 == **Feedback Items** == 9 +//__Cron triggers__// 10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before. 11 11 12 -//__"All entries" are now cleaned up as part of the migration__// 13 -To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture. 12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 14 14 15 -//__ Trigger IDadded to our alertingonthenext-generation architecture__//16 - WeaddedauniquetriggerID toeachalertconfigurationto maketheinterpretationfor oursupportdeskmucheasier andmoremanageable.14 +//__Design changes__// 15 +If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture. 17 17 18 -//__Improved performance Manage Dashboards__// 19 -We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture. 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 20 20 21 21 == **Bug Fixes** == 20 +//__Trigger activation__// 21 +Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed. 22 22 23 -//__ Ensure no flow can bein a releasetwice__//24 - Wehavefixedabugthatcouldcauseoneflow to endup inthe samerelease withtwodifferentflow versions. Asthis will breakyoursolutiononvarious occasions,we fixedthis.23 +//__Multiple users deploying__// 24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. 25 25 26 -//__Sped up adding a new operation to the API Gateway solution__// 27 -We have fixed a bug that slowed down the addition of new operations to the API Gateway solution. 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 28 28 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 30 + 29 29 == **Fancy Forum Answers** == 30 30 31 31 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: 32 32 33 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 35 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 36 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 37 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 34 34 35 -== **Key takeaways** ==39 +== **Key Takeaways** == 36 36 37 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:41 +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: 38 38 39 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 40 40 * If you have feedback or ideas for us, talk to the Platypus 41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 45 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 42 42 * Clear your browser cache (Ctrl + Shift + Del) 43 -* Check out the release notes [here] 47 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 44 44 * Start thinking about how the license tracker can aid your development 45 45 * Start thinking about major, minor, and patch 46 -* Upgrade to the latest build number 47 47 * Keep making great integrations 48 48 49 49 Let's stay in touch and till next time! ... ... @@ -51,6 +51,11 @@ 51 51 {{info}} 52 52 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 54 -~*~* Indicates a next-generation-architecture only feature. 55 -{{/info}})))((({{toc/}}))){{/container}} 57 +{{/info}} 58 +))) 59 + 60 +((( 61 +{{toc/}} 62 +))) 56 56 {{/container}} 64 +{{/container}}