Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
Change comment:
There is no comment for this version
To version 548.1
edited by CarlijnKokkeler
on 2024/06/03 16:00
on 2024/06/03 16:00
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 01-BeInformed1 +222 - Flee Frustration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,73 +1,59 @@ 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!** In the lastfew weeks, we have workedhardonplanning theupcomingQandfinishingupfeaturesofthelastQ.Moreonthat later.Ontop ofthatwe have several smalleritemsasa resultofourhackathon effortstopresent toyou.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! 6 6 7 -== **Announcement - Release Properties** == 8 -As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 9 - 10 -== ** Deploy Architecture - Apply To Environment improvements ** == 11 -As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 12 - 13 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 14 - 15 -== ** Breadcrumb navigation in eMagiz ** == 16 -With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel. 17 - 18 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 19 - 20 20 == **Feedback Items** == 9 +//__Cron triggers__// 10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 21 21 22 -//__Improved layout of catalog page in Design__// 23 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations. 12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 24 24 25 -//__ Improved layout of "Edit integration"pop-up for API Gateway integrations__//26 - Asofnowthefullpathofyourbackendsystemwill beshownwhenopeningthe"Edit integration"pop-uponyourAPI Gatewayintegration.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. 27 27 28 -//__Additional help texts on Design Architecture__// 29 -We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 30 30 31 -//__Improved Audit Trail on several places__// 32 -In several places in the portal we have improved the audit trail to better specify who changed what at which point in time. 19 +== **Bug Fixes** == 20 +//__Trigger activation__// 21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. 33 33 34 -//__ Removedtheerroneousalert on messagemappingwhen having a passthrough API__//35 - This releaseremovesthe erroneousalertpeople reportedon"errorsinmessagemapping"forapassthroughAPI.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. 36 36 37 - == **BugFixes**==26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 38 38 39 -//__ Avoidclicking on other components while deletinganother__//40 - Toavoid unexpectedbehavior wenowensurethatnothingcan be selectedonceyousee the"deletion"pop-upwhen you wantto remove somethingintheflowdesigner.28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 41 41 42 -//__ Improvedvalidation feedbackinmigrating tothenext-generationarchitecture__//43 - Wehave improvedseveral thingswithregardstothe validationfeedbackwhen migrating to thenext-generationarchitecture.31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 44 44 45 -//__M akesure that user credentials canbeviewed with viewrights__//46 -Th is releasemakes surethattheusercredentialsinDeploycan be viewedwithviewrightsand not onlywhenhavingedit rights.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 47 47 48 -//__Refresh behavior within the deployment plan is fixed__// 49 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 50 50 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||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"]] 58 58 59 -== **Key takeaways** ==46 +== **Key Takeaways** == 60 60 61 -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:48 +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: 62 62 63 63 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 * If you have feedback or ideas for us, talk to the Platypus 65 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 66 * Clear your browser cache (Ctrl + Shift + Del) 67 -* Check out the release notes [here] 54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 68 68 * Start thinking about how the license tracker can aid your development 69 69 * Start thinking about major, minor, and patch 70 -* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,6 +75,11 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -~*~* Indicates a GEN3-only feature. 79 -{{/info}})))((({{toc/}}))){{/container}} 64 +{{/info}} 65 +))) 66 + 67 +((( 68 +{{toc/}} 69 +))) 80 80 {{/container}} 71 +{{/container}}