Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 574.31
edited by Danniar Firdausy
on 2024/07/01 17:13
on 2024/07/01 17:13
Change comment:
There is no comment for this version
To version 550.1
edited by Carlijn Kokkeler
on 2024/06/05 09:31
on 2024/06/05 09:31
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 -22 4-SummerSonata1 +222 - Flee Frustration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,62 +3,45 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Over the pastweek, wefocused onimprovingtheusabilityof ourplatformandaddressing communityfeedback.Specifically,we enhanced userinterface elements on severalpages, includingthedescriptionsofhelp texts,external linkswithin helptexts,andthe overalllayoutofhelp text pages.Additionally,wemade improvementstoseveralpop-uppages.We alsomadetheuserinterfacemore user-friendlyfor debuggingintegrationflows. Lastly,weresolved an issuefor somemodelswhencreatinganEventProcessor.6 +**Hi there, eMagiz developers!** This release, we have worked to allow cron triggers 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 8 == **Feedback Items** == 9 -//__ Retentiondurationand bytesin Capture__//10 - Thepop-up pageforspecifying integrationrequirementsinheCapturephasenowcorrectlyasks fortherequiredretentiondurationand bytes forthe integration/topic,insteadof thepreviouslyincorrectterms retention size andbytes.9 +//__Design changes__// 10 +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. 11 11 12 -//__Help text panel in Capture__// 13 -Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 12 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]] 14 14 15 -//__Adding tags in Capture__// 16 -In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 14 +== **Bug Fixes** == 15 +//__Cron triggers__// 16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 19 - 20 -//__Property value page__// 21 -Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page. 18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 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. 24 24 25 -//__ Improvedtextin Designarchitecture__//26 - Wefixedsomespellingmistakes in thepop-up pagewhenapplyingto environmentDesign architecture.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. 27 27 28 -//__Adding attributes for a message definition__// 29 -We fixed an issue where your selected attributes were lost when navigating between paginations while adding more attributes to the entity in the pop-up shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model. 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 30 30 31 -//__ HelptextforHTTP methods__//32 -We improved the help text for the HTTPmethod fieldin theHTTP outbound gatewayand HTTP outboundchanneldapter flow components to provideclearerdescriptionsfor differentHTTPmethods. Additionally, we implementedavalidationfor these components to preventselecting the HTTP method 'PATCH' ifn Apache HttpComponentsREST template is not provided.28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 33 33 34 -//__ Externallinks__//35 - Clicking links toxternaldocumentationin the eMagizportalisnowconfiguredtoalways openthe links inanewtab,ratherthanreplacingyourcurrenttab.31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 36 36 37 -//__ TestMessagefrom Manage-Explore__//38 - Weimprovedthenamesand descriptionsof testmessages that you savedwhen debuggingand wiretapping your integrationin theManage- Explorection.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 39 39 40 - <Screenshothere>37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 41 41 42 -//__Password property__// 43 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 44 - 45 -== **Bug Fixes** == 46 - 47 -//__Event Processor Keystore and Trustore__// 48 - 49 -We fixed an issue where the keystore location and the truststore location were generated incorrectly when creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture. 50 - 51 - 52 - 53 - 54 54 == **Fancy Forum Answers** == 55 55 56 56 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: 57 57 58 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 59 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 60 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 61 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||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"]] 62 62 63 63 == **Key Takeaways** == 64 64 ... ... @@ -68,7 +68,7 @@ 68 68 * If you have feedback or ideas for us, talk to the Platypus 69 69 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 70 70 * Clear your browser cache (Ctrl + Shift + Del) 71 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 3-IdyllicImage.WebHome||target="blank"]]54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 72 72 * Start thinking about how the license tracker can aid your development 73 73 * Start thinking about major, minor, and patch 74 74 * Keep making great integrations