Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+225 - TBD

Author

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

Content

...	...	@@ -1,73 +1,86 @@
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 planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Announcement - Release Properties** ==
8		-As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9	9
10		-== ** Deploy Architecture - Apply To Environment improvements ** ==
11		-As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
	9	+== **Feedback Items** ==
	10	+//__Alerting notification settings__//
	11	+The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
14	14
15		-== ** Breadcrumb navigation in eMagiz ** ==
16		-This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
	15	+//__Process containers__//
	16	+If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
17	17
18		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
	18	+//__Design settings__//
	19	+When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
19	19
20		-== **Feedback Items** ==
	21	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
21	21
22		-//__Improved layout of catalog page in Design__//
23		-We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
	23	+//__Untested images__//
	24	+ A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
	25	+
	26	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
24	24
25		-//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26		-Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
	28	+//__Infinispan Cache Manager__//
	29	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	30	+
	31	+//__Infinispan Cache Manager error message__//
	32	+We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
27	27
28		-//__Additional help texts on Design Architecture__//
29		-We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
	34	+//__Flow bump__//
	35	+When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
	36	+
	37	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
30	30
31		-//__Improved Audit Trail on several places__//
32		-In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
	39	+//__Unused support objects__//
	40	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
33	33
34		-//__Removed the erroneous alert on message mapping when having a passthrough API__//
35		-This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
	42	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	43	+
	44	+//__Deleting routes__//
	45	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
36	36
	47	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
	48	+
	49	+//__Debug queue__//
	50	+The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
	51	+
	52	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	53	+
37	37	== **Bug Fixes** ==
	55	+//__Internal server error__//
	56	+The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
38	38
39		-//__Avoid clicking on other components while deleting another__//
40		-To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
	58	+//__Namespace update__//
	59	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
41	41
42		-//__Improved validation feedback in migrating to the next-generation architecture__//
43		-We have improved the validation feedback when migrating to the next-generation architecture.
	61	+//__Error pop-up__//
	62	+We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
44	44
45		-//__Make sure that user credentials can be viewed with view rights__//
46		-This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
	64	+//__SMB inbound channel adapter__//
	65	+The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again.
47	47
48		-//__Refresh behavior within the deployment plan is fixed__//
49		-This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
50		-
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
55		-* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56		-* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57		-* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
	71	+* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
58	58
59		-== **Key takeaways** ==
	73	+== **Key Takeaways** ==
60	60
61		-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:
	75	+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:
62	62
63	63	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64	* If you have feedback or ideas for us, talk to the Platypus
65		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	79	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66	66	* Clear your browser cache (Ctrl + Shift + Del)
67		-* Check out the release notes [here]
	81	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a GEN3-only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	91	+{{/info}}
	92	+)))
	93	+
	94	+(((
	95	+{{toc/}}
	96	+)))
80	80	{{/container}}
	98	+{{/container}}