Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Giant Leap
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,82 +1,97 @@
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 around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
	6	+**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved.
6	6
7		-== **3rd generation improvements** ==
8	8
9		-//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	9	+== **Pop-up Improvements** ==
	10	+//__Property releases__//
	11	+When a new property release is created, this property release can now be viewed and deleted.
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
	15	+//__Runtime deletion__//
	16	+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.
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
	18	+//__Wiretap & debug error messages__//
	19	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
	21	+//__Action messages__//
	22	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
	25	+== **Formatting & Alignments** ==
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
	27	+//__Input fields__//
	28	+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.
32	32
33		-//__Improved help text for network volumes__//
34		-With this release, we have improved the help text that explains network volumes and how to use them within our solution.
	30	+//__UI improvements__//
	31	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	33	+//__Runtime overview image versions__//
	34	+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.
37	37
38		-== **Feedback items ** ==
	36	+//__Component changes reversion__//
	37	+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.
39	39
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
	39	+//__State generation statistics__//
	40	+The state generation graphs will now show the correct number of cache hits and misses.
42	42
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
	42	+//__Queue browser timestamps__//
	43	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
45	45
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
	45	+//__Addition and deletion of internal recipients__//
	46	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
48	48
49		-//__Improved Topic calculations in Design Architecture__//
50		-Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level.
51	51
52		-== **Bug fixes ** ==
	49	+== **Feedback Items** ==
53	53
54		-//__Consolidated upgrade process cloud template__//
55		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
	51	+//__Update flows__//
	52	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
56	56
57		-//__Ensure users can deploy release on environments they have edit rights on__//
58		-Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	54	+//__Q&A forum search__//
	55	+The option to search by pressing the Enter key has been added to the Q&A forum.
59	59
	57	+//__Memory settings__//
	58	+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.
	59	+
	60	+//__Runtime validation__//
	61	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	62	+
	63	+
	64	+== **Bug Fixes** ==
	65	+
	66	+//__Removal of onramp__//
	67	+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).
	68	+
	69	+//__Runtime statistics details__//
	70	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
	71	+
	72	+//__Deployment prechecks__//
	73	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
	74	+
	75	+
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		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
65		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
66		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	80	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	81	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	82	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
67	67
68		-== **Key takeaways** ==
	84	+== **Key Takeaways** ==
69	69
70		-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:
	86	+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:
71	71
72	72	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73	73	* If you have feedback or ideas for us, talk to the Platypus
74		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	90	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75	75	* Clear your browser cache (Ctrl + Shift + Del)
76	76	* Check out the release notes [here]
77	77	* Start thinking about how the license tracker can aid your development
78	78	* Start thinking about major, minor, and patch
79		-* Upgrade to the latest build number
80	80	* Keep making great integrations
81	81
82	82	Let's stay in touch and till next time!
...	...	@@ -84,6 +84,11 @@
84	84	{{info}}
85	85	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86	86
87		-~*~* Indicates a GEN3-only feature.
88		-{{/info}})))((({{toc/}}))){{/container}}
	102	+{{/info}}
	103	+)))
	104	+
	105	+(((
	106	+{{toc/}}
	107	+)))
89	89	{{/container}}
	109	+{{/container}}