Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-261 - Taking Charge
	1	+205 - World Explorers

Author

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

Content

...	...	@@ -1,43 +1,71 @@
1		-This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that update a multitude of configurations on cloud and on-premises machines. Furthermore, we have a series of smaller improvements to enhance your everyday work.
	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>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.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
5		-==== New Features ====
	7	+== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
6	6
7		-* API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply:
8		-** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
9		-** Clients that obtain an access token with an authorization code will also obtain a //refresh token//, which can be used to obtain a subsequent access token without user intervention. This refresh token is valid for **24 hours**, meaning the client application must call the eMagiz API gateway at least that often; otherwise, manual intervention is needed to authorize the call again.
	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.
10	10
11		-==== Major changes ====
	11	+== **Feedback Items** ==
12	12
13		-* Deploy -> Architecture (Upgrade): The authorization server has been incorporated into the environment template. The first deployment will happen in Deploy > Architecture. All infra-side updates will be covered within the environment upgrade.
14		-* Deploy -> Architecture (Upgrade): Double lane models can now upgrade to an intermediate environment template first, before upgrading to the final template in case of a service-impacting template. This allows us to verify that all containers in the backup zone are running properly before the final, service-affecting template is applied.
	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.
15	15
16		-==== Minor changes ====
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
17	17
18		-* Generic -> Authorization Server: Improved security headers of the endpoints of eMagiz-hosted authorization servers.
19		-* Design -> Security: Removed the security setting button from the API Gateway catalog. You can still access the settings from the design overview.
20		-* Deploy: All pop-ups showing important information, like a key, secret, or password, are structured so that the data is visualised and can be copied by the user when the “show data” action button is utilised. (#1735)
21		-* Deploy -> User Management: Any reference to a URL related to the authorization server is now shown, including ‘https://'.
22		-* Deploy -> Architecture: Endpoint URL for routes is available on the view/edit pop-up of specific routes on the Deploy architecture. Additionally, the construction of how it is provided as a help text, and this feature is only available for the AWS model. (#792)
23		-* Manage -> Monitoring (HTTP Statistics): The details page will now show the display name of the user that initiated a request instead of the Id. Note: For this change to be applied to your environment, you need to adhere to the following requirements:
24		-** The MAM API-Gateway migration must be completed
25		-** You must be running on the latest environment template
26		-*** Single lane: R18
27		-*** Double lane: R20
28		-*** The gateway container must be deployed with the latest eMagiz runtime (version 3.5.0 or up)
	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.
29	29
30		-==== Bug fixes ====
	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.
31	31
32		-* Generic: System display names in all phases are updated progressively with the change in the Capture phase. All other places where the system display name was allowed to be changed are now disallowed, and changes can only be made from Capture. (#449)
33		-* Design - System Message: After successfully importing an OpenAPI file in the system request/response message, the user remains on the same page. (#1308)
34		-* Design - System (Failover): When you identify a system as a failover and subsequently create the integration on that system, you do not need to push multiple versions anymore before you can deploy your release.
35		-* Design - Architecture: We inform the user via the History overview when an overwrite action is triggered in the test environment for their model upon request. (#1697)
36		-* Create - Flow Designer: The help text of the XPath expression field on the XPath splitter is updated. (#1467)
37		-* Create - Transformation: Users can mark all XPath expressions as checked by a button in the transformation page. This button will remove only the warnings that come with the import from store feature, and will delete only those with an XPath expression.
38		-* Create - Add Integrations: When creating a new event processor with JSON as input and XML as output, this configuration is reflected in the generated flow in Create after transfer. Now the message format is automatically recognized and handled correctly, similar to API Gateway operations.
39		-* Deploy - Architecture (Start/Stop Flows): Your search phrase when searching for “component names” in this overview can now contain special characters present in the technical name of your inbound component(s). (#1639)
	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.
40	40
41		-==== Remarks ====
	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}}
42	42
43		-* Generic: When retrieving information from our infrastructure about available customer agents, we improved performance by reducing the amount of data we retrieve and process.
	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}}