Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-225 - TBD
	1	+227 - Fix Frenzy

Content

...	...	@@ -3,76 +3,58 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, we are bringing a significant performance improvement to flow testing, with execution times now accelerated by at least three times faster, and up to five times faster. 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	+**Hi there, eMagiz developers!**
7	7
8		-== **Faster Flow Testing** ==
9		-
10		-We are rolling out a major upgrade to flow testing performance, boosting execution speeds by at least three times faster, and up to five times faster. 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		-
12	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.
	9	+//__Start/stop flows search__//
	10	+The user is now able to search in the Start/Stop flows overview.
15	15
16		-//__Help text panel in Capture__//
17		-Collapsing the help text of this pop-up page by clicking the "i" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
	12	+[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
18	18
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.
	14	+//__Tracing information__//
	15	+The tracing information for errorChannel messages in flow test traces has been improved.
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
	17	+[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
23	23
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.
26	26
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.
32	32
33		-[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
	21	+== **Bug Fixes** ==
	22	+//__Update namespace resources__//
	23	+The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes on your namespaces in your message definitions.
34	34
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.
	25	+//__Queue triggers hybrid models__//
	26	+We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
37	37
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.
	28	+//__Internal/External recipients__//
	29	+You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly. Cases where this was applied incorrectly have been automatically fixed.
40	40
41		-//__Editing Flow Resource__//
42		-While editing a flow in Create, if users attempt to modify a resource that is used by multiple flows, they will now see a warning indicating that this resource is shared and that all flows using it may need to be updated.
	31	+//__Tenant queue trigger__//
	32	+We have fixed a case where a tenant queue trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
43	43
44		-//__Helptext for HTTP methods__//
45		-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.
	34	+//__Area selector__//
	35	+We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
46	46
47		-//__External links__//
48		-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.
49		-
50		-//__Debugging Shortcut__//
51		-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.
	37	+//__Runtime overview__//
	38	+The runtime overview will now always display the correct container version.
52	52
53		-[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
	40	+//__List of flows__//
	41	+We fixed a bug where runtimes that did not appear in the list of flows of the deployment plan were restarted anyway.
54	54
55		-{{html}}
56		-<!-- 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. -->
57		-<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] -->
58		-{{/html}}
	43	+//__Deploy prevention__//
	44	+When moving to Deploy phase for the first time, a background action could fail, which would prevent deploying a release. This has been resolved.
59	59
60		-//__Test Message from Manage-Explore__//
61		-Additionally, we have improved the name and description of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section.
	46	+//__Cancel button__//
	47	+The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
62	62
63		-[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
	49	+//__Log test execution__//
	50	+In case opening a log of test execution is not possible in flow testing, a warning message will now be shown.
64	64
65		-== **Bug Fixes** ==
66		-
67		-//__Event Processor Keystore and Trustore__//
68		-
69		-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.
70		-
71	71	== **Fancy Forum Answers** ==
72	72
73	73	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:
74	74
75		-* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
	56	+* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
	57	+* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
76	76
77	77	== **Key Takeaways** ==
78	78
...	...	@@ -82,7 +82,7 @@
82	82	* If you have feedback or ideas for us, talk to the Platypus
83	83	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84	84	* Clear your browser cache (Ctrl + Shift + Del)
85		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
	67	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
86	86	* Start thinking about how the license tracker can aid your development
87	87	* Start thinking about major, minor, and patch
88	88	* Keep making great integrations