Version Patched:

3.1.0

 

Date Released:

3/22/2024

 

Enhancements/Improvements

 

This release notes details the information related to enhancements, improvements, and resolved issues in Corridor.3.1.7.2.

 

Enhancement: Now Corridor has a Logging Management page where admins can see and configure logs. Before, only users with access to the Corridor server console could see and configure logs. 

Tracking code: STE-28732, STE-28733, STE-28735

 

Issues Resolution

 

This release notes details the information related to enhancements, improvements, and resolved issues in Corridor.3.1.7.2.

 

Issue: Home > View Timekeepers couldn’t list timekeepers if a record with an incorrect date format existed in the table.

Tracking code: STE-28854

 

Issue: Corridor messages cannot be dismissed.

Description: When a user tried to delete a message from clients to corridor firms, Corridor showed a blank screen. If the user clicked the Back button to return to the webpage, the message was still visible.

Tracking code: STE-28863

 

​​Issue: Users couldn’t create new line items in manual invoices.

Tracking code: STE-29307

 

Issue: Vendors submitted timekeepers through Corridor but emails were sent to a different firm.

Description: Clients received timekeeper notifications in the Lobby, but the data was incorrect due to the firm submitting the timekeeper data to a different firm.

Tracking code: STE-29067

 

Issue: Manual invoices set as NON-USD and without taxes specified failed to import to Corridor.

Tracking code: STE-29454

 

Dependencies:

• corridor3.1.7.1

 

Install Instructions

 

1. Stop the Corridor application on the Java application server. 

2. Back up the Corridor Web application in the WebApps folder on the Java application server. Delete the contents of the Corridor folder in WebApps after making the backup. 

3. Rename the Corridor.3.1.7.2.war file to the deployed filename in the WebApps folder. Copy the newly named war file to the WebApps folder and overwrite the current file contents. 

4. Unzip the new war file into the Corridor folder in WebApps. 

5. From the backup of the previous deployment, copy the \WEB-INF\Utilities.properties file to the same location in the newly exploded war file on the Java application server. 

6. Restart Corridor on the Java application server. 

7. Log in to Corridor as an Admin user and verify the settings.

 

Database Script Instructions

 

1. Use your preferred database tool, for example, SQL Server Management Studio, to back up your Corridor database.

2. Log in to your query tool as an administrative user.

3. Open the appropriate script for your database. It is contained in a ZIP file.

◦ ​​Corridor3.1.7.2-Scripts-SQL.zip

4. Extract and run the SQL script.