Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-195 - Easter Party
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,97 +1,92 @@
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 focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
	6	+**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
6	6
7		-== **Release properties** ==**
	8	+== **Pop-up Improvements** ==
8	8
9		-== **API improvements** ==
	10	+//__Property releases__//
	11	+When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
10	10
11		-//__Improved auto-generated error handling__//
12		-When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
13	13
14		-//__Switch default message format__//
15		-We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
	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.
16	16
17		-//__Re-using elements in gateway message__//
18		-This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
	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.
19	19
20		-//__Improved naming of API operations when adding integrations to Create__//
21		-Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
	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.
22	22
23		-== **3rd generation improvements** ==
	24	+== **Formatting & Alignments** ==
24	24
25		-//__Update of the static alerting engine__//
26		-In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
	26	+//__Input fields__//
	27	+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.
27	27
28		-//__Add "Data pipeline" functionality__//
29		-This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
	29	+//__UI improvements__//
	30	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
30	30
31		-//__Fix related to the debugger__//
32		-This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
	32	+//__Component changes reversion__//
	33	+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.
33	33
34		-{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
35	35
36		-//__Improved migration process__//
37		-This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
	38	+//__Queue browser timestamps__//
	39	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
38	38
39		-//__Deployment plan change__//
40		-In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
	41	+//__Addition and deletion of internal recipients__//
	42	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
41	41
42		-{{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}}
	44	+== **Feedback Items** ==
43	43
44		-== **Feedback items ** ==
	46	+//__Update flows__//
	47	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
45	45
46		-//__License Tracker improvements__//
47		-With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
	49	+//__Q&A forum search__//
	50	+The option to search by pressing the Enter key has been added to the Q&A forum.
48	48
49		-//__Ability to view the message definition for a topic__//
50		-Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
	52	+//__Memory settings__//
	53	+It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
	54	+//__Runtime validation__//
	55	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
51	51
52		-//__Restricted access for uploading custom certificates to endpoints__//
53		-To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
	57	+//__Runtime overview image versions__//
	58	+Insight into intended 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.
54	54
55		-== **Bug fixes ** ==
	60	+== **Bug Fixes** ==
56	56
57		-//__Improved deletion behavior for enumerations__//
58		-To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
	62	+//__Removal of onramp__//
	63	+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).
59	59
60		-//__Prevent "async" api operations__//
61		-With this release, we have removed the ability to select the "async" option when the default message format is API Management.
	65	+//__Runtime statistics details__//
	66	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
62	62
63		-//__Importing a response definition broke the request definition__//
64		-Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
	68	+//__Deployment prechecks__//
	69	+During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
65	65
66		-//__Removing a flow does not update the API "all-entry" anymore__//
67		-When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
68		-
69		-//__Stop deployment plan when a property is missing__//
70		-Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
71		-
72		-//__Cap stack trace of error messages and log entries__//
73		-To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
74		-
75	75	== **Fancy Forum Answers** ==
76	76
77	77	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:
78	78
79		-* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
80		-* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
81		-* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
	75	+* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
	76	+* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
	77	+* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
82	82
83		-== **Key takeaways** ==
	79	+== **Key Takeaways** ==
84	84
85		-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:
	81	+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:
86	86
87	87	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88	88	* If you have feedback or ideas for us, talk to the Platypus
89		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	85	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
90	90	* Clear your browser cache (Ctrl + Shift + Del)
91	91	* Check out the release notes [here]
92	92	* Start thinking about how the license tracker can aid your development
93	93	* Start thinking about major, minor, and patch
94		-* Upgrade to the latest build number
95	95	* Keep making great integrations
96	96
97	97	Let's stay in touch and till next time!
...	...	@@ -99,6 +99,11 @@
99	99	{{info}}
100	100	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
101	101
102		-~*~* Indicates a GEN3-only feature.
103		-{{/info}})))((({{toc/}}))){{/container}}
	97	+{{/info}}
	98	+)))
	99	+
	100	+(((
	101	+{{toc/}}
	102	+)))
104	104	{{/container}}
	104	+{{/container}}