Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

Corridor 3.1.0 Service Pack 8

  1. Last updated
  2. Save as PDF

 

Version(s) patched:

3.1.0

Date Released:

08/19/2024

 

Enhancements/Improvements

 

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

 

Enhancement: Now Corridor has a Manage Logging page where admins can configure the log level and granularity. For more information, see Corridor Logging Management.

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

 

Enhancement: Stronger password controls.

Description: Now Corridor requires stronger passwords. Password policies can be configured by admins and Corridor prompts users to create strong passwords when logging in for the first time to Corridor v.3.1.8. For more information, see Password Policy Settings.

Tracking code: STE-28440, STE-28428, STE-28416, STE-28861 

 

Enhancement: Task and Activity codes in Corridor were not consistently listed in the dropdown list.

Description: A recent change syncs Task and Activity codes from Suite to Corridor, but because not all users sync data between Suite and Corridor, the dropdown list in Corridor didn't update accordingly. To avoid this situation, now users can enter Task, Expense, Activity, and Tax Type codes manually to populate the dropdown lists. These codes are only valid for Corridor and will not sync to Suite.

Tracking code: STE-28798

 

Issue: Now the Help button contains the link to the Corridor user guide in Mitratech Customer Success Center.

Tracking code:  STE-29582

 

Bug Fixes

 

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


 

Issue: Invoices sent from eBilling Hub to Corridor would stay in the Received status if errors were encountered during processing.

Tracking code:  STE-28793

 

Issue: Discounts applied to manual invoices with taxes didn’t affect tax rate calculations

Description: When a user added a non-US invoice (a manual invoice with taxes) in Corridor, a discount was added to a line item, and charges were calculated per unit, the added discount wasn’t used in the tax calculation.

Tracking code: STE-29042

 

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

Tracking code: STE-28854

 

Issue: Corridor messages couldn't 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: Manual invoices set as non-USD and without taxes specified failed to import to Corridor.

Tracking code: STE-29454

 

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

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

Tracking code: STE-29067


 

Dependencies:

  • corridor3.1.7.3


 

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.8.0.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 the Corridor application 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.8.0-Scripts-SQL.zip

  1. Extract and run the SQL script.

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Classifications
    This page has no classifications.
  2. Tags
    This page has no tags.