TOLERANT Post Release 12.0

Notices and Warnings

• The internal field post.AddressComplete now only gets filled (regardless of the configured mapping) when the mode in postProfile is set to „FASTCOMPLETION“. This prevents confusion in the internal address validation engine, and sets a best practice to only use post.AddressComplete with the correct mode. The new behavior can be disabled via a special parameter with id postProject-1.ignoreAddressComplete. Please refer to support@tolerant-software.de for further information.
• Discontinued the feature PROVINCE_LIST which was an unused redundant feature, that can be better achieved via the mode LIST.
• Added support for the following fields (relevant for some countries like Spain for example):
  • post.SubBuilding3
  • post.SubBuilding3Name
  • post.SubBuilding3Descriptor: V5 only
  • post.SubBuilding3Nr
  • post.SubBuilding3PreDescV6 only
  • post.SubBuilding3PostDescV6 only
• When being in a service instance context in GUI, the GUI and all its configuration settings can now be reloaded from the memory of the running service instance (as opposed to the underlying xml configuration). The menu entries and tooltips were improved to reflect and clarify new (and existing) behavior. (since 2025/06/19, 12.0)
• Removed functionality to „Reconfigure Runtime“ from GUI, backend service and CLI calls. The functionality was too similar to „Reconfigure Service“ and led to confusion. (since 2025/06/19, 12.0)
• Based on customer requests, returncodes for Addressvalidation have been simplified for better understanding and easier usage:
  • Returncode 20 now identifies „Wrong or missing values“ for post.Street and combines the former return codes 20, 21 and 26.
  • Returncode 30 now identifies „Wrong or missing values“ for post.DeliveryService and combines the former return codes 30 and 31.
  • Returncode 50 now identifies „Wrong or missing values“ for company names and combines the former return codes 50 and 51.
  • Returncode 50 now identifies „Wrong or missing values“ for post.Number and combines the former return codes 61 and 62.
• Reworked, combined and harmonized the command-line tools for service administration. Now all functionalities for managing the service and much more can be found in the new< service.sh/.bat tool. For a detailed explanation of the new features and usage, please refer to the manual. (since 2025/06/19, 12.0)
• New docker images are now available via the TOLERANT Docker Hub online presence All configuration items and information regarding usage and best practices can be found under our TOLERANT GitHub online presence.
• A new version of the H2 database driver (h2-2.3.232) will be used from now on. This also means that customers will have to switch to a new version of our supplementary reference data (e.g. StaB data). This will be shipped together ( in the same folders on SFTP ) with the normal versions of the reference data, which will still be there to support older product versions. The new reference data artifacts will include „_from_12.0“ in the name.
• Completely reworked the logging functionalities. Users can now use the full breadth of log4J2 functionalities. To make the switch easier, log4J2 example configurations for different scenarios are shipped with the product. For more information please refer to the manual. (since 2025/06/19, 12.0)
• Internal fields post.NumberAdd and post.Number2Add were completely removed as these fields were not get populated by any values in address validation.
• Removed support for unused internal fields post.CityAddInfo, post.SubCityAddInfo, post.LocalityAddInfo.
• InternalField post.Province was replaced with post.Province1. There are also corresponding subitem fields available namely post.Province1Ext, post.Province1Abbrev, post.Province1ISO. Similarly post.SubProvince has been replaced with post.Province2 and respective subitems have been introduced. The field post.Province3 and corresponding subitems have also been introduced.
• Removed fields post.NumberAdd and post.Number2Add as they were redundant to post.NumberExt.
• Post v12 onwards no longer supports:
  • rcMode=“old“
  • Distance Mode
  • Database type „GeoOnly „db
• The default input format delimiter and output format delimiter value has been changed to semicolon.
• (since 2025/06/19, 12.0)
• The attribute fuzzyCompatibility (only for V5 engine) is now always enabled by default. The attribute itself was removed.
• The monolithic structure of the products has been broken down into a more modern, microservice-oriented architecture. The basic shipped TOLERANT application now consists of 7 services:
  • TOLERANT Backend Service: Contains all functionality needed for the technical processing of requests.
  • TOLERANT GUI Service: Contains the Angular GUI.
  • TOLERANT SOAP Service: Supports SOAP calls and routes to the Backend Service (optional).
  • Webserver (NGINX): Gateway for all incoming requests.
  • Identity Provider (Keycloak): Preconfigured identity provider for our example installation (optional).
  • Grafana: Visualization of available metrics (Docker example only).
  • Prometheus: Data collection and querying for later use in Grafana (Docker example only).

  (since 2025/06/19, 12.0)

