webMethods.io Integration 2.1.4 Fix readme

                                        October 2020
____________________________________________________________________________________________________                                        

** In addition to including resolutions to product defects, a fix may also include enhancements to 
   existing functionality and features.

** This fix readme is cumulative, which means that it includes all previous fixes for the release. 
   Fixes are listed from newest to oldest.

** This fix readme also mentions the cloud provider and zone/region where the fixes are applied. Go to the specific zone 
   in this fix readme to see the list of fixes available for that zone.
____________________________________________________________________________________________________
                                  
                                Cloud Provider: Amazon Web Services
                              _______________________________________

                                               Zones 
				        ______________________

				         [] US, Oregon
                                         [] EU, Frankfurt
        			        ______________________

______________________________________________________________________________________________________

				_______________________________________

				   Zone: US, Oregon
       	                        _______________________________________								

BIC-7279 (Fix 2)
Description: Global Error Handler is not working for webMethods.io Embed deployments.
Solution: Code changes made to fix this issue. Global Handler is now working as expected for the webMethods.io Embed deployments.

CF-941
Feature Description: Enabled custom domain feature that allows users to configure a custom domain for their tenants instead of using the default domain provided by webMethods.io Integration.	

CLTF-2656
Feature Description: All workflow execution requests which are kept on hold due to rate limiting will now be automatically executed after some time. This eliminates the need for users to manually execute each workflow in 'Hold' state.

FLOW-2199 (Fix 1)
Description: When a user creates an API using Swagger, the FlowService dependencies are not displayed for the associated connector.
Solution: Code changes made to fix this issue. Now when a user creates an API using Swagger, the FlowService dependencies will be displayed for the associated connector.

______________________________________________________________________________________________________

				_______________________________________

				   Zone: EU, Frankfurt
       	                        _______________________________________	

_______________________________________________________________________________________________________________________________________________________________________________________________________


Copyright

Copyright © 2020 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or 
its subsidiaries and/or its affiliates and/or their licensors.

The name Software AG and all Software AG product names are either trademarks or registered trademarks 
of Software AG and/or Software AG USA Inc. and/or its subsidiaries and/or its affiliates and/or their 
licensors. Other company and product names mentioned herein may be trademarks of their respective owners.

Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at 
http://softwareag.com/licenses.

This software may include portions of third-party products. For third-party copyright notices, license 
terms, additional rights or restrictions, please refer to "License Texts, Copyright Notices and Disclaimers 
of Third Party Products". For certain specific third-party license restrictions, please refer to section E 
of the Legal Notices available under "License Terms and Conditions for Use of Software AG 
Products / Copyright and Trademark Notices of Software AG Products". These documents are part of the product 
documentation, located at http://softwareag.com/licenses and/or in the root installation directory of the 
licensed product(s).