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	+206 - Situational Deployment

Author

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

Content

...	...	@@ -2,101 +2,107 @@
2	2	{{container layoutStyle="columns"}}(((
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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **Release properties** ==**
	7	+== **Deployment Plan** ==
8	8
9		-With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
	9	+//__Improved deployment plan to make the process better and more predictable__//
	10	+The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
10	10
11		-As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
12	12
13		-{{info}}The following considerations need to be taken into account when using this functionality:
14		-* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
15		-* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
16		-* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
17		-*{{/info}}
	15	+//__JMS memory setting check__//
	16	+A change in memory settings triggers redeployment of the container now.
18	18
19		-== **API improvements** ==
	18	+//__Properties tab__//
	19	+We have removed the deprecated tab Properties in the Deploy phase.
20	20
21		-//__Improved auto-generated error handling__//
22		-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.
	21	+//__Cleanup old images__//
	22	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
23	23
24		-//__Switch default message format__//
25		-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.
	24	+//__Performance improvements for loading releases__//
	25	+Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
26	26
27		-//__Re-using elements in gateway message__//
28		-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.
	27	+== **Store Improvements** ==
29	29
30		-//__Improved naming of API operations when adding integrations to Create__//
31		-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.
	29	+//__Message definition elements order__//
	30	+We fixed an issue that the order of message definition elements was changed after being imported.
32	32
33		-== **3rd generation improvements** ==
	32	+//__Improting a store item with synchronous message definitions__//
	33	+We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
34	34
35		-//__Update of the static alerting engine__//
36		-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.
	35	+//__Importing store items containing static copies__//
	36	+We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
37	37
38		-//__Add "Data pipeline" functionality__//
39		-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.
	38	+//__Importing Store content__//
	39	+We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
40	40
41		-//__Fix related to the debugger__//
42		-This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
	41	+== **Feedback Items** ==
43	43
44		-{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
	43	+//__Alerting manual pause__//
	44	+A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
45	45
46		-//__Improved migration process__//
47		-This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
	46	+//__Ordering of graphs in Manage__//
	47	+The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
48	48
49		-//__Deployment plan change__//
50		-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.
	49	+//__UTC times in Grafana panels__//
	50	+All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
51	51
52		-{{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}}
	52	+//__Update flow designer version__//
	53	+The framework used in the flow designer has been updated to the latest version.
53	53
54		-== **Feedback items ** ==
	55	+//__Carwash track TLS versions in logging__//
	56	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
55	55
56		-//__License Tracker improvements__//
57		-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.
	58	+//__Moving channels in the flow designer__//
	59	+Moving already attached channels in the flow designer has been made sligthly easier.
58	58
59		-//__Ability to view the message definition for a topic__//
60		-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.
	61	+//__Topic sizes description change__//
	62	+In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
61	61
62		-//__Restricted access for uploading custom certificates to endpoints__//
63		-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.
	64	+//__Password change notification__//
	65	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
64	64
65		-== **Bug fixes ** ==
	67	+//__Password comparison__//
	68	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
66	66
67		-//__Improved deletion behavior for enumerations__//
68		-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.
	70	+//__Inactive user alerting__//
	71	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
69	69
70		-//__Prevent "async" api operations__//
71		-With this release, we have removed the ability to select the "async" option when the default message format is API Management.
	73	+//__Alphabetical sorting on user level in HTTP statistics__//
	74	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
72	72
73		-//__Importing a response definition broke the request definition__//
74		-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.
	76	+//__SOAP Web services path__//
	77	+Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
75	75
76		-//__Removing a flow does not update the API "all-entry" anymore__//
77		-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.
	79	+== **Bug Fixes** ==
78	78
79		-//__Stop deployment plan when a property is missing__//
80		-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.
	81	+//__Flow designer styling__//
	82	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
81	81
82		-//__Cap stack trace of error messages and log entries__//
83		-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.
	84	+//__Partial search for messages__//
	85	+It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
84	84
	87	+//__Disk usage after cloud template update__//
	88	+In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
	89	+
	90	+//__Error handling migration__//
	91	+If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
	92	+
85	85	== **Fancy Forum Answers** ==
86	86
87	87	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:
88	88
89		-* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
90		-* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
91		-* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
	97	+* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
92	92
93	93	== **Key takeaways** ==
94	94
95		-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:
	101	+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:
96	96
97	97	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98	98	* If you have feedback or ideas for us, talk to the Platypus
99		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	105	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
100	100	* Clear your browser cache (Ctrl + Shift + Del)
101	101	* Check out the release notes [here]
102	102	* Start thinking about how the license tracker can aid your development
...	...	@@ -109,6 +109,6 @@
109	109	{{info}}
110	110	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111	111
112		-~*~* Indicates a GEN3-only feature.
	118	+~*~* Indicates a next-generation-architecture only feature.
113	113	{{/info}})))((({{toc/}}))){{/container}}
114	114	{{/container}}