Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 65.1
edited by Erik Bakker
on 2023/04/13 08:46
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 -195 - Easter Party
1 +205 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,30 +1,71 @@
1 -As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple 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.195 - Easter Party.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 -=====Minor changes=====
7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
6 6  
7 -* General - Control Tower: Changed several generic triggers for more predictable behavior.
8 -* Administration - License Tracker: The license tracker has been updated for new license models and features.
9 -* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
10 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
11 -* Design - API Gateway: Default HTTP responses are generated automatically (#417)
12 -* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
13 -* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
14 -* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
15 -* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
16 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
17 -* Deploy - Architecture: Certificates only editable by system admin.
18 -* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
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.
19 19  
20 -====Bug fixes====
11 +== **Feedback Items** ==
21 21  
22 -* General - Runtime Image: 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.V140.WebHome||target="blank"]].
23 -* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
24 -* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
25 -* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
26 -* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
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.
27 27  
28 -====Remarks====
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
29 29  
30 -* Deploy - Releases: We removed the existing snapshots of release property values.
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}}