Changes for page 237 - Fabulous Flow

Summary

• Page properties (3 modified, 0 added, 0 removed)

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,34 +1,71 @@
1		-As a quarter has come to a close we went silent for a couple of weeks to plan ahead 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 good spirit after solving several smaller feedback items and bugs reported by you. In this and the upcoming release several of those stories will be included. On top of that we introduce various improvements to our API Gateway pattern and to our 3rd generation runtime architecture. 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.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		-=====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.V131.WebHome||target="blank"]].
8		-* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers, and waking up a cloud slot will start those containers. (#889)
	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.
9	9
10		-=====Minor changes=====
	11	+== **Feedback Items** ==
11	11
12		-* Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.
13		-* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you use custom error handling on your event processors.
14		-* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
15		-* Deploy - User Management: Roles are sorted alphabetically. (#806)
16		-* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
17		-* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements.
18		-* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
	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.
19	19
20		-====Bug fixes====
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
21	21
22		-* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
23		-* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
24		-* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
25		-* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
26		-* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
27		-* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
28		-* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet it occurred (#825)
29		-* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
30		-* Manage - Alerting: Editable column shows the correct value.
	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.
31	31
32		-====Remarks====
	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.
33	33
34		-* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours because of data migration. You will get an error stating that the version is incompatible with the selected feature until the migration is finished.
	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}}