Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 574.5
edited by Danniar Firdausy
on 2024/07/01 13:57
on 2024/07/01 13:57
Change comment:
There is no comment for this version
To version 574.7
edited by Danniar Firdausy
on 2024/07/01 14:28
on 2024/07/01 14:28
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,11 +3,11 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Inthe past week, we focused oureffort toimprovethe usability of our platform aswellas addressingfeedback we received fromthe community.Morespecifically, weimproved user interfaceissues on several pagesthat are revolvingaroundthe description of help texts, external links inthehelp texts, thepage layoutsof help texts,aswell asimprovements onsome pop-up pages.Nexttothat<mentionimprovementsondebugginghere, EZ-18118andEZ-18285>.Finally, wealsofixed an issueofincorrectlygenerated resourcepathsof Keystores andTrustores when creating an Event Processorfor models that got migrated from the legacy runtime architecture to the current generation architecture.6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor. 7 7 8 8 == **Feedback Items** == 9 -//__ SwaggerUIdefault__//10 - Modelcontactsarenowable toselectadefaultSwaggerUIenvironment fromtheAPI managementsettingsin theDesignphase.Theenvironment selected herewillbe thefirstand thedefaultvaluefSwaggerUIserverdropdown.9 +//__Retention time and bytes requirements__// 10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes. 11 11 12 12 [[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 13 13