Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 00-UnchartedTerritories1 +221 - Swift Shift - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,67 @@ 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 th elast fewweeks,wehaveworked hard on alot ofthingsthat areunfortunately notquitereadytobereleased.Asa resultthe outputofthis release is limited.Havingsaid thatwe still bring somekeyimprovementsin theDeployandManagephase thatwouldmakelife mucheasier.6 +**Hi there, eMagiz developers!** In this release, we improved the user interface for managing your failover and grouping configurations and improved the method for adding new attributes to data models. Next to this, we have improved the Event Catalog overview for Catalog users. Using the back button on the eMagiz Q&A now also brings you back to where you were with your search query. We also fixed some previous bugs, resulting in improved delete behavior for containers and correctly generated scope properties. Lastly, there will not be a warning message anymore when importing an XSD if there is no selected request or response message definition. 6 6 7 -== **Next generation improvements and bug fixes** == 8 +== **Feedback Items** == 9 +//__Q&A search__// 10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A. 8 8 9 -//__E nhanced right-handview withinDeploymentPlancontext__//10 - When executing yourdeploymentplan we will showspecific log entriesofthe infocategorythatindicate thatacontainer(i.e.runtime) has startedupcorrectly. Ontopof thatweshowthewarningsanderrorsinthisoverview.12 +//__Event catalog__// 13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 11 11 12 - {{info}}Note that when the JMS containergetsrestarted connection errorsin the logs area normal thing to witness so keep youreyespeeledforthestartuplogging on JMS level to gain confidence in the deployment.{{/info}}15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]] 13 13 14 -//__Improved timeout settings when deploying__// 15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur. 17 +//__Attribute placements__// 18 +Some improvements regarding the placement of attributes have been done: 19 +* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. 20 +* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with. 21 +* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. 16 16 17 - {{info}}Note that this fix is part of a new runtime imagefor the current-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]] 18 18 19 -//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 25 +//__Failover & grouping__// 26 +Some improvements regarding the widgets for failover and grouping have been done: 27 +* When executing a start/stop action on a group, the description of the step now contains the name of the group. 28 +* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 21 21 22 - {{info}}Note that this fix is part of a new runtime imagefor the next-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.Runtime Images.WebHome||target="blank"]]{{/info}}30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 23 23 24 -//__Improved loading speed of Manage Dashboard__// 25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 26 26 27 -== **Store Improvements** == 28 - 29 -//__Importing in Design is improved__// 30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 31 - 32 32 == **Bug Fixes** == 35 +//__XSD import__// 36 +When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion. 33 33 34 -//__Deprecated reminder pop-up removed__// 35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems. 38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 36 36 37 -//__ Improvedselectionarea in Flow Designer__//38 - Whenworking on alargeflowyoucan nowselectspecificareas easilywhileyouare scrolleddown furtherdown the flow.40 +//__Container deletion__// 41 +The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 39 39 40 -//__ Improved Kafka settings__//41 - For all flows that usea Kafka relatedcomponentwithintheflow designerwe will runamigrationtoupdate everysingleoneofthemtothenewbest practicesandcreateanew flow version forthem.43 +//__Scope properties__// 44 +We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme. 42 42 43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 44 - 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 50 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 51 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 52 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 51 51 52 -== **Key takeaways** ==54 +== **Key Takeaways** == 53 53 54 -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:56 +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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 60 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 -* Check out the release notes [here] 62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 72 +{{/info}} 73 +))) 74 + 75 +((( 76 +{{toc/}} 77 +))) 73 73 {{/container}} 79 +{{/container}}