Changes for page 194 - Giant Leap

Summary

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

Details

Page properties

Content

...	...	@@ -37,31 +37,30 @@
37	37
38	38	== **Feedback items ** ==
39	39
40		-//__Removed OData as option for an API Gateway operation__//
41		-With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
	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.
42	42
43		-//__Changes in API Gateway operation paths is automatically updated in Create__//
44		-When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
	43	+//__User Roles are sorted alphabetically__//
	44	+All user roles under User Management are now also sorted alphabetically.
45	45
46		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
	46	+//__Name of keystore for user management now includes the environment__//
	47	+To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename.
47	47
48	48	== **Bug fixes ** ==
49	49
50		-//__Prevent endless loop in Deploy -> User Management__//
51		-With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
	51	+//__Consolidated upgrade process cloud template__//
	52	+With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud.
52	52
53		-{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
	54	+//__Ensure users can deploy release on environments they have edit rights on__//
	55	+As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so.
54	54
55		-//__Update error handling during migration to the 3rd generation runtime__//
56		-As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
57		-
58	58	== **Fancy Forum Answers** ==
59	59
60	60	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:
61	61
62		-* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63		-* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64		-* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
	61	+* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
	62	+* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
	63	+* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
65	65
66	66	== **Key takeaways** ==
67	67