Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 414.1
edited by Carlijn Kokkeler
on 2024/03/25 11:06
on 2024/03/25 11:06
Change comment:
There is no comment for this version
To version 545.1
edited by Carlijn Kokkeler
on 2024/06/03 13:27
on 2024/06/03 13:27
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 17-TemplateTango1 +222 - Flee Frustration - Content
-
... ... @@ -3,41 +3,45 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 6 +**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes! 7 7 8 -== **Cloud Template R12 Docker - Single Lane** == 9 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here. 10 - 11 -== **Cloud Template R14 Docker - Double Lane** == 12 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here. 13 - 14 14 == **Feedback Items** == 15 -//__C ustomtrigger__//16 - The genericalerttrigger"Morethan100messagesonqueue over 10minutes"hasbeenmigratedtoacustomtriggerfor eachmodel andenvironment,allowing users to editthis trigger.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. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-2 17-template-tango-custom-trigger.png]]12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 19 19 20 -//__ Copytoclipboard buttons__//21 - Copytoclipboardbuttonsare addedtovarious pages: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. 22 22 23 - * Deploy agent pop-up 24 - * Create - Flow designer: Properties 25 - * Deploy - Property releases: Property details 26 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 27 - 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 18 + 28 28 == **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. 29 29 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. 30 30 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 31 31 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 30 + 31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 33 + 34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 36 + 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 38 + 32 32 == **Fancy Forum Answers** == 33 33 34 34 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: 35 35 36 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 37 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 38 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 39 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 40 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 41 41 42 42 == **Key Takeaways** == 43 43 ... ... @@ -47,7 +47,7 @@ 47 47 * If you have feedback or ideas for us, talk to the Platypus 48 48 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 49 * Clear your browser cache (Ctrl + Shift + Del) 50 -* Check out the release notes [here] 54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 51 51 * Start thinking about how the license tracker can aid your development 52 52 * Start thinking about major, minor, and patch 53 53 * Keep making great integrations