• Adjusted the shipped example configurations and templates to reflect the prioritization of the new address verification engine V6. To be able to use the V5 engine, now the user must specifically set the attribute engineVersion=“V5″ in postRuntime.
• The old SOAP interface was moved to a separate microservice (or container in docker context). The installation is optional, to support legacy clients from customers with older infrastructure. By default it will not get installed.
• Completely reworked the internal metrics to provide a standardized format (which enables easy integration with tools like https://prometheus.io). See https://micrometer.io or the official TOLERANT manual for additional details on how to use them.
• A new version of the TOLERANT license (version 1.1). can now be created and interpreted via the application. It now (among other changes) includes the possibility so set a rate limit The validation is backward-compatible, so that old license will be validated correctly.
• New search mode GEOCODETOADDRESS was added to post profile. The search mode allows reverse geocoding. It applies a search radius to the submitted geocoordinates (WGS84) to define an area in which to search for addresses and retrieves the closest address or addresses to the coordinates with distance and direction to the submitted geocode:
  • searchRadius: new Field in post profile to apply a search radius in meters to the geocoordinates as center.
  • post.InputGeocodeLatitude: new input field for latitude.
  • post.InputGeocodeLongitude: new input field for longitude.
  • post.InputGeocodeComplete: new input field for latitude and longitude comma separated.
  • post.GeocodeDistance: new output field that indicates the distance in meters from the address to the center of the search radius.
  • post.GeocodeDirection: new output field that indicates the direction which the address lies from the center of the search radius.

  Please note that the new mode needs a new reference data and is only supported for Engine V6.

• Removed attributes user-1,user-2 and so on in an effort to clean up unused configuration attributes in project. (since 2025/06/19, 12.0)

New Product Features

Configuration and Administration GUI

• TPR-14266: Reworked and consolidated several icons throughout GUI for better clarity. (since 2025/06/19, 12.0)
• TPR-14170: Updated all GUI components to Angular version 19.0. (since 2025/06/19, 12.0)
• TPR-13108: V2 endpoints usage deprecated for GUI (since 2025/06/19, 12.0)
• TPR-13005: The static path element inst/1 can now be omitted from the requsts sent to the admin service. (since 2025/06/19, 12.0)
• TPR-12039: Cleaned up several labels and info texts in GUI as well as descriptions in the manual to increase consistency and information value of some configuration attributes.
• TPR-10708: Added upload functionality for .LIC files (V6 engine of Post) in the Unlockcode/Licence section in GUI.
• TPR-10704: New search mode GEOCODETOADDRESS and a new field called searchRadius were added to post profile settings.
• TPR-10274: The GUI now features a one-click auto-detection for CSV input file settings, including encoding, delimiters, and text enclosures. This streamlines the import process by automatically identifying relevant parameters.

Batch

• TPR-14120: Batch processes will now report their statistics to a batch summary file located under /logs. (since 2025/06/19, 12.0)

Service

• TPR-14193: TOLERANT Post now supports the latest cloud engine provided by Informatica/Addressdoctor, based on the latest internal engine version 6.6.
• TPR-12599: A new /info endpoint for all products has been introduced. For example: http://localhost:8080/postService/info. This endpoint can be used to monitor details about the product. For example: Post info endpoint has unlock code and its corresponding expiration date information. (since 2025/06/19, 12.0)
• TPR-12029: Service registration for Windows has been reimplemented and improved to better support the current multi-service setup. The functionality is included in the new service.exe tool. (since 2025/06/19, 12.0)
• TPR-10825: Unique validation for the filepath attribute in log element was added.
• TPR-10739: Improved and extended validation of path-values with better error messages.
• TPR-10137: Improved scrolling and reloading of console output when executing background jobs via GUI wizard.

API

• TPR-10622: The following system properties can now be used to configure the java API client:
  • com.tolerantsoftware.api.socketTimeout
  • com.tolerantsoftware.api.connectionTimeout
  • com.tolerantsoftware.api.maxConnections

General

• TPR-14699: Updated usage/help for postEngineUnlockcodes.sh tool, to better reflect the correct usage wit V6 .lic files.
• TPR-14673: The new profile attribute additionalData can be used with the V6 engine to get more data for verified and corrected addresses.
• TPR-14629: The H2 database driver was upgraded to use the latest version: 2.3.232.
• TPR-14448: Extended the shipped examples to now also include a separate project fully configured to use the Fastcompletion mode (V5 and V6, Service and Batch).
• TPR-14312: Features and enhancements for Version 5 of the address verification engine:
  • All Countries
    • Province Information Handling
      • Province information is retained in an output address even if the reference data lacks it for the country. If the address is valid without the province, a „V2 “ score is returned, indicating the address is correct but missing some data.
      • Previously, when province information was missing, Address Verification moved it to the Residue field and returned a „Cx“ score.
  • Japan
    • Improved Parsing and Validation
      • The parsing and validation of Japan addresses are improved based on customer feedback.
  • Spain
    • Address Correction and Reference Data Update
      • An Ix status is returned for an address that requires significant correction to yield a match with an address in the reference data. Previously, an address that required significant changes might have been corrected and an overly optimistic Process Status score returned for the address.
      • Additionally, the reference data for Spain is updated.
  • United States
    • Support for CASS Cycle „O „
      • Address Verification supports all requirements of the Coding Accuracy Support System (CASS) Cycle „O“ standard.
    • Updates to High-rise Default Calculation
      • Address Verification updates the verification logic for the identification of high-rise default addresses.
      • Identifies an address as a high-rise default when the address has a valid delivery point value at the primary building number and lacks secondary information.
    • Enhanced DPV Return Codes
      • Support for the enhanced DPV return codes introduced by the United States Postal Service in Cycle „O“.
    • Support for Non-Delivery Days Flag
      • Address Verification returns a single-character value to identify addresses that cannot receive mail on one or more days of the week.
      • Writes the value to a new field, Non-Delivery Days Flag, alongside the existing Non-Delivery Days field.
    • Verification of Non-Default Locality Names in Cross-State Addresses
      • Address Verification updates logic for verifying non-default locality names in addresses involving state boundaries.
    • TotalDPS Support
      • Address Verification supports delivery rules defined by TotalDPS, such as rules for addresses sharing Delivery Point Value.
    • Informed Address Support
      • Support for the Informed Address program, which allows vendors to provide an anonymized alphanumeric string instead of a full address.
      • Returns DPV footnote A1IA for an informed address and can add it to Form „3553 if the address has a valid ZIP code.
    • R779 Phantom Route Identification
      • Address Verification recognizes „R779“ as a phantom carrier route designation, in addition to „R777“.
    • Form „553“ Compliance
      • Supports the data requirements of Form „3553“ as defined by the United States Postal Service in August 2022.
    • Drop Indicator Recognition
      • Address Verification identifies mailbox addresses serving multiple households or businesses by using the DPV Drop Indicator table.
    • DSF2 No Stats Reason Field Updates
      • Introduces the value 6 in the DSF2 No Stats Reason field, identifying addresses that require secondary information.
    • Updates to Military Address Recognition
      • Recognizes newer military address identifiers mandated by Cycle „O „.
    • Improved Census Tract Identification
      • Improves census tract identification for addresses with house numbers forming part of a range.
      • Addresses with hyphenated or alphanumeric house numbers are better identified.
      • If census tract information cannot be retrieved at house number-level precision, the census tract number is returned at street-level precision.
    • Improvements to United States Addresses
      • A United States address can be validated when organization information precedes street information on a delivery address line. Types of organizations include universities, hospitals, and corporate offices. Previously, an Ix process status was returned for the address.
      • Address Verification recognizes the organization information when a house number and street type are found in the street information on the delivery address line.
  • Australia
    • AMAS Certification and Optimization Level Updates
      • The Address Matching Approval System (AMAS) „2020 “ standard for address verification in Australia is certified.
      • WIDE optimization is enabled when verifying Australia data in certified mode. Previously, WIDE optimization was disabled when verifying Australia data in certified mode.
      • If WIDE optimization was selected in an earlier release, the criteria defined by STANDARD optimization were applied.
      • The AMAS certification standard does not support addresses verified with the WIDE optimization level.
      • The optimization level in certified mode can be set to evaluate its effect on the data.
      • If submitting an address set to the Australian postal service as certified to the AMAS standard, the STANDARD optimization level should be used.
  • Israel
    • Geocode Return in Hebrew Script
      • Standard geocodes for Israel addresses can be returned in the Hebrew script in addition to addresses in a Latin script
  • Malawi
    • Postcode Recognition
      • Post code information in Malawi addresses can be recognized as a six-digit number,For example, „102010“ is recognized as a post code in Malawi
  • Saint Lucia
    • Postcode Recognition
      • Post code information in Saint Lucia addresses can be recognized in the following formats:
      • • As a five-digit number.
        • As a string that includes the two-letter ISO country code before the five-digit number and that adds a space between the fourth and fifth characters,For example, „LC05 201“ is recognized as a post code in Saint Lucia.
  • Samoa
    • Postcode Recognition
      • Post code information in Samoa addresses can be recognized as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, WS1334 is recognized as a post code in Samoa.
      • Previously, Address Verification recognized four-digit postcodes in Samoa.
  • Saint Vincent and Grenadines
    • Postcode Recognition
      • Post code information in Saint Vincent and the Grenadines addresses can be recognized as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, „VC0120“ is recognized as a post code in Saint Vincent and the Grenadines.
  • Ghana
    • Postcode Recognition
      • Post code information in Ghana addresses can be recognized as a three-digit number and as a five-character string that includes the two-letter ISO country code,For example, „GA183 „is recognized as a post code in Ghana
  • Liberia
    • Postcode Recognition
      • Post code information in Liberia addresses can be recognized as a four-digit number.,For example, „4000“ is recognized as a post code in Liberia
  • Viet Nam
    • ISO Name Recognition and Output Address Handling
      • Viet Nam is recognized as the International Organization for Standardization (ISO) name for the country in the English language.
      • Both Vietnam and Viet Nam are recognized in an input address, and Viet Nam is returned as the English-language name in an output address.
      • Previously, Vietnam was recognized and returned as the country name in the English language.
  • New Zealand
    • Certification to SendRight 2020 Standard
      • The SendRight 2020 standard for address verification in New Zealand is certified.
  • Japan
    • Improved Parsing and Validation
      • The parsing and validation of Japan addresses are improved based on customer feedback.
  • Barbados
    • Postcode and Street Level Verification
      • Post code information in Barbados addresses can be verified.
      • The reference data for Barbados includes street and post code data.
      • The reference data contains the post code as a five-digit number.
      • The postcode can be recognized as a five-digit number and as a seven-character string that includes the two-letter ISO country code,For example, Address Verification can recognize „26028“ and „BB26028“ as post codes in Barbados
      • The postcode is written with the prefix BB in formatted and delivery address lines and without BB in postal code address elements.
  • Kiribati
    • Postcode Verification
      • Post code information in Kiribati addresses can be verified
      • The reference data contains the post code as a four-digit number.
      • The postcode can be recognized as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, „0107 “ and“ KI0107″ are recognized as post codes in Kiribati.
      • The postcode is written with the country prefix „KI “ in formatted and delivery address lines and without KI in postal code address elements.
  • Denmark
    • Sub-Building Information Verification
      • Sub-building information in Denmark addresses is verified.
      • Additionally, the reference data for Denmark is updated.
  • Nauru
    • Postcode Verification
      • Post code information in Nauru addresses can be verified.
      • The reference data for Nauru stores the post code as a two-digit number.
      • The postcode can be recognized as a two-digit number and as a five-character string that includes the three-letter ISO country code,For example, „68 “ and „NRU68 “ are recognized as post codes in Nauru
      • The postcode is written with the country prefix „NRU “ in formatted and delivery address lines and without NRU in postal code address elements.
  • Anguilla
    • Postcode Verification
      • Post code information in Anguilla addresses can be verified
      • The reference data contains the post code as a four-digit number,For example, Address Verification recognizes 2640 as a post code in Anguilla.
      • Address Verification writes the postcode as four digits in formatted and delivery address lines and in postal code address elements.
  • Ireland
    • eircode Encoder Accreditation and Improvements
      • The eircode encoder accreditation in Ireland is granted, and the formal requirements defined by the eircode accreditation program for the addition of eircodes to addresses are met.
      • Additionally, multiple improvements are made to the parsing and verification of Ireland addresses.
  • Canada
    • Certification to SERP 2020 Standard
      • Informatica Address Verification is certified to the Software Evaluation and Recognition Program (SERP) 2020 standard for address verification in Canada.
  • Kiribati
    • Postcode Verification
      • Post code information in Kiribati addresses can be verified
      • The reference data contains the post code as a four-digit number.
      • The postcode can be recognized as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, „0107“ and „KI0107“ are recognized as post codes in Kiribati
      • The postcode is written with the country prefix KI in formatted and delivery address lines and without KI in postal code address elements.
  • Montserrat
    • Postcode Verification
      • Post code information in Montserrat addresses can be verified.
      • The reference data includes the post code as a four-digit number.
      • The postcode can be recognized as a four-digit number and as a seven-character string that includes the three-letter ISO country code,For example, „1230 „and „MSR1230 “ are recognized as post codes in Montserrat
      • The postcode is written with the prefix „MSR“ in formatted and delivery address lines and without „MSR“ in postal code address elements.
  • Myanmar
    • Postcode Verification
      • Post code information in Myanmar addresses can be verified
      • The post codes contain seven digits.
  • Namibia
    • Postcode Verification
      • Post code information in Namibia addresses can be verified.
      • The post codes contain five digits.
• TPR-14084: Features and enhancements for Version 6 of the address verification engine:
  • All Countries
    • Fast completion Mode Enhancements
      • Enhanced display of address ranges in Fast completion mode based on the RangesToExpand and RangeExpansionType parameters.
      • Helps users interact with and visualize address ranges more effectively.
      • Retention of Sub-Building Information
        • If you submit an address with sub-building information and the associated reference data doesn’t contain sub-building information at all for the address, Address Verification copies the input sub-building information to the output address.
        • The engine can return two levels of sub-building information in the output.
        • If your input address includes a sub-building descriptor, please enter the full descriptor. If you do not include the range at the end of the input string, you must provide the complete sub-building descriptor along with the range,For example: Enter „APT 7 “ in your input address, instead of „AP „.
    • Additional Data for „V“ or „C“ Scores
      • Allows the engine to return extra data for addresses with Verified (V) or Corrected (C) scores, if available in the reference database.
      • Options:
        • No: No additional data is returned (default).
        • ForAllElements: Returns all available extra data.
        • ForPostalRelevantElements: Returns data relevant to postal delivery.
      • Configure using the DeliverAdditionalSuggestions property in the AVJob.schema.json file.
    • Standardization of Invalid Addresses
      • Standardizes addresses marked as „Invalid“ (I Process Status score) to improve data quality for downstream tasks like deduplication.
      • Configure using the StandardizeInvalidAddresses property in the AVJob.schema.json file.
    • Support for Single-Line Address Input
      • Allows addresses to be submitted in a single-line field for batch, interactive, and Fast Completion modes, simplifying workflows.
    • Automatic Removal of Outdated Reference Files
      • Automatically deletes outdated reference files during initialization to save storage and reduce manual work.
      • How it Works:
        • Deletes files if a newer version exists and is compatible with the engine.
        • The engine determines file age based on version numbers in the file name.
      • Configuration:
        • Set the DeleteOutdatedDataFilesAtInit property in the IDVEConfig.json file:
        • • True: Activates file deletion.
          • False: Default. Keeps outdated files.
    • Multiple Country Identifiers in One Variant
      • Returns detailed country identifiers (e.g., name, ISO three-character code, ISO two-character code, and ISO two-digit code) in a single result variant.
      • Configure this under Outputs Results Variants AddressElements Country in the AVJob.schema.json file.
    • New Function Element: ListDataFilesUsedForOutput
      • Identifies the data sets used during address validation and enrichment.
      • Provides transparency and traceability in validation processes.
    • New Address Type Indicator (N)
      • Introduces „N“ as a new address type indicator, meaning „Not Certain.“
      • If Address Verification cannot determine the type of an address, it returns „N“ as the default to ensure clarity.
  • Austria, Japan, and Korea
    • Recognition of Outdated Addresses
      • Address Verification recognizes outdated addresses and can return either the outdated version or the current version.
      • Configure using the AlternativeHandling property in the AVJob.schema.json file.
  • Denmark
    • Improved parsing of sub-building information in Denmark addresses.
    • Updated reference data for enhanced accuracy.
  • Hong Kong
    • Geocoding Enrichments: Supports geocoding for Hong Kong addresses in the traditional Chinese script, with precision at ArrivalPoint and StreetCenter levels.
    • CAMEO Enrichments: Provides enrichments for Hong Kong addresses in the traditional Chinese script.
  • Kosovo
    • Recognizes Kosovo-specific ISO country codes (XKS and XK).
    • Supports geocoding for Kosovo addresses to StreetCenter precision.
  • Myanmar
    • Verifies and corrects Myanmar addresses containing 7-digit postal codes.
  • Anguilla
    • Postcode information in Anguilla addresses can be verified.
    • The reference data contains the postcode as a four-digit number.
    • Address Verification can recognize the postcode as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, Address Verification recognizes „2640“ and „AI2640“ as postcodes in Anguilla.
    • Address Verification writes the postcode with the country prefix AI in formatted and delivery address lines.
    • It also writes the postcode with the country prefix in the PostalCode address element when you set the Type property on the element to Formatted. Otherwise, Address Verification returns the postcode without the country prefix.
  • Australia, New Zealand, and United States
    • Approval for Address Certification
      • Address verification in Australia, New Zealand, and the United States is formally certified by their respective postal authorities
  • Australia
    • Local Government Area Names and Codes
      • Local Government Area names and Local Government Area codes can be returned as enriched address outputs,For example, Address Verification recognizes Wanneroo as a Local Government Area name and „58760 “ as the Local Government Area code
  • Samoa
    • Postleitzahlen in Samoa können sowohl als vierstellige Zahl als auch als sechsstelliger String erkannt werden, der den zweibuchstabigen ISO-Ländercode enthält,For example, Address Verification can recognize „1334“ and „WS1334“ as post codes in Samoa
    • Zuvor wurden nur vierstellige Postleitzahlen in Samoa erkannt
  • Saint Vincent and the Grenadines
    • Post codes in addresses of Saint Vincent and the Grenadines can be recognized as a four-digit number or as a six-character string that includes the two-letter ISO country code,For example, Address Verification recognizes „0120“ and „VC0120“ as post codes in Saint Vincent and the Grenadines.
  • Norway
    • Post Code Recognition and Validation
      • Post code information can be recognized as a four-digit number in Norway addresses.
      • Address Verification validates addresses with sub-building information.
  • Malawi
    • Post code information can be recognized as a six-digit number in Malawi addresses,For example, Address Verification recognizes „102010“ as a post code in Malawi
  • Liberia
    • Post code information can be recognized as a four-digit number in Liberia addresses,>For example, Address Verification recognizes „4000“ as a post code in Liberia
  • Canada
    • Certification for Address Verification
      • Post is certified to the Software Evaluation and Recognition Program (SERP) 2020 standard for address verification in Canada.
  • United States
    • Support for CASS Cycle „O „
      • Supports all requirements of the Coding Accuracy Support System (CASS) Cycle O standard
      • Adds the following features to complete Cycle „O “ support:
      • • Support for LACSLink False Positive Indicator: Returns a single-character value identifying an address found in the False Positive hash table (value „Y“).
        • Support for Non-Delivery Days Flag: Identifies addresses that cannot receive mail on specific days of the week with a „Y“ value in the Non-Delivery Days Flag field.
        • Enhanced DPV Footnotes: Supports enhanced DPV footnotes for return codes introduced by the USPS in Cycle „O „.
        • Verification of Non-Default Locality Names in Cross-State Addresses: Retains non-default locality names when city name is valid for ZIP Code but not default.
        • TotalDPS Support: Supports TotalDPS rules for verification calculations in cases with multiple addresses sharing a Delivery Point Value.
        • Updated Form „3553“ Compliance: Supports updated data requirements of Form „3553“ as defined by USPS in August 2022.
        • DPV Drop Indicator Recognition: Adds DPV Drop Indicator field for values reflecting the status of addresses in the DPV Drop Indicator table.
    • Fast Completion Mode Enhancements
      • Recognition of „ZIP+4“ Codes: Post can recognize and return „ZIP+4“ Codes in Fast Completion mode.
      • Address Verification reads „ZIP+4“ data and returns a five-digit ZIP code for non-deliverable addresses.
  • Nauru
    • Postcode information in Nauru addresses can be verified.
    • The reference data for Nauru stores the postcode as a two-digit number.
    • The postcode can be recognized as a two-digit number and as a five-character string that includes the three-letter ISO country code,For example,“68″ and “ NRU68″ are recognized as postcodes in Nauru.
    • Post writes the postcode with the country prefix „NRU“ in formatted and delivery address lines and without NRU in postal code address elements.
  • Namibia
    • Postcode information in Namibia addresses can be verified.
    • The post codes contain five digits.
  • Montserrat
    • Postcode information in Montserrat addresses can be verified.
    • The reference data includes the postcode as a four-digit number.
    • Address Verification can recognize the postcode as a four-digit number and as a seven-character string that includes the three-letter ISO country code,For example, Address Verification recognizes „1230“ and „MSR1230“ as postcodes in Montserr.
    • Address Verification writes the postcode with the prefix „MSR“ in formatted address line and country-specific locality line elements and without the prefix in other elements.
  • Kiribati
    • Postcode information in Kiribati addresses can be verified.
    • The reference data contains the postcode as a four-digit number.
    • Address Verification can recognize the postcode as a four-digit number and as a six-character string that includes the two-letter ISO country code,For example, Address Verification recognizes “ 0107″ and „KI0107“ as postcodes in Kiribati.
    • Address Verification writes the postcode with the country prefix KI in formatted and delivery address lines and without KI in postal code address elements.
  • Thailand
    • Supports geocoding for Thai addresses in Thai script with precision at levels such as Rooftop, ArrivalPoint, StreetCenter, LocalityCenter, and PostalCodeCenter.
• TPR-13869: Internal fields post.NumberAdd and post.Number2Add were completely removed as these fields were not get populated by any values in address validation.
• TPR-13857: The profile attribute elementAbbreviation is now supported for version 6.x of the internal addressengine. (since 2025/06/19, 12.0)
• TPR-13845: Post Engine V6 engine now supports the internal field post.Territory.
• TPR-13836: Removed support for unused internal fields post.CityAddInfo, post.SubCityAddInfo, post.LocalityAddInfo.
• TPR-13827: Added support post.DeliveryServiceTo, post.DeliveryServiceFrom, post.NumberTo and post.NumberFrom for V6.
• TPR-13815: Removed post profile attribute countryCodeType and internal field post.CountryCode. Added support for post.CountryISO3, post.CountryISO2 and post.CountryISONumber internal fields for V6 engine
• TPR-13323: Landscape Engine now supports fallbacks for certain postal codes in Japan, which can be set via the following new attributes:
  • fuzzy.PostalCodeFallback: when activated the engine will try to remove ambiguity by validating the postal code only.
  • fuzzy.PostalCodeFallbackReturnCode: can be used to change the default returnCode (0) used when the fallback has taken place.

  (since 2025/06/19, 12.0)

• TPR-13227: Tolerant Post now with the new version of the internal address verification engine (5.16.4)
  • New Features and Enhancements
  • • Ghana: Address Verification can recognize post code information as a three-digit number and as a five-character string that includes the two-letter ISO country code in Ghana addresses. For example, Address Verification can recognize GA183 as a post code in Ghana.
    • Liberia: Address Verification can recognize post code information as a four-digit number in Liberia addresses.
    • Malawi: Address Verification can recognize post code information as a six-digit number in Malawi addresses.
    • Saint Lucia: Address Verification can recognize post code information in Saint Lucia addresses in the following formats:
      • As a five-digit number.
      • As a string that includes the two-letter ISO country code before the five-digit number and that adds a space between the fourth and fifth characters.
    • Saint Vincent and Grenadines: Address Verification can recognize post code information as a four-digit number and as a six-character string that includes the two-letter ISO country code in Saint Vincent and the Grenadines addresses.
    • Samoa: Address Verification can recognize post code information as a four-digit number and as a six-character string that includes the two-letter ISO country code in Samoa addresses.
  • Bug Fixes
  • • Belgium:Address Verification returns a different address from the input address.
    • Spain: Address Verification returns duplicate addresses from multiple input addresses in Interactive mode.
    • United Kingdom: Address Verification returns incorrect building names from the input addresses.
• TPR-13005: The static path element inst/1 can now be omitted from the requsts sent to the admin service. (since 2025/06/19, 12.0)
• TPR-12982: Changes made when using mode=“FASTCOMPLETION“ for Post Engine V6:
  1. The FastCompletion mode for the V6 engine requires an input mapping of the internal field post.AddressComplete. From now on though, the project can still start up without it and the error handling will be done on request level (see point below).
  2. If the input mapping is missing for FastCompletion mode or if mapping is present but there are no values provided, then a post.ProcessStatus = „I“ will be returned with the new post.ReturnCode = „4“.
• TPR-12896: The attribute fuzzyCompatibility (only for V5 engine) is now always enabled by default. The attribute itself was removed.
• TPR-12614: The docker compose shipment now includes Prometheus and Grafana services. (since 2025/06/19, 12.0)
• TPR-12599: A new /info endpoint for all products has been introduced. For example: http://localhost:8080/postService/info. This endpoint can be used to monitor details about the product. For example: Post info endpoint has unlock code and its corresponding expiration date information. (since 2025/06/19, 12.0)
• TPR-12499: Reworked the installer to support the new microservice architecture and a simplified option set. (since 2025/06/19, 12.0)
• TPR-12058: Adjusted the shipped example configurations and templates to reflect the prioritization of the new address verification engine V6.
• TPR-12017: TOLERANT Products are restructured to use the microservice architectural and organizational approach:
  • services can be started as standalone applications
  • reverse proxy is used for the communication between the services
  • the on-premise installation needs multiple ports
  • the product is split into multiple smaller docker images
• TPR-11989: Cleaned up post.ProcessStatus implementation and documentation in the manual to correctly reflect the functionality of the new address verification engine (V6).
• TPR-11234: Following changes to the license checking were made:
  • TOLERANT Products now ship with an embedded license for initial product tests.
  • Changes in the license file will be reflected automatically, removing the need to reconfigure the service.
  • Both license volume and index volume are now checked separately for each project (previously, this was a global check).
  • A new rate limiter was implemented, allowing you to configure a rate limit via the new license attributes: rate and period.
• TPR-10958: It is now possible to configure JVM options via specific environment variables (see tolerantEnv.sh/bat for examples).
• TPR-10739: Improved and extended validation of path-values with better error messages.
• TPR-312: It is now possible to configure the JVM separately for Batch and Service via environment variables. To make use of this feature, the file setenv.sh/bat needs to be copied from config/templates to config and adjusted according to inline comments.

Security

• TPR-12671: It is now possible to configure the software to limit file access to the predefined TOLERANT directories. This setting is activated per default. (since 2025/06/19, 12.0)

Manual

• TPR-12039: Cleaned up several labels and info texts in GUI as well as descriptions in the manual to increase consistency and information value of some configuration attributes.
• TPR-10445: Extended manual to reflect new upload functionality via GUI.
• TPR-10439: Extended manual for new search mode GEOCODETOADDRESS.
• TPR-10162: The annex of supported countries has been updated. The data applies to both engines V5 and V6. Single Line Validation is available for all supported countries. For Table A.1, „Part of“ column was added and the legend was adapted.

Fixed Bugs

Configuration and Administration GUI

• TPR-14430: The first element of type InputFieldmap will be used, if the mode attribute is not specified in the service configuration. (since 2025/06/19, 12.0)
• TPR-14404: The GUI now displays an error banner when trying to start an inactive project. (since 2025/06/19, 12.0)
• TPR-14364: Reworked the unlockcode/licence view in GUI, to enable smooth switching between V5 and V6 engines and the respective unlockcodes or .LIC licence files.
• TPR-13375: Improved error handling of wrongly configured mode attribute in postProfile element.
• TPR-11790: Removed the possibility (via portal) to delete the local installation in which the portal itself is running.
• TPR-10963: Improved error handling when trying to update a read-only file via GUI.
• TPR-10423: The checkbox „Use synonyms“ now correctly triggers the synonym processing in file preview in GUI. All environment variables are now replaced when parsing the configuration from JSON. (since 2025/06/19, 12.0)
• TPR-10299: The GUI now correctly triggers the notification that requests the user to save the configuration when he navigates to another view. (since 2025/06/19, 12.0)
• TPR-10128: Improved view of output- and logfiles when executing a synonym test via GUI.
• TPR-10123: Long batch runs (30min +) executed via GUI can no longer lead to lost sessions in browser.
• TPR-10122: The wizard for executing background jobs via GUI now scrolls properly to the bottom in case of long console outputs.

Client GUI

• TPR-13454: To ensure consistent updates, the Juxtaposition tab in the Client GUI results view now refreshes correctly in all cases.
• TPR-11168: Removed redundant validation logic for Client GUI and GeocodeToAddress mode regarding the input fields. Checks are now done exclusively in the backend service.
• TPR-10327: Request history in Client GUI is now preserved when switching between Admin GUI and Client GUI. (since 2025/06/19, 12.0)
• TPR-10297: Fixed some minor bugs and added small usability improvements in the Client GUI. (since 2025/06/19, 12.0)

Service

• TPR-13116: Supplementary fields of the V6 Engine are now fully supported.
• TPR-11433: The service can now be properly registered and started under Windows via Windows services.
• TPR-10858: The post.ReturnCode 46 is not returned on missing or invalid V6 license
• TPR-10857: Detection of encoding is now limited to a certain number of bytes to prevent out-of-memory-error
• TPR-10378: File based databases no longer get locked when executing certain admin commands.

General

• TPR-14320: Bugfixes for Version 6 of the address verification engine:
  • All Counties
    • HDS-17759 : The Address Verification engine may fail to access all available memory, leading to issues in starting multiple function servers if the previous engine process ended without calling the IDVE_Deinitialize function.
    • HDS-29166 : Address Verification fails due to insufficient memory in interactive mode in the following scenario:
      • You set the ResultCount property to „1“ and the NumericRangeExpansion property to Full.
      • The reference data contains more than one suggestion for a numerical element type, such as building or sub-building numbers.
    • HDS-17751 : The Address Verification engine does not employ retry mechanisms to resync the engine and the function servers in cases where Linux operating system-level calls are interrupted by incoming signals.
    • HDS-17062 : Address Verification does not return an address in ASCII characters when you set the LimitLatinCharacters attribute to ASCII. This issue arises if the input address uses ASCII or Latin characters and you set the PreferredScript property to Preserve.
    • HDS-16982 : Address Verification drops sub-building level 2 information from a second address line in the following scenario: If the second address line contains information for sub-building level 1, and the first address line contains alphanumeric house numbers where digits and letters are separated by a character space.
    • HDS-16366 : Expired data licenses appear active to the Address Verification engine, causing inaccuracies.
    • HDS-16173 : Address Verification does not return an address in GeocodeToAddress mode if the house number contains an alphabetic character followed by digits.
    • HDS-16156 : Address Verification may not return enrichment or geocoding data with an output address if you specify a non-default option on the PreferredScript or PreferredLanguage properties.
    • HDS-10731 : Address Verification encounters issues when validating addresses in QuickCapture mode, especially for non-standard values like fractional house numbers (e.g., 3/4) and alphabetical ranges.
    • HDS-22401 : Address Verification included incorrect JSON schema files in some release packages.
    • HDS-22575 : Single-line input fails in Interactive mode.
    • HDS-23780 : Address Verification returns an incorrect Result Status for locality data in Interactive mode. The Result Status field returns a value of „1“ instead of 6 in the following cases:
      • The input address does not have a house number.
      • The input address does not have a correct mailbox.
    • HDS-23793 : Address Verification can ignore a house number range in the reference data and try to correct a valid house number in an input address to another valid house number.
    • HDS-24981 : Address Verification does not return Arrival Point geocoordinates when a user configures the AliasHandling property as PreserveAll.
    • HDS-21124 : Address Verification returns an alternative address that the reference data flags as no longer in use when you set the Match attribute on the OutdatedAddress property to Off.
    • HDS-21123 : Address Verification returns an Extended Result Status value of Deprecated for all elements in an outdated address and does not distinguish between deprecated and non-deprecated elements.
    • HDS-21122 : Address Verification returns a Result Status value of 2 and not 3 when a new element replaces an outdated element in an address.
    • HDS-19274 : Address Verification does not preserve the character case of delivery address line, postal address line, or formatted address line data.
  • Germany
    • HDS-20030 : Address Verification adds an extra character space between the words in a two-word locality name for correct parsing.
    • HDS-13070 : Address Verification fails to recognize ‚post nummer‘ as a variant of ‚postnummer,‘ leading to incorrect parsing.
    • HDS-19777 : Address Verification corrects the street name abbreviation St. (Saint) to Str. (Strasse) when the GlobalPreferredDescriptor attribute is SHORT.
    • HDS-25413 : Address Verification returns an „I “ process status for valid input addresses.
    • HDS-24063 : Address Verification returns suggestions when you enter a PO Box number range but does not return suggestions when you enter a single PO Box number value.
    • HDS-25413 : Address Verification returns an „I “ process status for valid input addresses.
    • HDS-24063 : Address Verification returns suggestions when you enter a PO Box number range but does not return suggestions when you enter a single PO Box number value.
  • Greece
    • HDS-16468 : Address Verification adds the tonos (`) character to alphabetic characters in the output address when the PreferredScript attribute is set to LATIN-1.
  • India
    • HDS-14817 : Address Verification can drop input detail from a delivery address line in an address. This issue arises in addresses that contain multiple building and sub-building values.
  • Japan
    • HDS-27605 : Address Verification returns archived and new locality names instead of new locality names only if the input address has postal code „7000921 „.
    • HDS-27017 : Address Verification does not return Locality „2“ and Locality „3“ values in the output.
    • HDS-26800 : Address Verification returns subbuilding information in the street field.
    • HDS-26126 : Address Verification does not parse 1 0 2 3 as a subbuilding and returns a C process status.
    • HDS-26125 : Address Verification does not parse and validate input addresses when you use single-line validation.
    • HDS-21587 : Address Verification returns incorrect address outputs when you enter addresses in Japanese language.
    • HDS-19535 : When you enter a complete postcode in Fast completion mode, Address Verification returns addresses to street level and not to house number level.
    • HDS-17437 : Address Verification adds a character space in a house number when you use the default preferred script option and omit the character space when you set the PreferredScript attribute to Postal Admin. The issue arises when you run Address Verification in batch mode as a web service.
    • HDS-23366: Address Verification does not recognize Locality “ 2″ information on a delivery address line.
    • HDS-24299 : Address Verification cannot parse a Japan address in the following scenario:
      • The address contains locality „1“ and other locality information on the same address line.
      • The address does not include a postcode.
  • South Korea
    • HDS-15839 : Address Verification can drop „HO“ and „DONG“ information from an address when you select a Latin preferred script.
    • HDS-15838 : Address Verification can drop „HO“ and „DONG“ information from an address when you select a Latin preferred script.
    • HDS-15778 : Address Verification can fail to identify sub-building data correctly and can drop the data from the output address.
  • United States
    • HDS-20350 : Address Verification moves alphanumeric sub-building information to the residue field in cases where the sub-building information is the only entry on the second delivery address line.
    • HDS-19375, HDS-20038 : Address Verification fails to return useful ZIP Code data in batch and interactive modes when the input address contains province and locality information only.
    • HDS-19096 : Address Verification does not return additional sub-building suggestions for an address with a „V“ or „C“ score in interactive mode.
    • HDS-18413 : Address Verification can validate ZIP Code inputs with leading zeros and return the six-digit equivalent when a „ZIP+4“ Code is input.
    • HDS-20350 : Address Verification moves alphanumeric sub-building information from a second address line to a residue field if the sub-building information is the sole entry on the second address line.
    • HDS-19375, HDS-20038 : Address Verification fails to return useful ZIP Code data in batch and interactive modes when the input address contains province and locality information only.
    • HDS-19096 : Address Verification does not return additional sub-building suggestions for an address with a“ V“ or „C“ score in interactive mode.
    • HDS-19084 : Address Verification fails to recognize a sub-building value in the following scenario: The street name includes an ordinal number, and the sub-building information does not include a descriptor.
    • HDS-18413 : If an input ZIP Code omits leading zeros from the +4 element of the code, Address Verification can validate the ZIP Code and return the six-digit input in place of the ZIP+4 Code.
    • HDS-16539 : Address Verification does not return a value for the UsedVerificationLevel property.
    • HDS-16268 : Address Verification does not recognize SUITE or SUTE as variant spellings of SUITE.
    • HDS-16284 : Address Verification fails to recognize „BIN“ as part of a street name when the street descriptor value is abbreviated.
    • HDS-16045 : Address Verification does not verify an address that includes multiple street descriptors, such as in the following scenario: The street name is abbreviated (e.g., PARK AVENUE WEST) but contains a post-directional value.
    • HDS-11850 : If an input address contains a unique ZIP Code, Address Verification corrects other input values and returns the address that the ZIP Code represents.
    • HDS-21760 : Address Verification fails to recognize the strings „PO „or „BOX „as part of a valid street name in batch and interactive modes.
    • HDS-24194 : Address Verification returns Process Status and Result Status values of C+0 for a United States address in cases where the values „C+2“ are appropriate. The issue can arise when the address contains a unique ZIP Code and does not contain street data.
    • HDS-27336 : Address Verification returns inconsistent address outputs.
    • HDS-27334 : Address Verification returns a „C“ process status for an address, instead of a „V“ or an „“I process status.
    • HDS-25878: Address Verification returns incorrect subbuilding in the output. The engine returns suite number as building number.
    • HDS-25626: Address Verification does not return High Rise Default in the output.
    • HDS-25608 : Address Verification returns valid addresses with an „I“ process status.
    • HDS-24469 : Address Verification cannot parse province details in the output.
    • HDS-23245 : Address Verification changes the format of the postal code for invalid addresses in certified mode.
    • HDS-23244: Address Verification returns incorrect ZIP Code with a „C “ process status.
    • HDS-23223 : Address Verification returns alphanumeric ZIP Codes in the address output.
    • HDS-21992 : Address Verification returns different address outputs for similar input addresses.
    • HDS-28911 : Address Verification drops valid state information from an AdministrativeDivision level 2 field when the AdministrativeDivision level 1 field is empty.
    • HDS-28771 : Address Verification returns an „I2“ process status for an address that combines ATTN information and PO BOX information in a partially-filled or unfilled address.
    • HDS-28769 : If the AdministrativeDivision field is empty and the Locality field contains a close misspelling of a state name in an input address, Address Verification corrects the locality to the state name and parses the state name to the AdministrativeDivision field in the output address.
    • HDS-28734 : Address Verification returns a higher-than-expected MatchStatus score when your input address has an invalid house number. The issue is observed in Certified mode.
    • HDS-28533 : Address Verification swaps the time zone name and time zone code values in the output.
    • HDS-28442 : Address Verification returns incorrect county information in the output when you set the PreferredVerificationLevel and MinimumVerificationLevel properties to All or Street.
    • HDS-28283 : If an input address matches a reference address with a PO Box number that begins with a leading zero, Address Verification returns an incorrect +4 extension with the five-digit ZIP Code.
    • HDS-28198 : Address Verification returns an „I“ process status for valid input addresses in Certified mode in the following scenario:
      • The address includes abbreviated street directional and street descriptor values.
      • You add periods after the street directional and street descriptor abbreviations.
    • HDS-28197 : Address Verification does not recognize „TWP “ as an abbreviation for TOWNSHIP. The issue is observed in Certified mode.
    • HDS-28196 : Address Verification returns a low MatchPercentage value in Certified mode for a valid address when the sub-building value does not follow a sub-building descriptor.
    • HDS-28194 : Address Verification fails to verify an address when the name of the county in which the address is located forms part of the street name. The issue is observed in Certified mode.
    • HDS-28192: Address Verification fails to validate an address when the street information contains multiple abbreviated descriptors, including „CH“ for „CHURCH“. The issue is observed in Certified mode.
    • HDS-28191: When the house number information is ambiguous, Address Verification assigns a higher match score to a combination of matching house number and locality information than to a combination of matching street name and locality information. The issue is observed in Certified mode.
    • HDS-28190: When the locality and the ZIP Code in an address do not match, Address Verification concludes that the two address parts are equal and fails to prioritize the locality information. The issue is observed in Certified mode.
    • HDS-28189: Address Verification fails to validate a highway address correctly when the word STATE or a state name appears in the highway name and the words HIGHWAY or ROUTE are absent. The issue is observed in Certified mode.
    • HDS-28182: Address Verification stops unexpectedly while processing an address that contains a sub-building descriptor without a sub-building value. The issue is observed in Certified mode.
    • HDS-28178: Address Verification fails to recognize abbreviations for COUNTY, STATE, and US highway locations and also fails to validate the addresses correctly. For example, Address Verification fails to recognize CTY ROAD as COUNTY ROAD, SR as STATE ROUTE, and US as HIGHWAY. The issue is observed in Certified mode.
    • HDS-28174: Address Verification does not recognize the directionals as streets that you enter. The engine fails to apply the correct street name to the input address.
    • HDS-16045: Address Verification does not verify an address that includes multiple street descriptors. The issue arises in the following scenario:
      • The descriptor in the street name is abbreviated, for example PARK AVENUE WEST is abbreviated to PARK AVE WEST.
      • The street information contains a post-directional value with dual indicators, for example PARK AVE WEST NW.
    • HDS-10862: When you verify an address that contains a „ZIP+4“ Code or a nine-digit postal code in Fast completion mode, Address Verification does not output the +4 digits.
  • Spain
    • HDS-14191 : In batch mode, Address Verification can return an „I3“ status score for an address that Address Verification earlier suggested in interactive mode.
    • HDS-24744, HDS-24468 : Address Verification returns a „V“ process status when you enter addresses with an extraneous preposition DEL in a valid street name. The engine returns an „I“ process status for the same addresses without the DEL preposition.
    • HDS-13238: Address Verification can return an „I2“ process status for an address that includes a valid post code and a „C4“ process status for the same address without the post code. The issue arises when the match scores for the non-post code values exceed the score for the post code.
    • HDS-16606: Address Verification returns incorrect suggestions for an input address in the following scenario:
      • The address contains an alphanumeric house number.
      • The address contains PRAL as a sub-building identifier on a delivery address line.
    • HDS-16871: Address Verification does not recognize house numbers in the following scenario:
      • The house number contains alphanumeric characters.
      • The house number contains a dash symbol, for example „11-D“.
    • HDS-21855: Address Verification can add the extraneous preposition DEL to a valid street name in a Spanish address, which can reduce the Result Quality score for the address.
    • HDS-19270: Address Verification can fail to match a street name with the corresponding street in the reference data in the following scenario:
      • The input address contains the address on a delivery address line.
      • The delivery address line contains unrecognized data that the engine parses to a residue field .
  • Romania
    • HDS-19479 : Address Verification returns a sub-building pre-descriptor in the post-descriptor position.
  • Portugal
    • HDS-15158 : When an address contains LOTE as a house number descriptor, Address Verification fails to parse the house number information to a house number field and instead passes the information to a building field.
    • HDS-20888: Address Verification returns incorrect address inputs with C process status.
    • HDS-13972 : Address Verification fails to recognize Nº as an abbreviation of Número and fails to recognize DT as an abbreviation of Direto when DT does not follow a house number.
  • Netherlands
    • HDS-13784 : When an input address contains range-based house number values with leading zeros, Address Verification fails to add the zeros to the output in Fast completion mode.
  • Korea
    • HDS-14843 : Address Verification can drop input detail from an address when you select a Latin preferred script and set the PreferredLanguage attribute to ENGLISH.
    • HDS-26781: Address Verification returns incorrect transliteration outputs with PreferredLanguage.ENGLISH and PreferredScript.ASCII_SIMPLIFIED.
  • Japan
    • HDS-19535 : When you enter a complete postcode in Fast completion mode, Address Verification returns addresses to street level and not to house number level.
    • HDS-17437 : Address Verification adds a character space in a house number when you use the default preferred script option and omit the character space when you set the PreferredScript attribute to Postal Admin. The issue arises when you run Address Verification in batch mode as a web service.
    • HDS-23366: Address Verification does not recognize Locality 2 information on a delivery address line.
    • HDS-24299: Address Verification cannot parse a Japan address in the following scenario:
      • The address contains locality „1“ and other locality information on the same address line.
      • The address does not include a postcode.
  • China
    • HDS-14989: Address Verification can return a building name as house number or street name information.
    • HDS-28537 : Address Verification can correct a valid street name in the English language to another street name when the name contains a directional indicator.
  • Colombia
    • HDS-23081: Address Verification does not return Colombia province information in formatted address line output. As a result, Address Verification does not return a „V status code for the address.
  • Czech Republic
    • HDS-21327: Address Verification returns building and house number data in an incorrect format on delivery address lines in Czech Republic addresses.
  • Indonesia
    • HDS-21329: Address Verification may not parse a locality „2“ value from an unfiled address.
    • HDS-22046: Address Verification does not recognize the special character „-“ in alphanumeric house number data.
  • Italy
    • HDS-22432: Address Verification parses invalid Post Office Box data in an Italian input address as a building instead of deleting or moving it to the Residue field.
  • Kenya
    • HDS-20371: Address Verification can return multiple candidate matches and an „I“ process status value for an address.
  • Malaysia
    • HDS-19464: Address Verification can return an „I3“ process status for an address that includes a valid locality name and a C4 process status for the same address without the locality name.
  • Canada
    • HDS-27667: Address Verification does not preserve the French language in an input address when you set PRESERVE as the preferred language property.
    • HDS-27577: Address Verification shuts down unexpectedly with some address inputs in Certified mode.
    • HDS-28897 – Address Verification shuts down unexpectedly when an address contains a large number of repeating province codes. For example, the engine shuts down when an address contains fourteen province codes.
    • HDS-28872 : Address Verification doesn’t parse a house number in an input address correctly if you put a comma after the house number. The engine merges the house number and the street in the output.
    • HDS-26559: Address Verification returns a process status of „V“ or „A“ instead of I when you set the Address verification level to Premise and your input address has an invalid street name.
    • HDS-26558: Address Verification rejects an address that does not have subbuilding information, when you set the preferred verification level to All and the minimum verification level to Premise.
    • HDS-21577: Address Verification assigns a „C“ status to an invalid address that mixes rural route and P.O. Box information and duplicates the value „BOX“ in the output address.
    • HDS-18919: Address Verification returns a different post code when you add a suite number to an input address.
  • Ecuador
    • HDS-23674: Address Verification moves ‚casa‘ to a residue field in order to parse street details.
  • Hong Kong
    • HDS-25866: Address Verification does not correctly parse subbuilding details.
    • HDS-25751 : When an input address combines building and sub-building values in the same field, Address Verification doesn’t parse all building-level data to the output address. The engine additionally fails to return a V process status when the input address concerned is correct.
  • Thailand
    • HDS-27410: Address Verification shuts down unexpectedly with some address inputs.
  • United Kingdom
    • HDS-26248: Address Verification returns incorrect output with a „C“ or a „V“ process status.
    • HDS-22565: Address Verification returns incorrect building name in output.
    • HDS-24035 : Address Verification parses building number as a house number in the following scenario:
      • The address includes building and sub-building information on a single line.
      • The building information does not include a building descriptor such as UNIT.
  • Belgium
    • HDS-29264 : Address Verification returns valid input addresses with an I process status.
  • Gibraltar
    • HDS-23673 :Address Verification does not parse street and building information to an output address when the input address contains ‚Gibraltar‘ as Locality „2“ information.
  • Turkey
    • HDS-21754 : Address Verification fails to recognize the house number in an input address when the delivery address line also contains building and sub-building information.
• TPR-14316: Bugfixes for Version 5 of the address verification engine:
  • All Countries
    • HDS-7821, HDS-7823 : When you call the address verification engine in a web service, a validation error might cause the engine to time out in fast completion mode.
    • HDS-7541: The Address Verification engine might stop unexpectedly when the geocoding database includes corrupt data.
  • Canada
    • HDS-8392, HDS-8294 : Address Verification can return incorrect geocodes for an input postal code when the data in the geocode database contains errors. It can also provide a locality-level status code (EGC6) for the postal code geocodes.
    • HDS-7498 : Address Verification returns a „Vx “ status for an address and not an Ix status in certified mode when the available street information comprises a number only and the number matches a rural route address.
    • HDS-7497 : Address Verification returns a „Vx “ process score and not an Ix score for a general delivery address containing delivery line address line 1.
    • HDS-7495 : Address Verification returns a Cx process score in batch and certified modes for addresses with ambiguous or incomplete P.O. Box information.
    • HDS-9705 : Address Verification can fail to recognize LN as an abbreviation for LANE in a Canada address and return an Ix process status for the address.
    • HDS-13375 : When you call the address verification engine in a web service from Informatica Data Quality, the engine might stop unexpectedly.
    • HDS-12093: When you call the address verification engine in a web service from Informatica Data Quality, the engine might stop unexpectedly.
    • HDS-11208: Address Verification can return a locality name without an expected dash symbol in certified mode.
    • HDS-10755 : When an input address includes rural route information, Address Verification does not move the rural route information to the line below the first line in the following scenario:
      • The input address contains additional delivery information, such as Site Camp.
  • Slovakia
    • HDS-17985 : Address Verification returns the letter „L“ in place of the Roman numerals I and II in an address in Slovakia.
    • HDS-8175:Address Verification can fail to validate an address that contains accented characters if you enter the address data with the unaccented versions of the characters. For example, Address Verification does not recognize „Zizkova“ as an alternative version of „Žižkova.“ The issue is also observed in other countries that use accented Latin-2 characters to record an address.
  • Australia
    • HDS-14190 : Address Verification can split an alphanumeric sub-building value and write the new values to house number and street fields respectively.
    • HDS-14020 : Address Verification can parse the string „NORTHERN“ as a province name.
    • HDS-14018 : Address Verification can assign different DPID values to the same address when you add or remove Locality 2 information.
    • HDS-13752 : If you validate an address that contains multiple sub-buildings and omit sub-building information, Address Verification can return a single sub-building with an Ix score.
    • HDS-13722, HDS-13066 : Address Verification can change locality information in an address rather than correct the house number or invalidate the address.
    • HDS-13605 : Address Verification appends the directional abbreviation „S“ to a street name when the reference data contains the same address with a North and South directional abbreviation.
  • Austria
    • HDS-13234 : Address Verification fails to recognize St. as the sub-building descriptor „Stiege“ in an address line and parses the information incorrectly.
  • Brazil
    • HDS-12571 : Address Verification parses sub-building information incorrectly if you enter the information on its own on the second address line.
  • British Indian Ocean Territory
    • HDS-10006 : Address Verification returns the postal code as a single string rather than with a character space between the fourth and fifth characters in the code.
  • Finland
    • HDS-7964 : When parsing an address with an incorrect sub-building descriptor, Address Verification can return the sub-building number in the house number field.
    • HDS-7963 : When an input address contains an alphanumeric house number that precedes a sub-building number, Address Verification can fail to parse the alphanumeric house number to a house number field.
  • Denmark
    • HDS-12143 : Address Verification can split the digits of a house number that includes a dash symbol into House Number and Sub-Building fields.
  • Hungary
    • HDS-31 : Address Verification may fail to validate an address because the reference data does not contain the full range of house numbers for the street.
  • Indonesia
    • HDS-21329 : Address Verification may not parse a locality 2 value from an unfiled address.
    • HDS-22046: Address Verification does not validate correct house number data.
  • India
    • HDS-10720 : Address Verification can return an Ix status score for an address in the following scenario:
      • The address identifies a business in an industrial estate.
      • The industrial estate name includes an organization abbreviation.
    • HDS-20015 : Address Verification writes the post code to a house number field in the following scenario:
      • The input address contains the post code in a locality field and contains the locality in a post code field.
    • HDS-1360 : If you use a province abbreviation in an address, Address Verification returns a lower than expected match score for an address that includes a province abbreviation.
    • HDS-21578 : The address verification engine can remove building information from an address during validation. The issue is observed in Informatica Master Data Management applications.
    • HDS-20930 : Address Verification parses valid delivery address line information to the Organization field.
    • HDS-4835: Address Verification fails to return BENGALURU as the preferred version of BANGALORE.
    • HDS-45 : Address Verification can return a redundant apostrophe after the digit in an ordinal street name, for example, 4TH CROSS ROAD.
    • HDS-15591 : Address Verification does not recognize Marg as a post-descriptor for a street name.
    • HDS-15579 : Address Verification can parse a building name as an organization name in the following scenario:
      • The building name is an abbreviation, for example D D A.
      • The input address contains the building name on a formatted address line.
    • HDS-14817 : Address Verification can drop input detail from a delivery address line in an address. The issue arises in addresses that contain multiple building and sub-building values.
    • HDS-14576 : The address verification engine can run out of memory in the following scenario:
      • You set the Format Delimiter to Comma.
      • The address record duplicates street and locality information on two delivery address lines.
  • France
    • HDS-8462 : When verifying a CEDEX address in fast completion mode, Address Verification can return different status codes values in the address suggestions if the input CEDEX includes one or more character spaces at the end of the address line.
    • HDS-17048: Address Verification removes apostrophe characters from an address in France when it reads reference data that contains diacritics.
  • Singapore
    • HDS-17734 : The Address Verification stops unexpectedly while processing a valid Singapore address. The issue is observed for an address at an industrial complex that does not contain street information.
  • Germany
    • HDS-8257 : When an input address contains range-based house number information in a delivery address line input, Address Verification incorrectly parses the range-based house number information to a street field.
    • HDS-8256 : When an input address contains the airport building name TERMINAL in a delivery address line, Address Verification parses the information as street information.
    • HDS-13070: Address Verification fails to recognize ‚post nummer‘ as a variant of ‚postnummer‘ and can parse a ‚post nummer‘ value to a building field.
    • HDS-19777 : Address Verification corrects the street name abbreviation St. (Saint) to Str. (Strasse) when the GlobalPreferredDescriptor attribute is SHORT.
    • HDS-19763: Address Verification returns multiple versions of a province name when the PreferredScript attribute is PRESERVE.
    • HDS-24137 : Address Verification reference database does not have house numbers for some addresses with new streets. As a result, Address Verification cannot validate such house numbers.
  • Malaysia
    • HDS-19464 : Address Verification can return an „I3 “ process status for an address that includes a valid locality name and a „C4 “ process status for the same address without the locality name.
  • Japan
    • HDS-8231 : Address Verification fails to recognize certain Kanji values when no character space appears between them.
    • HDS-7950 : When building information appears out of sequence in an address, Address Verification can drop the information from the address or move the information to residue.
    • HDS-10004 : If you submit an older version of an address for verification in Japan, Address Verification might match the address to the current version of the address in the reference data. The issue can arise regardless of the MatchingExtendedArchive attribute value.
    • HDS-10002 : When you verify an address that includes an obsolete aza element, Address Verification moves the obsolete aza element to residue but does not flag the address as invalid. , Address Verification returns an Ix process status value for the address.
    • HDS-9894 : Address Verification can add the value „番地 “ as street information to an output address when „番地 “ appears in the input address as locality information.
    • HDS-8314 : Address Verification can add an incorrect house number to an output address.
    • HDS-8313 : Address Verification can parse building information in an address to a locality 3 field.
    • HDS-17437 : Address Verification adds a character space between house number digits when you select the Database preferred script option and omits the character space when you select the PostalAdmitAlt preferred script option.
    • HDS-8311 : If the house number and sub-building information in an address are correct but poorly formatted, Address Verification applies the correct format in the output address elements but not in delivery address lines or formatted address lines.
    • HDS-8310 : When an input address contains duplicate data, Address Verification fails to move the duplicate data to residue and retains the duplicate data in the address output.
    • HDS-7949 : Address Verification can add the value „番地 „as street information to an output address when „番地 “ appears in the input address as locality information.
    • HDS-7439 : Address Verification might fail to recognize a locality 3 value when the value is not followed by the suffix „JO „.
  • Czech Republic
    • HDS-21327: If an input address includes building and house number information in the same Delivery Address Line, Address Verification does not generate an output address data.
  • Columbia
    • HDS-23081 : Address Verification does not return a „V “ process status for an address without Province address element in the formatted address line.
  • Greece
    • HDS-16468 : Address Verification can add the tonos (‚`) character to an alphabetic character in an output address when you set the PreferredScript attribute to LATIN-1.
  • China
    • HDS-16876 : Address Verification can downgrade the Element Input Status value for a Locality 1 element when the input address does not contain Shi after the locality name.
    • HDS-21184 : Address Verification returns an element result status of 7 instead of E for a valid province when you enter the address in a Latin script.
    • HDS-23800 : Address Verification returns an „EGC7 “ geocoding status instead of EGCo for an address that does not have any geocoordinates.
    • HDS-17382 : Address Verification does not recognize the Pinyin street descriptor „lu“ as street information. Address Verification can write the house number to a sub-building field when the address contains the street descriptor.
    • HDS-2112 : Address Verification can add diacritics to addresses when you set the preferred language to English.
  • Kosovo
    • HDS-11991 : Address Verification fails to recognize „XK “ and „RKS “ as two-letter and three-letter country codes.
  • North Macedonia
    • HDS-12912 : Address Verification fails to recognize the country name „North Macedonia.“
  • Italy
    • HDS-10505 : When the reference data contains two equally valid candidates for an incorrect input address, Address Verification might return one of the candidates instead of returning an Ix score for the input address. The issue arises when the input address contains an incorrect street name but is otherwise valid.
    • HDS-22432 : Address Verification parses an invalid PO box information as building.
  • Vietnam
    • HDS-17590 : Address Verification does not recognize „Số“ as a house number identifier and can return an Ix score for an address that contains the identifier.
  • Ireland
    • HDS-11867 : The Address Verification engine might stop unexpectedly when you verify an address with the following characteristics:
      • The address includes the T/A or „Trading As“ abbreviation in a delivery address line field.
      • The address does not use street information.
      • The province information is incorrect.
    • HDS-11780 : Address Verification might fail to recognize a slash character as a separator in a building number range when you enter the building and street information in the Street 2 element.
  • Belgium
    • HDS-24726: Address Verification returns a different address from the input address.
  • Korea
    • HDS-14843: Address Verification can drop input detail from an address when you set the PreferredScript attribute to LATIN and you set the PreferredLanguage attribute to ENGLISH.
  • Spain
    • HDS-16607 : If an input address contains both ordinals and sub-unit descriptors, such as Planta and Piso (°), in a delivery address line, Address Verification can parse the delivery address line information to a street field and return an Ix status score.
    • HDS-24277 : Address Verification returns duplicate addresses from multiple input addresses in Interactive mode.
    • HDS-13358 : Address Verification can return an input address twice in a address suggestion list. Address Verification can also return an „Ix “ status score and not a „Cx “ score for the address.
    • HDS-17937 : Address Verification parses all street-level information from Delivery Address Line 1 to a Street field in the following scenario:
      • The street-level information comprises house number, street name, sub-building 1, and sub-building 2 data.
      • The street-level information does not contain any street, number, or sub-building descriptors.
    • HDS-13238 : Address Verification can return an „I2 „process status for an address that includes a valid post code and a „C4 “ process status for the same address without the post code. The issue arises when the match scores for the non-post code values exceed the score for the post code.
    • HDS-16606 : Address Verification returns incorrect suggestions for an input address in the following scenario:
      • The address contains an alphanumeric house number.
      • The address contains PRAL as a sub-building identifier on a delivery address line.
    • HDS-16871 : Address Verification does not recognize house numbers in the following scenario:
      • The house number contains alphanumeric characters.
      • The house number contains a dash symbol, for example, „11-D „.
    • HDS-22033: Address Verification can return two address suggestions that alternatively include and exclude house number data for a given input address.
    • HDS-21709 : Address Verification returns an „I3 “ process status for a valid address when the preposition „de“ is absent from a street name. The issue is observed when the street information appears in a delivery address line.
    • HDS-12438: Address Verification can return an Ix status code for a valid address. The issue arises when near-duplicate addresses exist in the reference data.
  • St. Kitts and Nevis
    • HDS-16150 : Address Verification can parse post code and locality values to incorrect fields.
  • Portugal
    • HDS-15158 : When an address contains LOTE as a house number descriptor, Address Verification fails to parse the house number information to a house number field and instead parses the information to a building field.
    • HDS-13972: Address Verification fails to recognize „N° “ as an abbreviation of Número and fails to recognize „DT “ as an abbreviation of Direto when DT does not follow a house number. Address Verification returns a low malleability score for an address that uses the abbreviations in such cases.
  • Mauritius
    • HDS-16147 : Address Verification can parse post code values to a building field.
  • Nigeria, Syria, Zambia
    • HDS-16209 : Address Verification can standardize the country names Nigeria Republic, Zambia Republic, and Syria Republic to Serbia.
  • South Korea
    • HDS-8785 : Address Verification can split input street information and parse part of the street information to a locality 2 field.
    • HDS-15838 : Address Verification can drop „HO “ and „DONG “ information from an address when you select a Latin preferred script.
  • Nicaragua
    • HDS-16146: Address Verification can drop post code information from the country-specific locality line field of an address.
  • Taiwan
    • HDS-12779 : Address Verification does not return street information in delivery address line fields if you use a non-default preferred script.
  • United Kingdom
    • HDS-14347 : Address Verification can copy an incorrect house number from input to output in fast completion mode when multiple correct alternatives exist in the database.
    • HDS-14268, HDS-13355 : Address Verification can fail to return the enrichment values for an input address when one or more conditions are true. The conditions include the appearance of a sub-building number and sub-building descriptor in reverse order, such „as14 FLAT „, and the presence of an extraneous house number on the apartment building.
    • HDS-22565: Address Verification returns incorrect building information from the input addresses.
    • HDS-13617, HDS-13286 : Address Verification can return the same Unique Property Reference Number for more than one address.
    • HDS-22565 : Address Verification returns incorrect building information from the input addresses.
    • HDS-13353 : Address Verification returns business terms such as BARBER in UPRN and UPPRN fields for a small number of addresses.
    • HDS-10832 : Address Verification can return a dash symbol indicating the East/West direction on the wrong side of the decimal point in a longitude coordinate. The issue is observed when the integer to the left of the decimal point is 0, for example, -0.57020.
    • HDS-8837, HDS-8836 : Address Verification can populate an address line exclusively with a house number, rather than include the house number and locality 2 information on the same line, in a rural address that does not use street information.
  • United States
    • HDS-8682 : When an input address adds house number information to the street field and adds multiple zeros to the house number field, Address Verification returns an „Ix “ score for the address in batch mode.
    • HDS-8295 : When the same address uses AVENUE as a street descriptor, Address Verification returns a „Cx “ score for the address.
    • HDS-7844 : Address Verification can fail to cleanse duplicate building or sub-building numbers from an address and retains the duplicate data in the output address.
    • HDS-10294 : When an input delivery address line contains building information only, Address Verification might duplicate the building information on the first and second delivery address lines or formatted address lines in the output.
    • HDS-9891 : When street data is concatenated to a sub-building descriptor in an input address, Address Verification can drop the sub-building information from the output address.
    • HDS-9559 : Address Verification can fail to correct a street address and instead return an Ix process score when the street information includes a directional abbreviation and a redundant character space.
    • HDS-23767 : Address Verification returns a different process status for the same ZIP Code input in Interactive mode.
    • HDS-24843 : Address Verification returns an I4 process status for an address that does not include organization and a V4 process status for the same address with organization in Certified mode.
    • HDS-21941 : Address Verification does not parse sub-building information correctly in the following scenario:
      • The sub-building information contains one or more digits followed by one or more alphabetic characters.
      • A character space separates the digits and the alphanumeric characters.
    • HDS-14035: Address Verification returns an Ix value in batch and certified modes for a valid address in the following scenario:
      • The address includes a post office box number, for example, PO LN.
    • HDS-15561 : Address Verification parses department information to a sub-building field in the following scenario:
      • The address contains street and house number information.
      • The verification engine runs in the Address Validator transformation in Informatica Data Quality.
      • You configure the Address Validator transformation to use the hybrid post mode.
    • HDS-16738 : Address Verification does not return multiple suggestions for an address in interactive mode in the following scenario:
      • The street name in the input address begins with a number.
    • HDS-16852 : Address Verification returns an Ix score for a valid address when the street name includes more than one street identifier.
    • HDS-19512 : Address Verification parses sub-building information as house number and street information in the following scenario:
      • The sub-building information comprises alphanumeric characters on Delivery Address Line 2.
      • A character space separates the alphanumeric characters and digits in the sub-building information.
    • HDS-20064: If a leading zero is absent from the ZIP Code in an input address, Address Verification can add the zero but match the address to an incorrect address in the reference data.
    • HDS-20996: Address Verification fails to recognize the word ONE as a house number in batch mode when the address contains a sub-building number but does not contain a sub-building descriptor.
    • HDS-9555: Address Verification might fail to correct a street address and instead return an Ix process score when the street name includes a digit, and the digit is duplicated at the end of the street name.
    • HDS-14142 : Address Verification fails to parse street and building information correctly in the following scenario:
      • Delivery Address Line 1 contains the street information.
      • Delivery Address Line 2 contains a mix of building and sub-building information.
      • Delivery Address Line 2 begins with a number.
    • HDS-12965 : Address Verification may fail to parse the first line of an address correctly in the following scenario:
      • The valid address does not contain a street name.
      • The first address line identifies an organization.
    • HDS-12737 : Address Verification can downgrade the match between an input address and a reference address when the input contains an incomplete street name that is a substantial subset of the full street name.
    • HDS-16947: If an input address contains additional values after the sub-building information on Delivery Address Line 1, Address Verification can remove the sub-building information and all subsequent values from the address line.
    • HDS-16862 : Address Verification fails to correct an address that contains two different streets on delivery address lines 1 and 2 and instead returns an Ix score for the address.
    • HDS-15776: Address Verification may return the wrong street name for a United States address when you include an extraneous street identifier in the input.
    • HDS-14575 : In certified mode, Address Verification can duplicate a sub-building number in the delivery address line output. The issue is observed when you set the StandardizeInvalidAddresses attribute to ON.
    • HDS-14563 : Address Verification drops sub-building 2 information from a United States address in the following scenario:
      • The address includes sub-building 1 and sub-building 2 information on the second address line.
      • The house number ends in an alphabetic character.
    • HDS-14561 : If you verify a United States address that contains valid sub-building 1 and sub-building 2 values, Address Verification might return the same sub-building descriptor for each value. The issue arises when both values are within the valid range for one of the sub-building descriptors.
    • HDS-12736 : Address Verification fails to match an input address with an address in the reference data when the input contains a redundant street descriptor in a delivery address line.
    • HDS-12530 : Address Verification can take longer than expected to return results when you set the Optimization Level to WIDE.
    • HDS-12462 : Address Verification can drop the sub-building information from an input address in the following scenario:
      • The sub-building identifier is concatenated with the sub-building value.
      • The sub-building information appears in a single delimited field in the input address.
    • TPR-14250: Correct the usage of profile attribute: preferredLanguages.
    • TPR-14146: The tool postEngineUnlockCode.sh now correctly validates unlock codes if it is given a configuration as parameter.
    • TPR-14031: INGORE (since 2025/06/19, 12.0)
    • TPR-13375: Improved error handling of wrongly configured mode attribute in postProfile element.
    • TPR-13352: Using the value „SPACE“ for the profile attribute outputFormatDelimiter is now supported for the V6 Engine.
    • TPR-13327: Calculation for minimal memory requirements for project attribute maxMemoryUsageMB.
    • TPR-12978: Misleading errors caused by the V6 engine not returning results were removed from the logfile. (since 2025/06/19, 12.0)
    • TPR-12790: Reconfigure service/project/runtime now work with auto maintenance
    • TPR-11804: Removed some non used legacy configuration files.
    • TPR-11476: classname-property of extension will not be deleted on save-operation
    • TPR-11353: Fixed in Post v12.0 – HDS-24063: Address Verification returns suggestions when you enter a PO Box number range but does not return suggestions when you enter a single PO Box number value.
    • TPR-11146: Licence files (*.lic) are now allowed to have empty strings and line breaks at the end of a line, though its not recommended.
    • TPR-10936: The return code rules for the landscape extension now include a new code for ambiuous addresses (27).
    • TPR-10857: Detection of encoding is now limited to a certain number of bytes to prevent out-of-memory-error
    • TPR-10797: Improved logging of database settings and metrics.
    • TPR-10631: It is now possible to configure a logging element, with just the filename in path. (since 2025/06/19, 12.0)
    • TPR-10475: Database consistency check will not remove the schema name from the tablename if included to execute the check. (since 2025/06/19, 12.0)
    • TPR-10416: SHUTDOWN DEFRAG for H2 databases is now executed after creating a full savepoint. NOTE: Due to a known issue in H2 implementation itself, theSHUTDOWN DEFRAG command does not work properly with encrypted databases (for H2 native encryption, it will still work with the new application side encryption). (since 2025/06/19, 12.0)
    • TPR-10388: Added additional states in which a project cannot be stopped to increase stability of a running project. (since 2025/06/19, 12.0)
    • TPR-10180: If a project is in state ERROR it now prevents the cluster synchronization. When the project state has been recovered, the synchronization will resume. (since 2025/06/19, 12.0)
    • TPR-10009: Improved handling of polish post addresses.

    Security

    • TPR-10826: Updated to version 1.12.0 of Apaches common-text library to address the security finding CVE-2022-42889.
    • TPR-10684: Updated postgres driver to version 42.7.7 to address security finding CVE-2022-21724.

    Manual

    • TPR-13776: Corrected configuration example for TOLERANT Post engines

    Known Bugs

    • Currently no known bugs.