Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+205 - World Explorers

Content

...	...	@@ -1,43 +1,71 @@
1		-In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}(((
	3	+[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
4	4
	7	+== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
5	5
6		-=====Minor changes=====
	9	+As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
7	7
8		-* Design - Framework: The framework used in the flow designer has been updated to the latest version.
9		-* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier.
10		-* Design - Store: 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.
11		-* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
12		-* Deploy - Architecture: The title of the'apply to environment' action for changing topic retention size has been changed to be less confusing.
13		-* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum.
14		-* Deploy - Deployment plan: A change in the memory settings of the JMS triggers a redeployment of the container.
15		-* Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
16		-* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
17		-* Deploy - Release properties: The description of a property can be changed by editing the property.
18		-* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
19		-* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
20		-* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
21		-* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment.
22		-* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
23		-* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes.
24		-* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default.
25		-* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
26		-* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform of the action.
27		-* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
	11	+== **Feedback Items** ==
28	28
	13	+//__Improved Validation when migrating to the next-generation architecture__//
	14	+To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
29	29
30		-====Bug fixes====
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
31	31
32		-* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33		-* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
34		-* Design - Store: We fixed an issue that static copies were missing when importing store items.
35		-* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
36		-* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release.
37		-* Manage - Monitoring: It is now possible to search on messages partially in Manage Monitoring.
38		-* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
	18	+//__Improved HTTP Statistics__//
	19	+To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
39	39
	21	+//__Show values on the runtime level in Deploy Architecture__//
	22	+We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
40	40
41		-=====Infra and image changes=====
	24	+{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
	25	+* JMS - The number of queues in the active release.
	26	+* Messaging Container - The number of messaging integrations in the active release.
	27	+* Messaging Connector - The number of messaging integrations related to this system in the active release.
	28	+* API Gateway Container - The number of operations in the active release.
	29	+* Event Streaming Container - The number of event processors in the active release.
42	42
43		-* No infra and/or image changes is this release.
	31	+There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	32	+
	33	+== **Bug Fixes** ==
	34	+
	35	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	36	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	37	+
	38	+//__Ensure that differing container configurations deploy the correct configuration__//
	39	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	40	+
	41	+//__Remove queurying options in Manage__//
	42	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
	43	+
	44	+== **Fancy Forum Answers** ==
	45	+
	46	+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:
	47	+
	48	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	49	+
	50	+== **Key takeaways** ==
	51	+
	52	+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:
	53	+
	54	+* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	55	+* If you have feedback or ideas for us, talk to the Platypus
	56	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	57	+* Clear your browser cache (Ctrl + Shift + Del)
	58	+* Check out the release notes [here]
	59	+* Start thinking about how the license tracker can aid your development
	60	+* Start thinking about major, minor, and patch
	61	+* Upgrade to the latest build number
	62	+* Keep making great integrations
	63	+
	64	+Let's stay in touch and till next time!
	65	+
	66	+{{info}}
	67	+~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	68	+
	69	+~*~* Indicates a next-generation-architecture only feature.
	70	+{{/info}})))((({{toc/}}))){{/container}}
	71	+{{/container}}