Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 11:00
Change comment: There is no comment for this version
To version 101.1
edited by Erik Bakker
on 2023/08/03 16:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +202 - New Equilibrium
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,71 +1,40 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}(((
3 -[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
1 +In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
4 4  
5 -**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.202 - New Equilibrium.WebHome||target= "blank"]].
6 6  
7 -== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
5 +=====New features=====
8 8  
9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
7 +* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 +* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 +* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
10 10  
11 -== **Feedback Items** ==
12 +=====Minor changes=====
12 12  
13 -//__Improved Validation when migrating to the next-generation architecture__//
14 -To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
14 +* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 +* Deploy - Releases: The infographic has been updated.
16 +* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 +* Deploy - Property release: Names of properties can be created/removed/edited.
18 +* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 +* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966)
20 +* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
22 +====Bug fixes====
17 17  
18 -//__Improved HTTP Statistics__//
19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
24 +* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
25 +* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
26 +* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
27 +* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
28 +* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
29 +* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
30 +* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
31 +* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
32 +* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
33 +* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
34 +* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
20 20  
21 -//__Show values on the runtime level in Deploy Architecture__//
22 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
36 +=====Infra and image changes=====
23 23  
24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 -* JMS - The number of queues in the active release.
26 -* Messaging Container - The number of messaging integrations in the active release.
27 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 -* API Gateway Container - The number of operations in the active release.
29 -* Event Streaming Container - The number of event processors in the active release.
38 +* Runtime Image - Next-Generation Double Lane: A new runtime image is released including a Java version update. Please check out the runtime images [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for more information.
39 +* Infrastructure: Tightened security policies for a more secure infrastructure.
30 30  
31 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
32 -
33 -== **Bug Fixes** ==
34 -
35 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
37 -
38 -//__Ensure that differing container configurations deploy the correct configuration__//
39 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
40 -
41 -//__Remove queurying options in Manage__//
42 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
43 -
44 -== **Fancy Forum Answers** ==
45 -
46 -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:
47 -
48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
49 -
50 -== **Key takeaways** ==
51 -
52 -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:
53 -
54 -* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 -* If you have feedback or ideas for us, talk to the Platypus
56 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57 -* Clear your browser cache (Ctrl + Shift + Del)
58 -* Check out the release notes [here]
59 -* Start thinking about how the license tracker can aid your development
60 -* Start thinking about major, minor, and patch
61 -* Upgrade to the latest build number
62 -* Keep making great integrations
63 -
64 -Let's stay in touch and till next time!
65 -
66 -{{info}}
67 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 -
69 -~*~* Indicates a next-generation-architecture only feature.
70 -{{/info}})))((({{toc/}}))){{/container}}
71 -{{/container}}