Suite 8.11.0 SP19

Dependencies

1. This service pack requires the previous service pack installed:
   • Suite.8.11.18.3 (Service Pack)
2. This service pack updates the following applications:
   • Suite (suite.8.11.19.0)
   • Boxir4 (boxir4-Suite.8.11.19.0)
   • Suite Manager (Suite Manager.exe)
3. Run one of the following scripts, depending on your database.
   • Suite.8.11.0.19.0-Scripts-Oracle
   • Suite.8.11.0.19.0-Scripts-SQL

Downloads

Click on the link below to download a compressed file that can be used to access the necessary installation files.

• suite.8.11.19.0 (Service Pack 19)
• Boxir4 (boxir4-Suite.8.11.19.0)
• Suite Manager (Suite Manager.exe)
• Database scripts (Oracle and SQL Server)

The following rules can be imported to address issue resolutions:

• IManageIntegration
• Matter_PurgeMatters

Suite Installation

For more information on the Suite auto-installer, please refer to Using Suite Autoinstaller. 

You must follow these steps to install this product Suite.8.11.19.0 manually:

1. Stop the  Bridgeway Suite application on the Java application server. 
2. Back up the Suite Web application in the WebApps folder on the Java application server. Delete the contents of the Suite folder in WebApps after making the backup.
3. Rename the suite.8.11.19.0.war file to the deployed filename in the WebApps folder.
4. Copy the newly named war file to the WebApps folder and overwrite the current file contents.
5. Unzip the new war file into the Bridgeway Suite folder in WebApps.
6. Copy the following files from the backed up WAR file:
   • WEB-INF\classes\com\bsi\attributes\darwin.properties
   • WEB-INF\classes\com\bsi\attributes\dbs.enc
   • client.htm
7. Delete all files in the following folders on the server:
   • \work 
   • \conf\catalina
   • \temp
   • \bin\WEB-INF
8. Restart the Bridgeway Suite application on the Java application server.

Database Script Instructions

1. Use your preferred database tool (SQL Server Management Studio, Oracle RMAN utility, Oracle export data pump utility, etc.) to make a backup of your Suite database.
2. Log in to your query tool as an administrative user.
3. Open the appropriate scripts .ZIP file for your database:
   • Suite.8.11.0.19.0-Scripts-Oracle.sql for Oracle databases
   • Suite.8.11.0.19.0-Scripts-SQL.sql for SQL databases
4. Open and run the SQL script.

Suite Manager Installation

You  must follow these steps to install the Suite.Manager:

1. Uninstall the current instance of Suite Manager.
2. Extract the files from the Suite Manager.zip file.
3. Start the installation program for Suite Manager located in the directory in which the Suite Manager.EXE file was extracted.
4. Click Next on the Welcome screen.
5. On the License Key screen, type the license key in the text box and click Next.
6. On the Choose Destination Location screen, confirm that the Destination Folder is the desired directory location for the program files.
7. On the Start Installation screen, click Next to begin the installation process.
8. A progress screen will display. You can abort the installation at any time by clicking Cancel.
9. On the Installation Complete screen, click Finish.

Certifications

Suite.8.11.19.0 has been certified with Tomcat 9.0.118 and Windows Server 2025
Tracking Code: STE-32103

Enhancements/Improvements

Bug Fixes

Suite Manager

Issue: Multiple Fields Appear in Suite Manager but Do Not Exist in eCounsel Invoice Base Info.
Description: We fixed an issue where several fields appeared as configurable under Modules/Tabs for the eCounsel > Invoice > Base Info in Suite Manager, even though they do not exist in the actual eCounsel application. These fields included:

• Matter Name
• Tax Point Date
• Tax Invoice Note
• Tax Credit Note
• Invoice Reference
• Rejection Comments to Vendor
• Hide Audit Warnings
• Internal Rejection Comments
• Pending Approver (Days)

Tracking code: STE-29175,STE-31462

eCounsel

Issue:  We fixed an issue where invoices were still being accepted for matters that had already been closed, ignoring settings in Suite Manager.
Tracking code: STE-31964

Issue: Fixed logging for the AP Integration task to provide clear and specific error messages when an incorrect Invoice_ID is entered in the AP task import file.
Tracking code: STE-31275

Issue: We fixed a security vulnerability where password hashes were being returned in application responses from eCounsel and Suite Manager.
Tracking code: STE-31156, STE-31563

Issue: Resolved recurring issues in eCounsel where the “OOC Office” field displayed countries instead of offices and required field validations failed.
Tracking code: STE-30722

Issue: Timekeepers Sync Issue
Description: Resolved a problem where Timekeeper synchronization from Suite to Corridor failed to reflect rejection status accurately. When a timekeeper was rejected in Suite due to an incorrect CSV file, the corresponding record in Corridor did not update to “rejected,” resulting in mismatched statuses between the two systems. Updated synchronization logic now correctly captures and propagates rejection outcomes to maintain consistent timekeeper records.
Tracking code: STE-31606

Issue: Resolved an issue where the eCounsel–iManage integration intermittently failed to create workspaces due to a parsing error in the Lookup Tables.txt file. Updated logic now handles type mismatches and validates incomplete sections, ensuring reliable workspace creation for new matters.

Additionally, fixed a defect where the iManage task failed to append new Matters to the existing export file. Instead of updating the consolidated file, the task created a new file for each Matter, overwriting previous data.
Tracking code: STE-31691, STE-31830

Issue: Resolved an issue where invalid Legalhold integration credentials caused eCounsel Matters to load indefinitely and eventually display a blank screen after multiple access attempts. The system now properly handles credential validation errors and provides clear user feedback instead of blocking the interface. An indicator has been added to show connection status with Legalhold, and Matter creation options are disabled when disconnected.
Tracking code: STE-31694

Issue: Fixed an intermittent issue in the Timekeeper File Import Wizard where uploading a new rate for an existing timekeeper did not end-date the previous employment record. Updated processing to ensure the prior rate is always end-dated to the day before the new start date, enforcing a single active rate at any time.
Tracking code: STE-31917

Issue: Fixed a critical incompatibility with JDK 21 that prevented users from accessing records in the People and Entities modules.
Tracking code: STE-31993

Issue: Fixed an issue where Matter filtering failed when both the Corporate Unit and Primary Legal Contact filters were applied simultaneously.
Tracking code: STE-31916

Secretariat

Issue: Fixed an issue where entities with names containing spaces were incorrectly flagged as having pending changes, even when no edits were made. This false change detection blocked the normal approval workflow. The fix ensures names are handled consistently so approval flows proceed correctly when no actual modifications exist.
Tracking code: STE-31865

Issue: We fixed an issue where the Secretariat application that was sending email links failed with the error: "AlertForwarder() error - You must pass in an alert_id to use this object." The system now correctly handles XML deserialization and generates valid approval links, provided the Email Base URL is configured in Suite Manager. This ensures email notifications work as expected and improves the approval workflow.
Tracking code: STE-31765