Skip to Content

Changes for page 216 - Hack Heaven

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +205 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,71 @@
1 -The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
1 +{{container}}
2 +{{container layoutStyle="columns"}}(((
3 +[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
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.
4 4  
5 -=====New features=====
7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
6 6  
7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 -* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information, see the release blog post. (#815)
9 -* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench-shaped icon, which becomes available once a release is set as active.
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.
10 10  
11 -=====Minor changes=====
11 +== **Feedback Items** ==
12 12  
13 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 -* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
16 -* Manage - Error messages: Message history is sorted by timestamp descending.
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.
17 17  
18 -====Bug fixes====
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
19 19  
20 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 -* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 -* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
23 -* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
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.
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.
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.
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}}