Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+213 - Joyful Journeys

Content

...	...	@@ -1,69 +1,64 @@
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!** We have done .....
	6	+**Hi there, eMagiz developers!** This release ....
6	6
7		-{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}}
8	8
9		-== **Quicker Deployment Plan** ==
10		-We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
	9	+== **Feedback Items** ==
11	11
12		-== **Next Generation Architecture Default** ==
13		-With this release, the next generation architecture will become the default. New models will use this generation as default.
	11	+//__Property releases__//
	12	+When a new property release is created, this property release can now be viewed and deleted.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
	14	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
16	16
17		-== **Cloud Template R11 Docker - Single Lane** ==
18		-This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
	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.
19	19
20		-== **Cloud Template R13 Docker - Double Lane** ==
21		-This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
	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.
22	22
23		-== **Feedback Items** ==
	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.
24	24
25		-//__Unused properties overview__//
26		-In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
27		-* Not used by any runtime that is in the Create phase release.
28		-* Not required by a flow that is in the Create phase release.
29		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
	25	+//__Memory settings__//
	26	+It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
30	30
31		-//__Send build requests asynchronously__//
32		-The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	28	+//__Runtime validation__//
	29	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
33	33
34		-//__Queue explorer milliseconds__//
35		-The queue browser now displays milliseconds in the timestamps.
	31	+//__UI improvements__//
	32	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
36	36
37		-//__Cancel and next buttons order__//
38		-The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
	34	+//__Q&A forum search__//
	35	+The option to search by pressing the Enter key has been added to the Q&A forum.
39	39
40		-//__Unused images__//
41		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	37	+//__Wiretap & debug error messages__//
	38	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
42	42
43		-//__Carwash logging__//
44		-A new logging feature enabling us to make better choices in encryption standards will be released.
	40	+//__Runtime overview image versions__//
	41	+Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
45	45
46		-//__Static alerts queue consumers__//
47		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
48		-
49	49	== **Bug Fixes** ==
	44	+//__Action messages__//
	45	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
50	50
51		-//__Flow Designer connection line__//
52		-In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
	47	+//__Removal of onramp__//
	48	+We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
53	53
54		-//__Portal for migrated models__//
55		-We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	50	+//__Component changes reversion__//
	51	+In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
56	56
57		-//__Error channel inbounds__//
58		-We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
59		-
60	60	== **Fancy Forum Answers** ==
61	61
62	62	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:
63	63
64		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	57	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	58	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	59	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
65	65
66		-== **Key takeaways** ==
	61	+== **Key Takeaways** ==
67	67
68	68	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:
69	69
...	...	@@ -74,7 +74,6 @@
74	74	* Check out the release notes [here]
75	75	* Start thinking about how the license tracker can aid your development
76	76	* Start thinking about major, minor, and patch
77		-* Upgrade to the latest build number
78	78	* Keep making great integrations
79	79
80	80	Let's stay in touch and till next time!
...	...	@@ -82,6 +82,11 @@
82	82	{{info}}
83	83	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84	84
85		-~*~* Indicates a next-generation-architecture only feature.
86		-{{/info}})))((({{toc/}}))){{/container}}
	79	+{{/info}}
	80	+)))
	81	+
	82	+(((
	83	+{{toc/}}
	84	+)))
87	87	{{/container}}
	86	+{{/container}}