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,53 +1,63 @@
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 and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
	6	+**Hi there, eMagiz developers!** 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	+== **Feedback Items** ==
	9	+//__Retention duration and bytes in Capture__//
	10	+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.
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.
	12	+//__Help text panel in Capture__//
	13	+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.
	14	+
	15	+//__Property value page__//
	16	+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.
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}}
	18	+[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
13	13
14		-//__Improved efficiency in deploying a release__//
15		-This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
	20	+//__Improved text in Design architecture__//
	21	+We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture.
16	16
17		-//__Removed specific dependencies between Deploy Architecture and Releases__//
18		-In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
	23	+== **Bug Fixes** ==
	24	+//__Adding tags in Capture__//
	25	+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 validation errors on the invalid configuration of HTTP outbound components__//
21		-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.
	27	+[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
22	22
23		-//__Improved migration behavior__//
24		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25		-A smoother migration of your JMS (and backup JMS) process.
26		-Shortening of names that otherwise would be too long, additional feedback given to the user.
27		-Feedback when the migration process is finished.
	29	+//__External links__//
	30	+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.
28	28
29		-//__Additional checks when deploying__//
30		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
	32	+//__Adding attributes for a message definition__//
	33	+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.
31	31
	35	+//__Helptext for HTTP methods__//
	36	+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.
	37	+
	38	+//__Multipart/form-data HTTP request__//
	39	+The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
	40	+
32	32	== **Fancy Forum Answers** ==
33	33
34	34	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:
35	35
36		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	45	+* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
	46	+* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
	47	+* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
	48	+* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
38	38
39		-== **Key takeaways** ==
	50	+== **Key Takeaways** ==
40	40
41		-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:
	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:
42	42
43	43	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
44	44	* If you have feedback or ideas for us, talk to the Platypus
45		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	56	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46	46	* Clear your browser cache (Ctrl + Shift + Del)
47		-* Check out the release notes [here]
	58	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
48	48	* Start thinking about how the license tracker can aid your development
49	49	* Start thinking about major, minor, and patch
50		-* Upgrade to the latest build number
51	51	* Keep making great integrations
52	52
53	53	Let's stay in touch and till next time!
...	...	@@ -55,6 +55,11 @@
55	55	{{info}}
56	56	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57
58		-~*~* Indicates a GEN3-only feature.
59		-{{/info}})))((({{toc/}}))){{/container}}
	68	+{{/info}}
	69	+)))
	70	+
	71	+(((
	72	+{{toc/}}
	73	+)))
60	60	{{/container}}
	75	+{{/container}}