This page contains release notes for all versions of the Apinizer platform released in 2022. For each version, new features, changes, fixes, and migration notes are listed in detail.
The Apinizer platform began to be developed with basic features from its first versions in 2022. All changes made during this year are listed below.
A Code Snippet tab has been added to the Test Console, enabling generation of the necessary code to send requests via cURL.IMPORTANT CHANGES AND IMPROVEMENTS
Queries for Request Address and Routing Address fields in the Simple tab of the API Traffic screen search panel have been improved. Since Index Mapping Type has changed to enable these improvements, it is recommended to reindex old indexes to be able to search on these fields in old data.
Management of Error response template’s ignore setting has been enabled through API Proxy Group.
User experience of the API Proxy Group screen has been improved.
User experience of the dialog for IP Group selection has been improved.
Listing of Nodes on the Kubernetes Resources screen has been enabled.
An Endpoints tab has been added to the API Proxy Group screen for listing and filtering all methods/endpoints and viewing their details.
BUG FIXESAPNZ-3335 : In methods prepared with Select SQL Statement through DB-2-API, when null values are sent to bit and int type fields, false or 0 values are received instead of null values in the response.APNZ-3324 : When editing operations (policy, etc.) are performed on API Proxy, the edited routing address uses the previous value.APNZ-3323 : When an Advanced type query is created on the API Proxy Traffic screen, all results come, the query does not work.APNZ-3316 : When a policy is added after endpoint or Protocol Transformation editing, it creates a duplicate copy.APNZ-3315 : When an API Proxy added to Proxy Group is wanted to be deleted from the API Proxy list, it does not delete even though it returns ‘Successful’ result.APNZ-3310 : “This page is not responding” error is received on the Endpoints tab of the Proxy Group screen.APNZ-3309 : When trying to add Backend API Auth to Proxy Group, the screen breaks.APNZ-3306 : When SQL written in the DB-2-API module on the Manager screen is tested, it works, but when it is deployed to API proxy and tested through API Proxy, an error is received.APNZ-3305 : When an API Proxy is created with DB-2-API created as PostgreSQL type, connection problems are encountered.APNZ-3290 : Portal Manager (API Portal Manager) and Analyzer permissions added when editing a user are not working properly.APNZ-3279 : In Token Requests and Report Generator screens, records after 100 cannot be displayed due to pagination number limitation, even though records exist.APNZ-3278 : API Proxy filter on the API Traffic screen cannot be selected multiple times.APNZ-3277 : When a global policy is exported and import is attempted, the operation is shown as successful but is not performed.APNZ-3012 : In REST2SOAP type API Proxy’s Get method endpoints, body object remains in OpenAPI documentation.
Release Date: November 1, 2022IMPORTANT CHANGES AND IMPROVEMENTS
When Log Setting is set through API Proxy, it has been enabled to override the project-based log setting and operate in reverse.
Methods that take path parameters without a method name after the root directory have been enabled to work.
When Db-2-API’s method is tested, the returned response has been enabled to be editable. Thus, users can change the example response information or remove sensitive information and ensure this information appears correctly in the API definition file.
After Environment is republished, pods have been enabled to automatically restart.
Changes have been made in the usage requirements of fields related to API Proxy reparse and soapToRest expressions in Management APIs.
On the Kubernetes Resources page, viewing, deletion, and log information viewing of all namespaces belonging to the environment and pods connected to them have been enabled.
When the Hide in Spec File feature of API Proxy method is activated, if the Data Model used within the method is not used by other methods, this model is hidden from the definition file.
The ability to delete pods through the Kubernetes Resources screen has been added.
In Queries and Report Generator screens, exporting query results in excel format and accessing the view of data (parameter, header, body) belonging to message regions through dialog when the query is tested have been enabled.
Deploy All option has been removed from the API Proxy detail page. This operation should be done in a controlled manner based on environment.
User experience of the dialog for project selection has been improved.
An Advanced section has been added to the filter field on the API Traffic screen, enabling the use of personalized query filters.
When API Proxy name is clicked on the API Traffic screen based on project, redirection to the relevant API Proxy’s detail page has been enabled.
BUG FIXESAPNZ-3252 : Error is received when API Proxy is being undeployed.APNZ-3245 : If the response is successful and an error is received from a policy in the response line, the error code is not overridden by the policy’s error code.APNZ-3243 : Delete method is not found in Open API type documentation created from Apinizer.APNZ-3225 : When a global policy is exported and imported in a project other than the project named Default, the process does not work completely.APNZ-3218 : When taking backup, it does not give an error if path information is missing.APNZ-3216 : Documents returning Byte Array should be able to return as encoded string by default.APNZ-3206 : When WS Security STS Token policy is run in Trace mode, API calls made are not visible.APNZ-3203 : When LDAP Provider is selected as Identity/Role/Group Service in the policy and returned to edit, the value of this field appears as the default value.APNZ-3202 : The check that body information’s maximum size does not exceed 10mb when logging traffic records should be done after Privacy Settings are applied.APNZ-3201 : Remote Address information on the Login Audits screen comes incorrectly.APNZ-3200 : When going to the APIs page in API Developer Portal, an error is received from the console.APNZ-3197 : When Credential is imported as CSV, default fields in the Token Settings tab do not come selected.APNZ-3191 : When adding a new Key Store, an error is received from the console when the first definition is made and it is not added.APNZ-3185 : Backups taken do not appear on the History page.APNZ-3180 : Even though ProCrypt setting is closed based on application, it appears in API Proxy’s Settings tab.APNZ-3030 : When method name is changed on API Creator (DB-2-API, Mock, and Script API) on which API Proxy is created, policies in API Proxy’s method are lost.APNZ-3011 : When Get method is created with Db-2-API, requestbody object is produced empty in OpenAPI documentation.APNZ-2674 : Response comes empty in some existing examples on the JSON Path Test screen.
Common Query Model is metadata information that describes what type of data is in the message (usually in the body section). Models created based on Global are used when designing API definition files.
General settings related to Apinizer Platform’s Environments, Pod Security Context definition, server configuration (Management Console, API Integrator, and API Portal), pod restart and disable/removal, monitoring all pods and accessing their logs, and monitoring Kubernetes cluster operations can be managed through the interface.
ACL Report is a report screen that enables reaching information about which users from which organization can access which API Proxy, or which API Proxies users from which organization can access. Data such as Routing Address and Data Model belonging to access information can be viewed with filtering. Additionally, the output of the created report can be obtained as Excel.
ACL Audit Records displays records of operations of credentials that are approved or have their approval removed for access to API Proxy or API Proxy Group. Information such as operation date, operation type, reason, which user it applies to, which API Proxy/API Proxy Group and method it applies to are listed, and detailed filtering options are available.
Apinizer Management APIs enable performing many operations such as API Parse, ReParse, Deploy, etc. without needing the screen application. Thus, Apinizer can be integrated into DevOps environments.
Spec Design Editor allows creating a new API Definition Document by filling out forms through the interface or using existing API Definition Documents by importing them. This interface has been revised to improve user experience.
To prevent malicious login to Apinizer Management Console, a limit has been placed on the number of incorrect logins a user can make. After the user exceeds the allowed number of incorrect logins in the first stage, captcha verification is activated and the user attempts login with the determined login attempt. If the user has exceeded the total allowed number of incorrect logins, they are locked and are no longer allowed to log into the application.For a locked user to be able to log into the application again, this lock must be removed by an Admin from the Users page.
For REST type API Proxies, by hiding at the API Proxy level, access to the entire API Definition File can be restricted, or by hiding at the method level, access to specified methods from the API Definition File can be restricted.IMPORTANT CHANGES AND IMPROVEMENTS
When API Proxy Group’s Swagger UI information is displayed, all method tabs come open, filtering can be done according to API Proxy criteria, method grouping has been removed, and alphabetical sorting has been enabled.
Enter key has been activated for adding new entries to the Category list on the API Proxy page.
In API Portal, Shared Secret information belonging to the key can be changed and generated.
Time option has also been added to the date-based filter field on screens in the Reports and Analytics menu.
Fields where code entry is made on application screens have been enabled to be resizable.
Object ID filter has been added to the Audit Records screen.
Error Handling Type and Condition entries according to the type here have been added to the Connection Settings section of Routing settings belonging to API Proxy.
The ability to customize error messages in responses has been added to the tab where Routing settings belonging to API Proxy are located.
Export API Proxy link has been enabled to be accessible from the dropdown menu on the API Proxy listing screen.
Overview, Settings, Design, and Routing tabs have been renewed to improve user experience on the API Proxy editing page.
Overview and Settings tabs have been renewed to improve user experience on the API Proxy Group editing page.
When defining a variable of Body type, it has been enabled to come with default values according to body type.
When adding a new user, if Login Type value is LDAP, querying information from LDAP based on the setting defined on Apinizer LDAP Login page has been implemented.
BUG FIXESAPNZ-3178 : When Gateway Engine Logs’ level is set to Debug from the Application Logs page, MongoDB appender’s log is continuously printed to the database.APNZ-3176 : When tests made in Test Console are saved, it throws an error.APNZ-3174 : In Mock API, creating a second record with the same Content Type value for a response is not allowed.APNZ-3171 : When editing a method’s parameter in Db-2-API, if Repetition Type is selected as Multiple and Try It is done, it returns to Single.APNZ-3168 : In Db-2-API, timeout of Connection Pool Definition for SQL statements of Batch or Procedure type does not work.APNZ-3168 : Connection Timeout field is not found in Connection Configurations for databases. Additionally, time units in the connection definition are incorrectly selected. (Entered in seconds when it should be milliseconds.)APNZ-3165 : When a WSDL with SOAP 1.2 method is imported, only SOAP 1.1 endpoint is used.APNZ-3147 : Listing on the Users page is not working.APNZ-3139 : When a new Action is wanted to be added to an API Integrator task, if the action contains a Body field, this input field does not come after the action is saved.APNZ-3137 : A person with Project Owner permission cannot add new members to the project.APNZ-3135 : When editing Authentication policies, Error Message Customization list does not come.APNZ-3124 : Case-insensitive method search on API Proxy’s Design and Development tabs does not work.APNZ-3117 : When wanting to edit configuration belonging to certificate definition, certificate detail is not displayed.APNZ-3115 : When a new method is added in Mock API, a second copy of the method is created.APNZ-3112 : In API Call policy, variable contents for Original Message Data do not change.APNZ-3102 : Token requests are not logged when they are incorrect, even though they should be logged.APNZ-3096 : Error is received when assigning values to Context Values section when adding a Variable.APNZ-3095 : Namespace appears incorrectly in WSA Settings.APNZ-3082 : Character limit error in the description field on API Proxies prevents saving.APNZ-3079 : When a role added to Credential is deleted, this situation is not reflected in the request when a request is sent to an API Proxy with one of the authentication policies added.APNZ-3068 : Control continues on Scheduled Jobs even though there is no active patch operation.APNZ-3061 : Library incompatibility error is received in Incoming Message WS-Security (Ws Security From Target) policy.APNZ-3060 : In newly added API Call policy on the response line, Message Template Operation Type field’s initial value assignment has not been made.APNZ-3058 : WSA settings are not applied for API Proxy with SOAP2Rest protocol transformation applied.APNZ-3057 : When globally added Plain-Text Authentication, Digest, and Base64 policies are opened for editing each time, selected fields return to default values each time.APNZ-3042 : When API Proxy with SOAP2Rest protocol transformation applied is added to API Proxy Group, the body variable of Script policy added to the response line appears as XML.APNZ-3041 : Export API Proxy link on the API Proxy page does not work and gives an error for users other than Admin.APNZ-3040 : Test Console errors; In Proxy Group List, Relative Path value only shows active ones, all values in the Endpoints field do not appear within the field.APNZ-3039 : Error is received after a method is deleted in Mock API.APNZ-3038 : Error icon is seen on the endpoint created in the Development tab in Empty API.APNZ-3032 : Errors are received when WS-Security policy is imported; Save button does not appear clickable, Delete button does not appear, and Encryption and Signature fields’ order is broken.APNZ-3029 : After operations are performed on methods on API Proxy page’s Development tab, active method selection appears incorrectly.APNZ-3026 : When adding from existing IP Groups to Allowed IP List policy, it gives a validation error.APNZ-3021 : Context Variable values selected in Variable are not saved.APNZ-3010 : When adding a new endpoint, when the status of the input for using Byte Array type for Compressed Response (according to Accept-Encoding value) changes, the label remains the same.APNZ-2939 : Deficiencies have been detected in the project export and import process.APNZ-2539 : Parameter added to the query of a method added in DB-2-API cannot be used in multiple places in the query.
Indexes in the defined Elasticsearch Cluster can be automatically backed up (snapshot) at determined time intervals. When this setting is configured, Snapshot Lifecycle Management (SLM) policy is defined on the cluster. Thus, backup settings can be managed on the cluster without needing another add-on, and history information containing result information of backups run can be monitored. Snapshot taking can be manually started when desired.
General settings (logo, title) on API Developer Portal and page contents or some fields (How It Works, FAQ, Login, Register) can be customized optionally. Thus, Portal Administrators can personalize the content their clients will use. In this way, content management can be done according to market dynamics and needs.IMPORTANT CHANGES AND IMPROVEMENTS
Token Settings have been added to the Credential page, enabling authentication settings to be managed based on Credential as well.
“Enable Download” field and “Use Base64 Encoded Text/Byte Array For Compressed Response(by Accept-Encoding value)” option have been added to the method/endpoint editing dialog within API Proxy to manage operations to be performed on response content.
Search filter according to Routing Address has been added to the API Proxy screen.
Changing the level of log4j setting based on API Proxy has been enabled.
Screen improvements have been made for easy use of Authentication Policies.
Display of example body taken from API Definition file through Test Console has been improved.
Display of all sections belonging to Request and Original Message fields of API Call Policy has been arranged. Usage of Body sections has been improved.
Cache settings have been added to the Request section of API Call Policy, enabling request results to be retrieved from cache according to the selected variable.
When API Proxy is in Trace mode, logging of API Call policy’s information has been enabled.
New variable definitions that limit error message or response message characters returned from API with XML/JSON Error Response Template within API Proxy have been added.
Display of deployment information on API Proxy and API Proxy Group screens has been improved.
“Apply by” value has been added to API Based Quota and API Based Throttling screens, enabling these policies to work through a specific variable.
“Context Value” type and values and “Form” option for Parameter type have been added to the Variables screen.
New key concepts have been added to Gateway Environment settings to configure settings for multi-part HTTP requests for file uploads.
Display of members and roles on the Projects page has been renewed.
Display of error messages on XML Transformer and JSON Transformer screens has been improved.
Display of error messages on LDAP connection definition and LDAP Identity Provider screens has been improved.
Quick search feature has been added to the endpoints/methods section on API Proxy’s Development tab.
Filtering option according to “Correlation ID” on Gateway Engine logs on the Application Logs screen has been added.
Display of Username or Key information on the Token Requests screen has been enabled. API Proxy, Username or Key, and Status Code Bigger Than fields have been added to filtering options.
New methods have been added for accessing Swagger and OpenAPI definition files through deployment address information.
Features for viewing API Proxy Group’s API definition file (API Definition Document) and API definition information interface have been added.
Display of Response Message created according to settings on the screen where SOAP2Rest transformation configurations are made has been enabled.
Files that are PKCS12 type and have PFX extension have also been allowed for keystore file types to be used for HTTPS termination in environment settings.
Editing of added configurations on the Key Stores screen has been enabled.
Byte Array Content Types page has been made to the Predefined Variables menu to manage “isByteArrayContent” values.
Necessary options for API Proxy Group and API Call have been added to the Cache Monitoring screen.
Authentication information has been added to API Specification information in Swagger and Open API formats.
When API Proxy is reparsed, name and description information is now retrieved from the original API Proxy.
The ability to view all APIs’ endpoints in swagger interface through the selected API Proxy Group page has been enabled.
The ability to create API Product with API Proxy Group has been enabled.
If the feature to apply API Proxy Group settings to API Proxies is activated, the ability to manage settings (CORS, Log Settings, XML/JSON Error Response Template, Forwarded IP Header Parameter, and Log Settings) that will be applied to all API Proxies within it from the API Proxy Group screen has been enabled.
If API Proxy is added as API Proxy Group, in addition to the relevant API Proxy deployment information, listing of API Proxy Group deployment information has been enabled.
When creating Gateway Instance, the selection of which Kubernetes worker server the relevant environment will run on has been added.
The feature to add multiple example responses to an endpoint when editing Mock API definition has been developed.
API Security role has been added to manage Identity Management section working based on project.
New ones have been added to lists showing API Traffic logs and dialog areas where log details are displayed. Method name has been added to filtering criteria.
“Signature Digest Algorithm, Use Single Certificate” fields have been added to the Signature section and “Key Identifier Type, Custom Identifier Type, Custom Identifier Type Value Type” fields have been added to the Encryption section in WS-Security to Target policy.
“Log Key” field has been made editable to make ILM Policy and Template information of deleted Elasticsearch Cluster definition usable in another cluster as well. Additionally, when boxes showing ILM and Template statuses on the screen where clusters are listed are clicked, the relevant ILM or Template status can be updated.
API Based Quota and Backend API Authentication policies created only based on local can be created based on global through the Global Policies menu.
Selected MongoDB collections can be excluded when taking backup. Thus, by ensuring that records kept for logs are not included in the backup file, backup file size can be controlled.
Two operations related to JWT information generation on the Environment Settings page have been added; regenerating and loading the token, and taking private key information from file and generating and loading the token.
“SOAP Action” field has been added to WSA setting that can be updated based on method for SOAP type API Proxy.
General settings on Privacy Management have been enabled to be applied to requests coming outside API Proxy as well. Thus, even if requests are sent to the wrong address, sensitive data they contain is protected.
BUG FIXESAPNZ-3004 : When Gateway Environments are republished or published, the saved password for HTTPS is encrypted again.APNZ-2903 : Path parameter containing spaces is sent incorrectly to the API.APNZ-2976 : Searching for parameter and header sections with keyword criteria through the Queries page does not work.APNZ-2974 : When “example” in the API Definition file on Test Console is empty, selection should be made according to API type in “examples”.APNZ-2963 : When a request is sent through API Proxy to a method of StoredProcedure type created with DB2API, large numbers in the response come with broken format and appear in scientific notation.APNZ-2956 : Example request body created from API Proxy’s Design tab does not come to the test console.APNZ-2955 : Error occurs when wanting to create example request and response body from API Proxy’s Design tab.APNZ-2952 : Parameter information of web services added from WSDL type does not come to the test console.APNZ-2948 : After Rest2SOAP Protocol Transformation is saved, changes are not reflected to the Design tab.APNZ-2947 : Error is thrown when parsing WSDL belonging to KPS services.APNZ-2943 : Any editing done on Gateway Environments breaks pod selection to “all”.APNZ-2933 : Logs on API Proxy’s Trace tab show the processing order of policies on the response line completely reversed.APNZ-2931 : When testing in Database Identity Provider, username and password field values are used incorrectly.APNZ-2930 : Example message values in DB-2-API do not come automatically when API Proxy is created and wanted to be tested.APNZ-2923 : When a policy added in API Proxy Group is removed, status information remains as deployed.APNZ-2899 : Error is received when clicking on a method from the API Design screen.APNZ-2895 : Error occurs when a local policy is imported to API Proxy.APNZ-2983 : When a method/endpoint is added or updated, the policy icon in API Proxy flow structure disappears.APNZ-2881 : API Proxy Group does not use Apinizer error message templates.APNZ-2880 : When CORS is added, status codes of responses for requests other than HTTP method Options are broken.APNZ-2876 : Errors are seen when API Spec information is displayed as Swagger 2.x format.APNZ-2873 : Pagination component on the API Proxy Traffic screen disappears.APNZ-2870 : If Content-Type “application/x-www-form-urlencoded;charset=UTF-8” is sent in JWT Token acquisition message, it returns an error.APNZ-2868 : Models do not come in some services in specification information in Open API format produced for WSDL.APNZ-2864 : In the dialog where API Proxy is added to the API Proxy Access Control List (ACL) list of any credential through the Credentials menu, filter selections like project do not reflect to the list without pagination.APNZ-2862 : When API Proxy Group is loaded to multiple environments, if one is redeployed, others fall into redeploy required status.APNZ-2861 : Time fields in JWT Token responses are not in ISO 8601 format.APNZ-2855 : When the example of Rest2Soap type API Proxy is changed from the Design tab, this situation is not reflected to Swagger documentation and Test Console.APNZ-2846 : Multiple responses with the same status code can be created for the same endpoint in Mock API.APNZ-2841 : When adding a condition on API Proxy page’s Routing tab, even if “does not contain” function is selected, it does not appear within the component when updating the condition.APNZ-2836 : When API Integration is run, it only brings one result.APNZ-2829 : When a SOAP web service is wanted to be created as REST API, changes made during protocol transformation are not reflected to Design.APNZ-2828 : In Rest-to-SOAP type API Proxies, when changes are made through Jackson Transformation, it does not come automatically to Test Console.APNZ-2826 : Texts appear incorrectly in the dialog that appears when API Proxy is reparsed.APNZ-2824 : When testing an endpoint with API’s document through API Portal, it gives a CSP error.APNZ-2819 : Error is given when wanting to create API Proxy through Open API.APNZ-2818 : When wanting to create API Proxy by uploading a file, the file component in the opened dialog gives an error.APNZ-2805 : When multiple API Proxies are created from DB-2-API, the Deploy All API Proxy button on the DB-2-API screen does not work.APNZ-2797 : Log tab on Test Console gives an error.APNZ-2788 : Example section of Open API documentation does not come properly.APNZ-2787 : API Proxy Template screen crashes when Authentication policy is added.APNZ-2783 : Collection list on the Collection tab on Test Console and Collection List are not the same.APNZ-2782 : A second Key Store definition cannot be added to WS-Security policy.APNZ-2763 : Condition error in Routing; when conditional routing is added, it cannot distinguish according to query parameters.APNZ-2760 : When too many credentials are added to an API Proxy through API Proxy ACL or selections are made on different pages of the table, it does not work properly. Additionally, after filters are deleted in the dialog where credential selection is made, added credentials can be selected again.APNZ-2756 : When endpoint addition and editing operations of Empty API type API Proxy are done in Design tab or Develop tab, changes here cause data (Backend Path, Name, Description) belonging to relevant path’s fields not to work synchronously.APNZ-2723 : After API Proxy Group is saved or redeployed, API Proxies go into redeploy mode.APNZ-2749 : When adding an endpoint to Mock API, the body of the default response in Response Information is edited and saved. Later, when this response is wanted to be viewed, this information is seen not to have changed with the given value.APNZ-2744 : When wanting to create API Proxy by uploading the API’s spec file, when multiple file operations are done in the input field, this input gets stuck, assigned data does not change.APNZ-2742 : Even if “Use a variable” is selected and saved in Modify Original Message field in API Call Policy, “Specify the Value” option comes selected.APNZ-2741 : Value belonging to Identity/Role/Group Service field cannot be selected in Digest Authentication policy.APNZ-2572 : When selecting certificates with the same name belonging to different environments in Test Console, it is not clear which certificate belongs to which environment.
Release Date: February 1, 2022IMPORTANT CHANGES AND IMPROVEMENTS
The ability to create API Proxy Group access list for Credential has been enabled.
Views of detail and stack trace information on the Application Logs screen have been arranged.
Security vulnerability originating from Log4J has been permanently resolved.
Definitions created on Sensitive Data Management have been enabled to be applied to form-data type data.
BUG FIXESAPNZ-2706 : Data belonging to Authentication and Incoming Message WS-Security policies for Backend API appear incorrectly.APNZ-2702 : When wanting to add a new query or filter on the Anomaly Detector and Report Generator screen with query, empty values can be entered even though there are required fields.APNZ-2690 : In input fields on Backend API Authentication Policy and Backup Settings screens, passwords only appear masked.APNZ-2689 : Password fields requested in Backend API Authentication policy are encrypted multiple times.APNZ-2628 : Auto-filled field in CORS component throws a database error.APNZ-2684 : Republish operation on Gateway Environments screen does not work stably.APNZ-2683 : When copy-paste is done to the host alias field on Gateway Environments screen, it creates with newline and space characters.APNZ-2682 : When any editing is done on Elasticsearch Clusters, boxes showing status information of Index Templates turn red.APNZ-2681 : Since databases before MSSQL 2014 do not have TLS 1.2 support, Db2Api created with these connection definitions give TLS error.APNZ-2678 : A non-functional component appears on the CORS Headers screen.APNZ-2670 : Selected log information on the Token Requests screen comes late.APNZ-2664 : When a request is made with a non-existent relative path to the access address given to Manager console, it is not logged.APNZ-2660 : Pagination section on API Proxy Group does not appear.APNZ-2656 : Roles field in Authorization policy does not work properly.APNZ-2655 : Roles component in Authorization policy stays below another component in appearance.APNZ-2622 : HTTPS requests sent to Elasticsearch cluster through management console do not go.APNZ-2615 : API Based Throttling policy cannot be selected from global on the API Proxy screen.APNZ-2613 : API Definition Document Editor does not allow creating endpoints from special characters.APNZ-2563 : Project information assigned to Gateway Environment does not appear completely.APNZ-2717 : Undeployed environments do not come on API Proxy and Proxy Group screens.
