Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-192 - Small Step
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,70 +1,50 @@
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 couple of weeks, we worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
	6	+**Hi there, eMagiz developers!** This release ....
6	6
7		-== **Start/Stop Flows** ~*~* ==
8	8
9		-{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
	9	+== **Feedback Items** ==
10	10
11		-To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
	11	+//__Property releases__//
	12	+When a new property release is created, this property release can now be viewed and deleted.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
	14	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14	14
15		-After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
	16	+//__Runtime deletion__//
	17	+When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
	19	+//__Update flows__//
	20	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
18	18
19		-{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
	22	+//__Input fields__//
	23	+Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
20	20
21		-== **Manage overview Event Streaming** ~*~* ==
	25	+== **Bug Fixes** ==
22	22
23		-To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
26	26
27		-== **Feedback items ** ==
28		-
29		-We have also solved other feedback items besides the flow designer's critical updates.
30		-
31		-//__Topic configuration calculation__//
32		-With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
33		-
34		-//__Make preparation step in deployment plan visible__//
35		-For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
36		-
37		-{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
38		-
39		-//__3rd generation runtime debugger feedback__//
40		-We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
41		-
42		-//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43		-As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
44		-
45		-//__User Management synchronization now happens in one step__//
46		-With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
47		-
48	48	== **Fancy Forum Answers** ==
49	49
50	50	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:
51	51
52		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53		-* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54		-* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
	33	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	34	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	35	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
55	55
56		-== **Key takeaways** ==
	37	+== **Key Takeaways** ==
57	57
58		-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:
	39	+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:
59	59
60	60	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61	* If you have feedback or ideas for us, talk to the Platypus
62		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	43	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63	63	* Clear your browser cache (Ctrl + Shift + Del)
64	64	* Check out the release notes [here]
65	65	* Start thinking about how the license tracker can aid your development
66	66	* Start thinking about major, minor, and patch
67		-* Upgrade to the latest build number
68	68	* Keep making great integrations
69	69
70	70	Let's stay in touch and till next time!
...	...	@@ -72,6 +72,11 @@
72	72	{{info}}
73	73	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74
75		-~*~* Indicates a GEN3-only feature.
76		-{{/info}})))((({{toc/}}))){{/container}}
	55	+{{/info}}
	56	+)))
	57	+
	58	+(((
	59	+{{toc/}}
	60	+)))
77	77	{{/container}}
	62	+{{/container}}