Build Number
Official build number: 2.11.914
Release Date
May 17th, 2022
License Compatibility
If you are upgrading from a previous ViaWorks/Locator 2.x release, your 2.x license will continue to work. If you are installing Locator 2.11 SR9 for the first time, or if you are upgrading from ViaWorks 1.5.x, you will be required to obtain a new license key from Ayfie. Contact your Ayfie sales representative to obtain your license key.
New Installations
Download the Locator Installation package, and run Locator_2.11.914.exe.
For hardware and software requirements (including AV configuration information), and for help on how to install Locator, please see the Locator Installation Guide.
Upgrading from a Prior Installation
It’s recommended to upgrade to this service release, if running earlier version.
If you are upgrading from a version earlier than Locator 2.11 SR8, see also Locator 2.11 SR8 (2.11.903).
You can upgrade to this release from a previous ViaWorks/Locator 2.x release.
You CANNOT upgrade to this release from ViaWorks 1.x or earlier.
If upgrading from a previous major version, it's recommended that you upgrade all installed connectors. If upgrading from 2.7 or below it's required that you upgrade all connectors.
Supervisor versions 2.1 and older do not support Locator 2.11 SR9. Customers should not upgrade to Locator 2.11 SR9 until they've upgraded to Supervisor 2.3.
As Supervisor version 2.3 requires the new Authority Service, that comes with Locator 2.11 SR1 and above, users upgrading to Supervisor 2.3 should first upgrade to Locator 2.11 SR9.
Note: When you upgrade to Locator 2.11 SR9 you need to configure the Active Directory authentication system, as this is a requirement for Supervisor 2.3.
Notes if upgrading from ViaWorks 2.7 or Older:
The PostgreSQL database format will be upgraded. It is strongly recommended to create a backup of the database prior to running the 2.11 upgrade. Once the database has been upgraded, it is not possible to revert back to a previous version
The index will be rebuilt after the upgrade has finished. The index rebuild can potentially take a while, and users may not be able to search or have incomplete search results until the rebuild completes. Documents will not be re-fetched during this process
All customers will be moved from the "ViaWorksV2" Solr core to the “ViaWorksCloud” Solr collection during the upgrade process. The “ViaWorksV2” core from versions 2.7 SR5 and older is no longer supported
During the upgrade, the solrconfig_overrides.xml and schema_overrides.xml files will be reset. Before upgrading, make note of the customization added to these files so they can be re-applied after the upgrade is complete. Note: the Solr schema has changed and overrides will need to be updated to support the changes.
Locator 2.11 SR9 will install .NET Framework version 4.7.2.
New Features & Improvements
Locator 2.11 SR9 is a new service release containing the following new features and improvements:
Component | Description |
|---|---|
Documentation | Updated Document Handler documentation on how to prevent opening confirmation pop-up on every document. |
SQL Server | Performance tuning of database triggers. |
Bug Fixes
Locator 2.11 SR9 is a new service release containing the following bug fixes:
Component | Description |
|---|---|
Data Access Layer | Document workflow related operations are now transactional. |
Document Handler | Removed ping to server in FileServer Document Handler Plugin. |
Documentation | Security article created. |
Index Builder | Microsoft SQL Server queries now take DateTime2 type values as query parameters instead of DateTime. |
Platform SDK | Added externalID field to document. Connectors can assign value to externalID that’ll be used when updating documents. Documents and embedded documents with ExternalID are updated without deleting them. |
Search Scopes | The Locator backend now handles excluded values in search scopes. A fix to add excluded values to search scopes from the Locator UI will not be done in 2.x and only be fixed in latest major release. |
Solr | Fixed an issue with Solr not logging UTF-8 encoded characters to log file. |