Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+224 - Summer Sonata

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.dfirdausy

Content

...	...	@@ -1,67 +1,95 @@
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 the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
	6	+**Hi there, eMagiz developers!** In this release, we are bringing a significant performance improvement to flow testing, with execution times now accelerated by up to 3 times. Next to that, over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
6	6
7		-== **3rd generation improvements and bug fixes** ==
	8	+== **Faster Flow Testing** ==
8	8
9		-//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10		-Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed.
	10	+We are rolling out a major upgrade to flow testing performance, boosting execution speeds by up to three times. This enhancement will greatly accelerate your workflow when developing integrations, enabling you to run tests faster and more efficiently. Consequently, this will further support users for delivering higher-quality integrations.
11	11
12		-{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
	12	+== **Feedback Items** ==
	13	+//__Retention duration and bytes in Capture__//
	14	+The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
13	13
14		-//__Removed certain dependencies between Deploy Architecture and Releases__//
15		-In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
	16	+//__Help text panel in Capture__//
	17	+Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
16	16
17		-//__Improved validation errors on invalid configuration of HTTP outbound components__//
18		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	19	+//__Adding tags in Capture__//
	20	+In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon.
19	19
20		-//__Improved migration behavior__//
21		-This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
	22	+[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
22	22
23		-//__Improved auto-healing when running in a hybrid situation__//
24		-In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
	24	+//__Adding attributes for a message definition__//
	25	+We fixed an issue where your selected attributes were lost when navigating between paginations while adding more attributes to the entity in the pop-up shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model.
25	25
26		-//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
27		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	27	+//__Improved text in Design architecture__//
	28	+We fixed some spelling mistakes in the steps to be executed within the pop-up page when applying to environment in Design architecture.
	29	+
	30	+//__Property value page__//
	31	+Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page.
28	28
29		-{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
	33	+[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
30	30
31		-== **Feedback items ** ==
	35	+//__Password property__//
	36	+In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value.
32	32
33		-//__Make sure the message format can be viewed without "Start editing"__//
34		-With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
	38	+//__Enumeration values__//
	39	+When editing a message definition (i.e., a System Message, CDM, API Data Model, or Event Streaming Data Model) in the Flow designer within the Create phase, users can add enumeration values for attributes with an Enumeration data type. In this release, we’ve added a "Save and Add New" button to streamline the process of adding multiple enumeration values.
35	35
36		-//__Various styling improvements in the flow testing functionality__//
37		-Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
	41	+//__Helptext for HTTP methods__//
	42	+We improved the help text for the HTTP method field in the HTTP outbound gateway and HTTP outbound channel adapter flow components to provide clearer descriptions for different HTTP methods. Additionally, we implemented a validation for these components to prevent selecting the HTTP method 'PATCH' if an Apache HttpComponents REST template is not provided.
38	38
	44	+//__External links__//
	45	+Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab.
	46	+
	47	+//__Debugging Shortcut__//
	48	+Debugging a flow typically requires users to activate debug on a specific flow in Deploy → Containers, then navigate to Manage → Explore → Queue Browser and manually type in emagiz.debug. In this release, we have added a shortcut button that opens the Queue Browser page directly in the pop-up page right after activating debugging.
	49	+
	50	+[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
	51	+
	52	+{{html}}
	53	+<!-- Next to that, the Queue Browser page now includes a button to directly open the debugging queue, eliminating the need to manually type in emagiz.debug in the search box. -->
	54	+<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] -->
	55	+{{/html}}
	56	+
	57	+//__Test Message from Manage-Explore__//
	58	+Additionally, we have improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section.
	59	+
	60	+[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
	61	+
	62	+== **Bug Fixes** ==
	63	+
	64	+//__Event Processor Keystore and Trustore__//
	65	+
	66	+We fixed an issue where the keystore location and the truststore location were generated incorrectly when creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture.
	67	+
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
43		-* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
44		-* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
	72	+* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
45	45
46		-== **Key takeaways** ==
	74	+== **Key Takeaways** ==
47	47
48		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	76	+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:
49	49
50	50	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51	51	* If you have feedback or ideas for us, talk to the Platypus
52		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	80	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53	53	* Clear your browser cache (Ctrl + Shift + Del)
54		-* Check out the release notes [here]
	82	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
55	55	* Start thinking about how the license tracker can aid your development
56	56	* Start thinking about major, minor, and patch
57		-* Upgrade to the latest build number
58	58	* Keep making great integrations
59	59
60	60	Let's stay in touch and till next time!
61	61
62		-{{info}}
63		-~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	89	+)))
64	64
65		-~*~* Indicates a GEN3-only feature.
66		-{{/info}})))((({{toc/}}))){{/container}}
	91	+(((
	92	+{{toc/}}
	93	+)))
67	67	{{/container}}
	95	+{{/container}}