Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-224 - Summer Sonata
	1	+206 - Situational Deployment

Author

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

Content

...	...	@@ -1,77 +1,79 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
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 up to three 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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
7	7
8		-== **Faster Flow Testing** ==
	7	+== **Deployment Plan** ==
9	9
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.
	9	+//__Improved deployment plan to make the process better and more predictable__//
	10	+The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
11	11
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.
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
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.
	15	+//__JMS memory setting check__//
	16	+A change in memory settings triggers redeployment of the container now.
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.
	18	+//__Properties tab__//
	19	+We have removed the deprecated tab Properties in the Deploy phase.
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
	21	+//__Cleanup old images__//
	22	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
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.
	24	+//__Performance improvements for loading releases__//
	25	+Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
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.
	27	+== **Store Improvements** ==
32	32
33		-[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
	29	+//__Message definition elements order__//
	30	+We fixed an issue that the orders of message definition’s elements were changed after they were imported.
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.
	32	+//__Message definition elements order__//
	33	+We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
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.
	35	+== **Feedback Items** ==
40	40
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.
	37	+//__Alerting manual pause__//
	38	+A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
43	43
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.
	40	+//__Ordering of graphs in Manage__//
	41	+The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
49	49
50		-[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
	43	+//__UTC times in Grafana panels__//
	44	+All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
51	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}}
	46	+//__Update flow designer version__//
	47	+The framework used in the flow designer has been updated to the latest version.
56	56
57		-//__Test Message from Manage-Explore__//
58		-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.
	49	+//__Carwash track TLS versions in logging__//
	50	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
59	59
60		-[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
	52	+//__Moving channels in the flow designer__//
	53	+Moving already attached channels in the flow designer has been made sligthly easier.
61	61
62		-== **Bug Fixes** ==
	55	+//__Topic sizes description change__//
	56	+In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
63	63
64		-//__Event Processor Keystore and Trustore__//
	58	+//__Password change notification__//
	59	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
65	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.
	61	+//__Password comparison__//
	62	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
67	67
	64	+
	65	+== **Bug Fixes** ==
	66	+
	67	+//__Flow designer styling__//
	68	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
	69	+
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
	74	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
73	73
74		-== **Key Takeaways** ==
	76	+== **Key takeaways** ==
75	75
76	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:
77	77
...	...	@@ -79,9 +79,10 @@
79	79	* If you have feedback or ideas for us, talk to the Platypus
80	80	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81	81	* Clear your browser cache (Ctrl + Shift + Del)
82		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
	84	+* Check out the release notes [here]
83	83	* Start thinking about how the license tracker can aid your development
84	84	* Start thinking about major, minor, and patch
	87	+* Upgrade to the latest build number
85	85	* Keep making great integrations
86	86
87	87	Let's stay in touch and till next time!
...	...	@@ -89,11 +89,6 @@
89	89	{{info}}
90	90	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91	91
92		-{{/info}}
93		-)))
94		-
95		-(((
96		-{{toc/}}
97		-)))
	95	+~*~* Indicates a next-generation-architecture only feature.
	96	+{{/info}})))((({{toc/}}))){{/container}}
98	98	{{/container}}
99		-{{/container}}