Version 2024.01.1 Patch
Date of version: February 14, 2024
This section contains New Features, Important Enhancements, Modifications, Removed Features and Bug Fixes for patch version 2024.01.1.
Removed Features
APNZ-3790 WARNING! The feature of automatically applying URL decoding to the value found with the variable at the time of retrieval has been removed. If this functionality is needed, URL decoding should be done with a business rule.
New Features
APNZ-4047 New Screen: Application Logs Purge Jobs
The automatic cleanup of the data logged on Apinizer at specified time intervals has been implemented. See.
APNZ-4048 Creation of Alarms for Logs
When the logs stored in Apinizer reach a certain size, the creation of an alarm has been enabled. See.
APNZ-4057 Trace Search Filter
An advanced search filter based on trace mode has been added to the API Proxy. See.
APNZ-4060 Make Global Feature
The items listed on the project pages (connection information, monitor settings, report settings, credentials, certificates) can be moved to the administrator side, so that their management can be done by the administrator and their use can be done jointly in all projects.
APNZ-4080 NTLM Settings
NTLM feature has been added to the routing tab of API Proxy to enable authorization in cases where Backend APIs require NTLM. See.
APNZ-4108 Adjustment of Log Levels Based on Class/Package
With the addition of the Log Levels tab to the Application Logs page, the configuration of log levels based on class/package has been enabled. See.
APNZ-4144 URL encode and URL decode operations in the Business Rule Policy
URL encode and URL decode features have been added to the Business Rule policy. See.
APNZ-4146 URL encode and URL decode operations on the Data Operations Page
URL encode and URL decode features have been added to the Data Operations page in the toolbox. See.
Important Enhancements and Modifications
APNZ-3860 Conditions "is exist" and "is not exist" have been added to the policies.
APNZ-3914 The information about the current project being accessed has been added to the left menu of Apinizer.
APNZ-3928 Roles with access to the Test Console in Toolbox have been revised.
APNZ-3973 Configuration of credentials and analytics in the API Portal has been enabled. See.
APNZ-4082 Links have been added to the breadcrumbs.
APNZ-4097 Node affinity has been added to the Apinizer Kubernetes servers for Manager, Integration, and Portal. See.
APNZ-4110 Tables that were not appearing on the Audit and Backup page and entity names to be excluded during backup have been added.
APNZ-4114 Information about which API Proxies the Connectors are running for has been added to the Application Logs.
APNZ-4117 Performance improvement has been implemented in the process of saving data to the Apinizer database with failover.
APNZ-4119 Menu changes have been made.
APNZ-4120 A new error type has been added to Routing Connection. See.
APNZ-4128 To limit the size of the sample SOAP XML message generated with WSDL, settings for Sample SOAP XML Message Generation Settings have been added to General Settings. See.
APNZ-4134 For SOAP services, a "Fix SOAP Action and Namespace" option has been added to the Routing tab, allowing correction of SOAP Action and Namespace information. Thus, this process, which was previously done automatically, can now be made optional. See.
APNZ-4147 The log level for API Proxy application logs can now be changed specifically for the specified API Proxy. See.
Bug Fixes
Issue No | Description |
---|---|
APNZ-4063 | The requirement for scheduling has been removed on the Backup screen. |
APNZ-4065 | The issue of analytic charts grouping methods with the same endpoint has been resolved. |
APNZ-4069 | Pagination-related issues have been resolved. |
APNZ-4070 | The time display of data in the charts on the Analytics tab has been corrected to be in local time. |
APNZ-4071 | Webhook actions have been removed. |
APNZ-4089 | The error of re-encrypting the password when global STS Authentication and Backend API Authentication policies are defined for the Proxy has been resolved. |
APNZ-4090 | The issue of a Proxy generating excessive logs when its log level is set to debug, and the inability to search due to missing API Proxy and clientId information, has been resolved. |
APNZ-4100 | The issue of application logs writing the MongoDB insert log when the log level is set to debug has been resolved. |
APNZ-4102 | The issue of receiving an empty scope during the token acquisition process has been resolved. |
APNZ-4111 | The error of not falling into failover when an error occurs during the creation of a connection definition for logging has been resolved. |
APNZ-4113 | The issue of not going into failover if an error occurs during the creation of the Connector has been resolved. |
APNZ-4115 | The issue of missing API Proxy information in application logs for certain loggers has been resolved. |
APNZ-4121 | Headers added during the connection in routing, which were not logged, are now being logged. |
APNZ-4125 | The issue of the total value showing as 0 in IP Traffic & Time Metrics reports has been fixed. |
APNZ-4127 | The issue of caching where the same key goes to a different endpoint within the same proxy or proxy group now retrieves the previous result correctly. |
APNZ-4133 | The issue of Identity Providers not displaying records before the update and not reflecting new records on the screen has been resolved. |
APNZ-4142 | The issue of the "XML format" option in Data Operations resulting in a single line has been fixed. |