We now support selection of multiple policies while creating a search. In the Search creation view in the list of available Inclusion, Exclusion or category policies we have check boxes against individiual items so that user can select multiple policies. Similarly while searching for "Custom" policies i.e. The policies which are not yet present in Compliance Accelerator/Discovery accelerator databases, user can now specify multiple policies by separating individual policies with commas.
Files updated File Version
=============
On the client:
Accelerator.Modules.SearchModule.dll 10.0.0.1161
Accelerator.Client.Common.dll 10.0.0.1161
AcceleratorInterfaces.dll 10.0.0.1161
AcceleratorMessages.dll 10.0.0.1161
On the server:
AcceleratorSearch.dll 10.0.0.1161
AcceleratorInterfaces.dll 10.0.0.1161
AcceleratorWebBO.dll 10.0.0.1161
AcceleratorMessages.dll 10.0.0.1161
Search Criteria Drilldown.rdl (only for Discovery Accelerator)
Installation instructions
=========================
Following instructions need to be carried out on a Compliance Accelerator or Discovery Accelerator server:
-Stop the Enterprise Vault Accelerator Manager Service.
-Once the Enterprise Vault Accelerator Manager Service has stopped, take a backup copy of the files listed in the "Files updated" section pertaining to the server, locatable in the Compliance Accelerator or Discovery Accelerator installation folder (which is by default "C:\Program Files (x86)\Enterprise Vault Business Accelerator").
-Additionally for a Discovery Accelerator installation, take a backup copy of the file "Search Criteria Drilldown.rdl", locatable in the Discovery Reports folder (which is by default "C:\Program Files (x86)\Enterprise Vault Business Accelerator\Discovery Reports").
-Copy the updated files "AcceleratorSearch.dll", "AcceleratorInterfaces.dll", "AcceleratorWebBO.dll", "AcceleratorMessages.dll", packaged in this hotfix, to the Compliance Accelerator or Discovery Accelerator installation folder, replacing the original.
-For Discovery Accelertor copy the updated "Search Criteria Drilldown.rdl" replacing the original.
-Run the sql file "UpdateReportSP.sql" against the Discovery Accelerator customer database. *Do not perform this step for a Compliance Accelerator implementation.*
-Start the Enterprise Vault Accelerator Manager Service.
Following instructions need to be carried out for Discovery Accelerator only:
-Launch the EVBAAdmin website, click on "Reporting Server" button in bottom right corner of the page.
-Upload the updated reports template by specifying reporting server URL,username and password.
-------------------------------------------------------------------------------------------
Following instructions need to be carried out on Compliance Accelerator or Discovery Accelerator Client:
-Close the Compliance Accelerator or Discovery Accelerator Client application
-Once the Compliance Accelerator or Discovery Accelerator Client application has closed, take a backup copy of the files listed in the "Files updated" section pertaining to the client, locatable in the Compliance Accelerator or Discovery Accelerator Client installation folder, (which is by default "C:\Documents and Settings\<User>\Local Settings\Application Data\Enterprise Vault Compliance Accelerator\Client\" OR "C:\Documents and Settings\<User>\Local Settings\Application Data\Enterprise Vault Discovery Accelerator\Client\")
-Copy the updated files "Accelerator.Modules.SearchModule.dll", "Accelerator.Client.Common.dll", "AcceleratorInterfaces.dll", "AcceleratorMessages.dll", packaged in this hotfix, to the Compliance Accelerator or Discovery Accelerator Client installation folder, replacing the original.
-Start the Compliance Accelerator or Discovery Accelerator Client application.
Uninstallation instructions
=========================
Following instructions need to be carried out on Compliance Accelerator or Discovery Accelerator server to unistall this hotfix:
-Stop the Enterprise Vault Accelerator Manager Service.
-Once the Enterprise Vault Accelerator Manager Service has stopped, take the backed up copy of the files listed in the "Files updated" section pertaining to the server and replace the hotfixed files, locatable in the Compliance Accelerator or Discovery Accelerator installation folder (which is by default "C:\Program Files (x86)\Enterprise Vault Business Accelerator").
-Additionally for a Discovery Accelerator installation, take the backed up copy of the file "Search Criteria Drilldown.rdl", and replace the hotfixed file, locatable in the Discovery Reports folder (which is by default "C:\Program Files (x86)\Enterprise Vault Business Accelerator\Discovery Reports").
-Run the sql file "RevertReportSP.sql" against the Discovery Accelerator customer database. *Do not perform this step for a Compliance Accelerator implementation.*
-Start the Enterprise Vault Accelerator Manager Service.
Following instructions need to be carried out for Discovery Accelerator only:
-Launch the EVBAAdmin website, click on "Reporting Server" button in bottom right corner of the page.
-Upload the updated reports template by specifying reporting server URL,username and password.
-------------------------------------------------------------------------------------------
Following instructions need to be carried out on Discovery/Compliance Accelerator Client:
-Close the Compliance Accelerator or Discovery Accelerator Client application
-Once the Compliance Accelerator or Discovery Accelerator Client application has closed, take the backed up copy of the files listed in the "Files updated" section pertaining to the client and replace the hotfixed files, locatable in the Compliance Accelerator or Discovery Accelerator Client installation folder (which is by default "C:\Documents and Settings\<User>\Local Settings\Application Data\Enterprise Vault Compliance Accelerator\Client\" OR "C:\Documents and Settings\<User>\Local Settings\Application Data\Enterprise Vault Discovery Accelerator\Client\").
-Start the Compliance Accelerator or Discovery Accelerator Client application.
Note:
The hint that appears for custom policy textbox, will not be localised in the hotfix, it will get localized in next service pack.