Skip to main content
Mitratech Success Center

Suite 8.11.0 SP13

Summary

Date Released

09/11/2020

End of Support Schedule for Integrations

The following products will no longer be supported as of January 31, 2021:

  • SiteMinder authentication (contact Support for more information on SAML authentication)
  • Bridgeway Link (contact Support for more information on Mitratech Office Link)
  • Bridgeway Calendar Link (contact Support for more information on Mitratech Office Link)
  • Bridgeway E-mail Link (contact Support for more information on Mitratech Office Link)

Enhancements

Suite

  • eCounsel and Secretariat are now certified on Oracle 19c databases.
  • For eCounsel and Secretariat, user fields can now be added to grids on all applicable pages and tabs that allow user fields to be added to those pages or tabs. These user fields are sortable and searchable in each grid on which they are added.
    Tracking code: STE-20828

Note: The following do not allow user fields to be added to the grid:

  • eCounsel - Calendar Module
  • eCounsel - Matters Module - Physical File Action Tab
  • eCounsel - Matters Module - Documents Tab - Document File Subtab
  • eCounsel - Matters Module - Costs Tab (including the Cost Detail Subtab)
  • eCounsel - Matters Module - Calendar Tab
  • eCounsel - Invoices Module - Documents Tab - Document File Subtab
  • eCounsel - Entities Module - Documents Tab - Document File Subtab
  • eCounsel - Entities Module - Related Matters tab
  • eCounsel - People Module - Employment Tab
  • eCounsel - People Module - Documents Tab - Document File Subtab
  • eCounsel - People Module - Related Matters Tab
  • Secretariat - Calendar Module
  • Secretariat - Entities Module - Names Tab - Former Names Subtab
  • Secretariat - Entities Module - Names Tab - DBA Names Subtab
  • Secretariat - Entities Module - Names Tab - Alternate Names Subtab
  • Secretariat - Entities Module - Notes/History/Charts Tab - Notes/History File Subtab
  • Secretariat - Entities Module - Securities Tab - Equity - History Tab
  • Secretariat - Entities Module - Calendar Tab
  • Secretariat - People Module - Notes/History/Charts Tab - Notes/History File Subtab

Known Issues: The following are known issues with adding user fields to grids:

  • When sorting by a user field on the Players tab in the Matters module, the grid returns no results. This issue will be resolved in a future release.
    Tracking code: STE-22158
  • When selecting the Invoices Awaiting My Approval filter on the Invoices List page, user fields do not display due to the way the filter works.
    Tracking code: STE-22090
  • If you sort on a user field, then search for data for a different user field, the results will be sorted by the user field that is part of the search criteria because multiple sorting on user fields is not supported.
    Tracking code: STE-22128
  • If you sort on a user field on the Progress Notes tab in the Matters module, the comments will no longer appear on the grid (either expanded or collapsed). To workaround this issue, remove any sorting on user fields if you want to view the comments in the grid list.
    Tracking code: STE-22139
  • For logical user fields that do not have a value (for example, the user field was created after a record has already been entered), these appear with a value of "False" in the grid list. When sorting by the logical user field, the value is actually "NULL" so the record will appear to sort in the wrong order. Workaround is to open the record and re-save after checking or unchecking the checkbox.
    Tracking code: STE-22140
  • When combining sorting of the standard fields with user fields that are date/time data type, the date/time user field must be in the first sort position or the grid list will not display results. 
    Tracking code: STE-22145
  • In the Invoices module, on the Invoice Approval subtab of the Matter tab, selecting export with user fields on the grid list and sorted by a user field returns an error in Microsoft Excel. To workaround this issue, remove the sort on the user field and export the results.
    Tracking code: STE-22153
  • When adding user fields to the Calendar module or Calendar tab, searching or sorting on user fields returns results that do not meet the criteria specified.
    Tracking code: STE-22152, STE-22266
  • When searching by user fields on the Accruals tab in the Matters modules, the values for the Vendor field do not appear on the grid.
    Tracking code: STE-22156
  • On the Matters List page, searching by a user field and then sorting by Logical Group does not return results. Do not sort by a Logical Field if you need to search criteria to include a user field.
    Tracking code: STE-22228

Quick Reference to Enable this Feature: This feature is enabled by default. See Working with Grids for more information.

  • For user-defined tabs that are multi-record, the records are automatically sorted by the first column on the grid list.
    Tracking code: STE-20561

Quick Reference to Enable this Feature: This feature is enabled by default.

eCounsel

  • Scripts have been created for the new feature to allow vendors/law firms to submit timekeepers via the Corridor Website. These scripts query the eCounsel matter management system for all approved timekeepers that are active for each vendor/law firm, then transforms the data to be uploaded via database scripts to Corridor with a status of "Approved".
    Tracking code: STE-21196

Quick Reference to Enable this Feature: 

  1. Download the script package for your database server from Downloads.
  2. For Microsoft SQL Server, follow the instructions in Database Script Instructions; for Oracle, follow the instructions in Database Script Instructions.
  3. Send the results of the database script, along with your Client Identifier for Corridor to eCounselSupport@mitratech.com.
  • The current New Matter Alert rule, which notifies users when they are added as players to a matter, has been replaced by two alerts:
    • New Player Alert - Notifies users when they have been added as a new player on a matter in eCounsel.
    • New Matter Alert - Notifies users when a new matter has been added to eCounsel (the user does not have to be a player on the matter).

Tracking code: STE-18899

Quick Reference to Enable this Feature: See Rule Installation Instructions for detailed steps.

  1. If the New Matter Alert rule is installed, use Suite Manager to remove the current alert. The version of the rule should indicate Version 1.0 or 1.1.
  2. Import the New Matter Alert rule using Suite Manager Rules Engine. The version of the rule should indicate Version 1.2.
  3. Import the New Player Alert rules using Suite Manager Rules Engine. The version of the rule should indicate Version 1.2.
  • A new version of the Timekeeper Employment Validation Smart Invoice rule has been created for Oracle databases to remove the case sensitive restriction when using an Oracle database since Oracle is case sensitive by default.
    Tracking code: STE-21384

Quick Reference to Enable this Feature: See Rule Installation Instructions for detailed steps.

  1. If the Timekeeper Employment Validation rule is installed and you want to use the new Oracle database specific rule instead, use Suite Manager to remove the current alert. 
  2. Import the TimekeeperEmploymentValidationORA.bsi file using Suite Manager Rules Engine. Select the unlimited encryption rule if your site has implemented Java Cryptography Extension (JCE) Unlimited.
  • A new rule, Line Item Date Past Matter Close, allows clients to place an invoice on hold instead of rejecting it if it exceeds the Matter Close Date. This rule places imported invoices "On Hold" and sends an email notification when an invoice line item date is more than a specified number of days after the Close Date. 
    Tracking code: STE-21966

Quick Reference to Enable this Feature: See Rule Installation Instructions for detailed steps. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.

  • Two new rules, Maximum Expense Values and Maximum Expense Values with Configuration File, allow clients to validate maximum rates, maximum expense rates, expense codes per units, and maximum expense amounts. The Maximum Expense Values rule replaces the Max Rate, Maximum Expense Rate, Expense Rate, Expense Code per Unit, and Maximum Expense Amount rules. To install the rule, you must first install the ruleinstallerhelper rule prior to its installation. The fule uses the following parameters to validate a single code:
    • Expense Code – The expense code that the rule should validate, similar to the current rules (required parameter)
    • Expense Rate – The maximum allowable rate for the given expense code (optional parameter)
    • Expense Hours or Units – The maximum allowable hours or units for the given expense code (optional parameter)
    • Expense Amount – The maximum allowable line item amount (in billed currency) for the given expense code (optional parameter)

The second rule, Maximum Expense Values with Configuration File, allows a client to validate multiple codes and values without having to install the Max Expense Values rule multiple times. Note that this rule can be set to either Warning or Rejection, so your site can install twice, once for codes that cause a warning, and once for codes that cause the invoice to be rejected. 
Tracking code: STE-22009, STE-22014

Quick Reference to Enable this Feature: See Rule Installation Instructions for detailed steps. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.

  • A new rule, Require Corridor Attachments Task, has been created to validate that invoices imported from the Corridor Website contain an attachment (not the LEDES file itself but additional supporting document attachments). This rule will not trigger for Collaborati or manually entered invoices in eCounsel.
    Tracking code: STE-22034

Quick Reference to Enable this Feature: See Rule Installation Instructions for detailed steps. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.

Office Link

  • Office Link addins now support TLS (Transport Layer Security) 1.2.
    Tracking code: STE-21777

Quick Reference to Enable this Feature: This feature is enabled by default.

  • Office Link Version 3.1.0 has been released with updates to version numbers and the downloaded installers via eCounsel and Secretariat.
    Tracking code: STE-20672

Quick Reference to Enable this Feature: You must uninstall the previous add-ins and install the new versions of the add-ins. See Upgrading and Reinstalling Add-ins and Installing the Add-ins for more information.

  • The Office Link installers now use a certificate to validate the installer so that antivirus software will not flag as a risk.
    Tracking code: STE-19074

Quick Reference to Enable this Feature: This feature is enabled by default. See Installing the Add-ins for more information on installation.

  • A new setting, "Keep plug-in enabled after restarts", has been added to the Office Link Outlook add-in to mitigate the possibility of the add-in being disabled.
    Tracking code: STE-19075

Quick Reference to Enable this Feature: See Configuring Settings for more information on enabling this feature.

  • When authenticating the login in Office Link, the default 30-day window for a user's session to remain active has now been enhanced to be a rolling window, meaning that the user's session will remain active until 30 days after the last use of Office Link. If your company has set the OfficeLinkTokenExpiration property (acceptable values in seconds) in the darwin.properties file to timeout the session sooner than 30 days, the value for the property will be used in the rolling window (for example, if OfficeLinkTokenExpiration = 864,000, the rolling window will be 10 days instead of 30 days). 
    Tracking code: STE-19072

Quick Reference to Enable this Feature: See "Appendix A: Setting Properties" in the Suite 8.11.0 Installation Guide for more information.

  • When dragging-and-dropping files from Microsoft Outlook into the Office Link Outlook addin, or dragging-and-dropping files from Windows Explorer or the Desktop into the Office addin, these files will be uploaded in the background so that you can continue to use the Microsoft Office product during the upload.
    Tracking code: STE-19073

Quick Reference to Enable this Feature: See Saving and Copying Documents for more information on saving a document.

  • For each installation of the Office Link add-ins on a user's computer, a daily log will be saved to the user's folders with the current date (typically, C:\Users\[username]\OfficeLinkLogs). These logs will be deleted after 60 days, as new logs are created.
    Tracking code: STE-20516

Quick Reference to Enable this Feature: See "How Can I Access Logs?" in Troubleshooting for more information.

  • When saving a document to any Microsoft Office product such as Microsoft Word or Excel, you can now search for matters or entities to which to save the document. The matter or entity will be added as the first entry in the Most Recently Accessed list of matters or entities. 
    Tracking code: STE-20421

Quick Reference to Enable this Feature: See Saving and Copying Documents for more information on saving a document.

  • When searching for a matter, the matter name and number are both returned in the results as "Matter Name - Matter Number".
    Tracking code: STE-15073

Quick Reference to Enable this Feature: See Searching Matters and Entities for more information on searching for matters.

  • Adding, deleting, and/or updating appointments have been refactored for performance.
    Tracking code: STE-19076

​​​​​​Quick Reference to Enable this Feature: See Appointments for more information on creating, deleting, or modifying appointments.

  • Deleting an appointment in Microsoft Outlook that is sychronized with eCounsel or Secretariat now removes the invitee from the appointment in the Calendar module of eCounsel or Secretariat. If the person is re-invited in eCounsel or Secretariat, a new appointment will be synchronized with his/her Microsoft Outlook.
    Tracking code: STE-20501

Quick Reference to Enable this Feature: See Appointments for more information on creating, deleting, or modifying appointments.

  • Because you must have the Outlook add-in enabled to use the Office add-in since these two add-ins share document features, the checkbox to enable the Office add-in has been moved to be to the Enable Add-in for Outlook section on the Office Link Settings in the Suite Manager System Settings component.
    Tracking code: STE-14104

Quick Reference to Enable this Feature: See Configure Suite Manager for more information on configuration settings for Office Link.

  • When installing the add-ins for Office Link, the URLs needed during the installation process are now available on the Office Link tab of the Tools | Preferences page.
    Tracking code: STE-20380

Quick Reference to Enable this Feature: See Installing the Add-ins for more information.

  • Error handling for the Office Link add-ins has been improved for address not found, bad requests, and methods not supported.
    Tracking code: STE-21174

Quick Reference to Enable this Feature: See Troubleshooting for more information.

  • When installing the add-ins for Office Link, the URLs needed during the installation process can now be made available on the Office Link tab of the Tools | Preferences page. Clicking on the URL allows a user to copy the link and paste directly into the installer for the Outlook and Office add-ins.
    Tracking code: STE-14100

Quick Reference to Enable this Feature: A system administrator must first enable the new Show Office Link URL checkbox in Office Link Settings on the Mitratech Suite tab of System Settings component in Suite Manager (see Configuring Suite Manager). Once this checkbox is enabled, users can access by clicking Tools in eCounsel or Secretariat, selecting Preferences, and selecting the Office Link tab. Clicking on the URL link copies the link to the Clipboard where it can be pasted into the Outlook or Office add-in installer. See Installing the Add-ins for more information.

  • Deleting an appointment in Microsoft Outlook that is synchronized with eCounsel or Secretariat now removes the invitee from the appointment in the Calendar module of eCounsel or Secretariat. If the person is re-invited in eCounsel or Secretariat, a new appointment will be synchronized with his/her Microsoft Outlook.
    Tracking code: STE-15022

Quick Reference to Enable this Feature: This feature is enabled by default. See Deleting Appointments for more information.

  • Invoices can now be searched by matter number or identifier within the Microsoft Outlook addin.
    Tracking code: STE-21527

Quick Reference to Enable this Feature: This feature is enabled by default. See Searching Invoices for more information.

  • For Office Link installers, access to the online user guide on the Mitratech Customer Success Center is now provided. In addition, if you have configured the Office Link installers to be available for eCounsel and/or Secretariat users, the Office Link tab under Tools > Preferences now opens the Mitratech Office Link Installation Guide in the Mitratech Customer Success Center.
    Tracking code: STE-21858

Quick Reference to Enable this Feature: See Making the Installer Accessible for more information on configuring the installers to appear in eCounsel and/or Secretariat.

  • For Office Link, a setting can be selected in the Office Link Settings under System Settings in Suite Manager so that all events (appointments and tasks) for a user will appear on the user's default calendar. Enabling this checkbox replaces the need for a Mitratech Calendar and makes scheduling events in Outlook for eCounsel or Secretariat easier because all eCounsel or Secretariat events appear on each user's calendar for scheduling purposes.
    Tracking code: STE-21903

​​​​​​​​​​​​​​​​​​​​​Quick Reference to Enable this Feature: See Administering Mitratech Office Link for more information on setting this global parameter for Office Link.

Issue Resolutions

In addition to security updates, this service pack includes the following issue resolutions.

Update Manager

  • A new version of Update Manager, Version 1.0.10, is now available to resolve an issue with files not being removed during uninstall due to case differences in the file specified and the actual file (for example, viewprofilesummaryTools.xsl as opposed to viewprofilesummarytools.xsl).
    Tracking code: STE-21891

Suite

  • Modifications to the deployment files to upgrade libraries.
    Tracking code: STE-19571, STE-19577
  • When uploading documents on a deployment that is set to file server storage, a new setting in Suite Manager controls whether the application searches the file server storage location for subfolders. If the Ignore Subfolders checkbox is enabled, performance will be improved in environments with a large number (10s of 1000s) of documents at the root level of the file server storage location.
    Tracking code: STE-20575
  • For an integration using SAML authentication, users who are locked out or inactive in eCounsel will not be allowed to login using SAML.
    Tracking code: STE-21055
  • In Advanced Search, the list of lookup values for user fields now displays when creating criteria.
    Tracking code: STE-21169
  • The report re-import for Business Objects no longer intermittently fails on eCounsel or Secretariat.
    Tracking code: STE-21281
  • For parent/child relationship lookups (such as the Law Area and Law Subarea on the matters Base Info tab), selecting a parent without selecting a child no longer results in having to select the Save button twice on Chrome browsers in order to properly save the record. 
    Tracking code: STE-20427
  • When accessing a View Profile Summary using Tools | Preferences, Suite no longer returns an Operation Failed message.
    Tracking code: STE-20908
  • In Advanced Search, for fields that are lookups, the "Starts With" and "Contains" operators now allow for text entry instead of only allowing a selected value.
    Tracking code: STE-21445

eCounsel

  • For clients with a Collaborati integration, the LEDES invoice submitted by the vendor that was automatically attached to the eCounsel invoice now is prepended with an identifier on eCounsel deployments that use a File Server storage method to avoid overwriting existing files with the same name. 
    Tracking code: STE-20546
  • For clients with a Collaborati integration, an invoice administrator can now deauthorize and deactivate a vendor so that the entity can be remapped using Collaborati.
    Tracking code: STE-21501
  • For clients with a Corridor integration, the Configure Invoice Submission period in Suite Manager settings no longer apply to invoice submissions. These settings only apply to the sychronization of matters to vendors in Corridor for manual invoice submission. So, if the client has installed the Corridor Matter Vendor task and is synchronizing matters to Corridor, only those matters with a close date or inactive player will synchronize for the number of days specified. All matters with no close date and active player records for the vendor will continue to synchronize with Corridor.
    Tracking code: STE-20800
  • Adding new contact information on the EDGE browser now works properly.
    Tracking code: STE-17311
  • For Collaborati integrations, pagination has been added to requests for records from Collaborati to resolve an issue with Collaborati timing out prior to eCounsel retrieving the entire list of items.
    Tracking code: STE-20172
  • When entering multiple line items for an invoice by clicking the Save/New button, the button bar on the top of the dialog box now persists. 
    Tracking code: STE-20929
  • When composing an accrual notification in eCounsel, the lines break according to carriage returns in the text when sending the email.
    Tracking code: STE-20514
  • If the Invoices Matter Tax Detail tab is hidden by view or type profile, the Billed Currency Pre-tax and Base Currency Pre-tax fields on the Invoices Summary page now display the appropriate values. 
    Tracking code: STE-20942
  • For invoices that are submitted via the Corridor Website, but are not imported into the client's eCounsel matter management system because the client/vendor relationship is disabled, The Invoice Status page in Corridor now displays an error "Invoice failed to import. Error: The client / vendor relationship is not active in eCounsel. See your system administrator." The client invoice administrator must enable the relationship in eCounsel with the law firm/vendor. The law firm/vendor should resubmit the invoice once the relationship is enabled.
    Tracking code: STE-19381
  • Editing older invoices no longer returns a Null pointer exception error.
    Tracking code: STE-21369
  • If your company has installed the Corridor Vendor Matters task to synchronize matter information so vendors can submit manual invoices through the Corridor Website, now if a matter has multiple players that are vendors in Corridor, the matter will synchronize with each vendor in Corridor.
    Tracking code: STE-21210
  • If your company has installed the Corridor Vendor Matters task to synchronize matter information so vendors can submit manual invoices through the Corridor Website, now vendors can only select from matters that belong to a particular client.
    Tracking code: STE-21578
  • In advanced search, when you add user fields as criteria or as result fields from the Matters Base Info tab, then sort by Legal Section, an error is no longer returned.
    Tracking code: STE-21263
  • In Advanced Search, searching on the Evaluations tab for Entities and People now returns results.
    Tracking code: STE-21367
  • The Timekeeper Import Wizard no longer fails to upload an email address that contains as apostrophe (') prior to the @ symbol. 
    Tracking code: STE-21292
  • For Corridor integrations, resolved an error when activating a law firm/vendor with more than 20 characters in the Tax ID since Corridor only accepts 20 characters for Tax ID. 
    Tracking code: STE-21118
  • If the Document tab is hidden in eCounsel, you can now delete a matter with progress notes and the progress notes will be deleted with the matter.
    Tracking code: STE-21614
  • Custom dynamic filters on the Entities Employees tab no longer return an error on Person_ID.
    Tracking code: STE-21538
  • The Timekeeper File Import wizard in eCounsel no longer takes excessive time to process timekeepers.
    Tracking code: STE-20946
  • For Collaborati integrations, when Collaborati fails to send the complete information concerning an invoice to eCounsel, the error message has been modified to indicate information to aid in troubleshooting the issue.
    Tracking code: STE-21146
  • For clients with an Accounts Payable (AP) integration, importing payment information from the AP system into eCounsel now displays the proper error if invoice payment information is submitted that does not have an invoice record in eCounsel. In addition, the task will continue to process invoices in the file after this error occurs.
    Tracking code: STE-21215
  • When searching in grid lists in the Invoices module with a deployment using an Oracle database, searches are now case insensitive.
    Tracking code: STE-21708
  • The XML parser for Tomcat Java Application Servers has been updated in darwinmaster.properties if using i-net reports. Specify javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl as the value in darwin.properties to resolve any issues with i-net reports. If using Business Objects with an Apache Tomcat Java Application Server, update the XML transformer to javax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl in darwin.properties to resolve any issues when testing the connection.
    Tracking code: STE-20876
  • Tax amounts now appear properly on the Invoices Summary page.
    Tracking code: STE-21955
  • The Invoice Amount Minimum rule has been updated to include a new parameter, "Ignore Foreign Currency Invoices (Y/N)", so that the rule now can validate all invoices regardless of currency. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.
    Tracking code: STE-21970
  • The Rate Validation rule has been updated to provide clients with the option to change the content of the message that is sent when an invoice is rejected. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.
    Tracking code: STE-22002
  • The Invoice Routing Rule has been updated so that an approver is only added after the pre-approver for that approver has approved the invoice. This rule is self-installing rule and relies on the installation of the ruleinstallerhelper rule prior to installing the rule.
    Tracking code: STE-21981
  • When exporting timekeepers from the Entities Employees tab, only timekeepers for entities that are classified as “Vendors” can be exported. A database script has been provided with the service pack to remove this constraint.
    Tracking code: STE-21806

Secretariat

  • For the Global Appoint/Promote/Retire Positions Wizard and Copy Data Wizard, selecting all the records, then de-selecting some records still changed all the records.
    Tracking code: STE-21981STE-22068

Office Link

  • Removed the following statement from the logs since it was incorrectly logged as an error: Client.OfficeRestClient [auto refresh] - Error raised when invalid list of ids., details.
    Tracking code: STE-18692
  • For attachments in Office Link, modifying the metadata no longer returns an error.
    Tracking code: STE-20658
  • Dragging-and-dropping a document in the Office Link addin from a Cloud location such as Google Drive now properly adds the file to eCounsel/Secretariat.
    Tracking code: STE-21341
  • When installing and logging into the Outlook addin and Office addin, the credentials entered when installing the Outlook addin will be used when installing the Office addin. If you change the credentials in the Office addin, it will impact the Outlook addin and vice versa since the addins share a configuration file.
    Tracking code: STE-13111
  • For Office Link, the Matters Most Recently Accessed filter no longer includes new matters to which a player had been assigned if the new matter has not been recently accessed.
    Tracking code: STE-14287
  • When calendering is disabled in Suite Manager for Office Link, appointments and tasks in Microsoft Outlook are no longer updated. If calendaring is re-enabled, any appointments/tasks added to the Mitratech Calendar used by Office Link will be overwritten by eCounsel or Secretariat.
    Tracking code: STE-20582
  • When editing the metadata of an item, selecting the Update Outlook Category checkbox no longer returns an unhandled exception.
    Tracking code: STE-21751
  • For Mitratech Office Link, if an appointment is created in eCounsel or Secretariat without an end date and end time, eCounsel will send the appointment to Microsoft Outlook invitees as an all-day appointment. If the end date and end time were omitted in error, resolve the issue in either eCounsel or Secretariat (by adding an end date and end time to the appointment so that it resyncs with Microsoft Outlook) or in Microsoft Outlook (by removing the All-day event designation and specifying the duration of the appointment so that it resyncs with eCounsel or Secretariat).
    Tracking code: STE-21802
  • For Mitratech Office Link, if an appointment is created in eCounsel or Secretariat as an All-day event, it is no longer necessary to specify the end date and end time. eCounsel or Secretariat will send the appointment as an all-day event to Microsoft Outlook. For multi-day all-day events, simply specify an end date and time that is past the start date.
    Tracking code: STE-21802

Bridgeway Link

  • Added support for SAML authentication with Bridgeway Link.
    Tracking code: STE-20489
  • When clicking on the Bridgeway Link add-in in Microsoft Outlook prior to logging in, the user no longer receives a missing or invalid session token error.
    Tracking code: STE-10551
  • When viewing a list of matters in Bridgeway Link, selecting the Print button no longer returns an error.
    Tracking code: STE-10300

Dependencies

This service pack requires the previous installation of the following:

  • suite8.11.0.sp12.2

This service pack includes an update to the following:

  • Suite (suite8.11.0.sp13.1)
  • Update Manager Version 1.0.10
  • Suite Manager (SuiteManager.exe)
  • Mitratech Outlook Add-in
  • Mitratech Office Add-in
  • Bridgeway Link Add-in

One of the following scripts needs to be run against the database:

  • suite8.11.0.sp13.1-Scripts-Oracle
  • suite8.11.0.sp13.1-Scripts-SQL

The following rules have been updated or are new: 

  • New Matter Alert
  • New Player Alert
  • Timekeeper Employment Validation (Oracle databases only)
  • Invoice Amount Minimum
  • Rate Validation
  • Maximum Expense Values
  • Maximum Expense Values with Configuration
  • Line Item Date Past Matter Close
  • Require Corridor Attachments Task

Downloads

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

If using Mitratech Office Link, the following add-ins need to be installed:

If using Bridgeway Link with eCounsel, the following add-in needs to be installed:

The following rules can be imported to take advantage of issue resolutions and new features:

The following database scripts can be used to export timekeepers from eCounsel for upload into Corridor:

Installation Instructions

Suite Installation Instructions

  1. Stop the Bridgeway Suite application on the Java application server.
  2. Use Update Manager to install the suite8.11.0.sp13.1 update. Update Manager will back up the following files: 
  • cshomepage\cshp_main.htm
  • cshomepage\cshp_top.htm
  • cshomepage\reportpromptwizard_main.htm
  • css\global.css
  • htm\customreportswizard_top.htm
  • htm\docasm_genprompt_top.htm
  • htm\docasmwiz_top.htm
  • htm\docimportwiz_filebrowse.htm
  • htm\documentsavefile.htm
  • htm\executesearch.htm
  • htm\hyperlinkedit.htm
  • htm\longcomments.htm
  • htm\multiselect.htm
  • htm\openwindow.htm
  • htm\output_edit_main.htm
  • htm\reportprompt_noprompt.htm
  • htm\reportprompt_simple.htm
  • htm\search_runprompt.htm
  • htm\sendemail.htm
  • htm\singleedit.htm
  • htm\userfields_edit_main.htm
  • htm\wizardscategory_edit_main.htm
  • htm\wizardstemplate_edit_main.htm
  • htm\wizards_edit_main.htm
  • htm\ecounsel\copymattername.htm
  • htm\ecounsel\copymatterwizard_top.htm
  • htm\ecounsel\corr_activatelawfirm.htm
  • htm\ecounsel\globalassignwizard_top.htm
  • htm\ecounsel\playerreassignwizard_top.htm
  • htm\ecounsel\privatematter.htm
  • htm\ecounsel\timekeeperfileimportwizard_main.htm
  • htm\elobby\sendemail.htm
  • htm\secretariat\calura_edit_main.htm
  • htm\secretariat\noteshistoryfile_edit_main.htm
  • htm\secretariat\title_edit_main.htm
  • htm\secretariat\wizards\cdwizard_types_main.htm
  • htm\secretariat\wizards\cmwizard_positions_main.htm
  • htm\secretariat\wizards\cmwizard_reelect_bottom.htm
  • htm\secretariat\wizards\cmwizard_reelect_main.htm
  • htm\secretariat\wizards\copydatawizard_main.htm
  • htm\secretariat\wizards\corpchartswizard_top.htm
  • htm\secretariat\wizards\corpmeetingwizard_main.htm
  • htm\secretariat\wizards\entitycswizard_main.htm
  • htm\secretariat\wizards\globalaprwizard_main.htm
  • htm\secretariat\wizards\globalsortorderupdatewizard_top.htm
  • htm\secretariat\wizards\wizards_top.htm
  • htm\spellcheck\xsc_server.jsp
  • javascript\bsi_hotkey_manager.js
  • javascript\calendarview_include.js
  • javascript\darwin_globals.js
  • javascript\data.js
  • javascript\datagrid.js
  • javascript\directory_tree.js
  • javascript\listpagemanager.js
  • javascript\lobby_pagination.js
  • javascript\notificationmanager.js
  • javascript\searchmanager.js
  • javascript\ajax\stateful_ajax.js
  • javascript\dhtml\common\prototype.js
  • toplink\BSICommon\com.bsi.dataclasses.bsicommon.LkupMatter.descriptor
  • toplink\BSICommon\com.bsi.dataclasses.bsicommon.LkupMatter.topclass
  • toplink\Calendar\com.bsi.dataclasses.calendar.Calendar.descriptor
  • toplink\Matter\com.bsi.dataclasses.matter.LkupMatter.descriptor
  • toplink\Matter\com.bsi.dataclasses.matter.LkupMatter.topclass
  • toplink\Matter\com.bsi.dataclasses.matter.Matter.topclass
  • WEB-INF\classes\com\bridgeway\api\utilities\Dates.class
  • WEB-INF\classes\com\bridgeway\lobby\serviceclients\CSCServiceOfProcess.class
  • WEB-INF\classes\com\bridgeway\suite\report\boreport\util\BSICrypt.class
  • WEB-INF\classes\com\bridgeway\utilities\BSICrypt.class
  • WEB-INF\classes\com\bridgeway\utilities\BSICrypt3DesSpec.class
  • WEB-INF\classes\com\bridgeway\utilities\SSLTunnelSocketFactory.class
  • WEB-INF\classes\com\bridgeway\utilities\URLConnectionHelper.class
  • WEB-INF\classes\com\bsi\attributes\darwinmaster.properties
  • WEB-INF\classes\com\bsi\buslogic\invoice\collaborati\CollaboratiInvoiceMapper.class
  • WEB-INF\classes\com\bsi\buslogic\invoice\collaborati\CollaboratiInvoiceParser.class
  • WEB-INF\classes\com\bsi\buslogic\invoice\ledes\Importer.class
  • WEB-INF\classes\com\bsi\control\DateRangeConstants.class
  • WEB-INF\classes\com\bsi\control\DateRangeInfo.class
  • WEB-INF\classes\com\bsi\control\IListCommand.class
  • WEB-INF\classes\com\bsi\control\ListCommand$ListPositioner.class
  • WEB-INF\classes\com\bsi\control\ListCommand.class
  • WEB-INF\classes\com\bsi\control\SearchOptions.class
  • WEB-INF\classes\com\bsi\control\admin\ModuleListCommand.class
  • WEB-INF\classes\com\bsi\control\admin\TabHierachicalListCommand.class
  • WEB-INF\classes\com\bsi\control\admin\TabListCommand.class
  • WEB-INF\classes\com\bsi\control\ecounsel\PluginPrefsDisplayCommand.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand$1.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand$AccessEInvoicing.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand$ActivateCorridor.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand$ActivateEInvoicing.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand$ActivateEMail.class
  • WEB-INF\classes\com\bsi\control\invoice\ActivateEInvoicingCommand.class
  • WEB-INF\classes\com\bsi\control\outputadmin\UploadOutputCommand.class
  • WEB-INF\classes\com\bsi\control\search\GetLooukUpFields.class
  • WEB-INF\classes\com\bsi\control\search\HtmlSearchResultsWriter.class
  • WEB-INF\classes\com\bsi\control\search\SearchResultsWriter.class
  • WEB-INF\classes\com\bsi\dataclasses\BaseFieldMetadata$OtherOtoDisplayValueFields.class
  • WEB-INF\classes\com\bsi\dataclasses\BaseFieldMetadata.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\Address.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\ContactInfo.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\Document.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\DocumentFile.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\EntityAddress.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\Evaluation.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\Group.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\LkupEntity.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\LkupMatter.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\LkupPlayerPerson.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\LkupUser.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\RelationshipClass.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\RelationshipClassHelper.class
  • WEB-INF\classes\com\bsi\dataclasses\bsicommon\UserField.class
  • WEB-INF\classes\com\bsi\dataclasses\calendar\Calendar.class
  • WEB-INF\classes\com\bsi\dataclasses\calendar\Jurisdiction.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\CostManagement.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\CostManagementEmail.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\Invoice.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\InvoiceAllocation.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\InvoiceApproval.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\InvoiceDetail.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\InvoiceDetailTaxable.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\LkupInvoice.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\MatterInvoice.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\MatterInvoiceTaxSummary.class
  • WEB-INF\classes\com\bsi\dataclasses\invoice\MatterInvoiceTaxSummaryVendor.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\Address.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\Agent.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\AgentForId.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\Entity.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\EntityAddress.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\Jurisdiction.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\JurisdictionContact.class
  • WEB-INF\classes\com\bsi\dataclasses\jurisdiction\LKJurisHelper.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\BudgetDetail.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\GoodService.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\LkupBudget.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\LkupMatter.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MruMatter.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\LkupMatterHelper.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\LkupPlayer.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Matter.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterAccrual.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterAccrualNotify.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterBudget.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterCalendar.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterCalendarEventUser.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterDamage.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterExposure.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterInsuranceClaim.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterInsurancePolicy.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterLitigation.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterLitigationJudge.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterNegotiation.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterPlayer.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterRecovery.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterRelated.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterReserve.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MatterTypePhase.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\MruMatter.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Opposition.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Patent.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Phase.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\PhysicalFile.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\PhysicalFileAction.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\PlayerContactInfo.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Task.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\Trademark.class
  • WEB-INF\classes\com\bsi\dataclasses\matter\UserMatter.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\BillingInfo.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Company.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\CompanyPerson.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Court.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\CourtPerson.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Employment.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Entity.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Evaluation.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\ExpertiseAffiliation.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\InsurancePolicy.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\MattersVendors.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\MruEntity.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\MruV_Entity.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Person.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\Timekeeper.class
  • WEB-INF\classes\com\bsi\dataclasses\peopleentity\V_Entity.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Agent.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\AlternateName.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Calura.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Canada.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Company.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\CompanyPerson.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\DBAName.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Entity.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\FormerName.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Jurisdiction.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\LkupCompany.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\LkupEntity.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Member.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\MruEntity.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Ownership.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\PermanentRelationship.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Person.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Registration.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Security.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\SecurityDividend.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\SecurityIssued.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\SecurityTransaction.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\Title.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\entity\UnitsShareholders.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\CompanyPerson.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\Member.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\MruPeople.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\PermanentRelationship.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\Person.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\Title.class
  • WEB-INF\classes\com\bsi\dataclasses\secretariat\people\TitleList.class
  • WEB-INF\classes\com\bsi\dataclasses\wizards\CorpTask.class
  • WEB-INF\classes\com\bsi\dataclasses\wizards\CorpTaskAccess.class
  • WEB-INF\classes\com\bsi\dataclasses\wizards\CorpTaskFavorite.class
  • WEB-INF\classes\com\bsi\dataclasses\wizards\TaskDocs.class
  • WEB-INF\classes\com\bsi\datalogic\BaseLogic.class
  • WEB-INF\classes\com\bsi\datalogic\DeleteLogic.class
  • WEB-INF\classes\com\bsi\datalogic\GetClassList.class
  • WEB-INF\classes\com\bsi\datalogic\GetObjectID.class
  • WEB-INF\classes\com\bsi\datalogic\ListLogic.class
  • WEB-INF\classes\com\bsi\datalogic\MetadataService.class
  • WEB-INF\classes\com\bsi\datalogic\ModuleSearch.class
  • WEB-INF\classes\com\bsi\datalogic\UpdateLogic.class
  • WEB-INF\classes\com\bsi\datalogic\admin\DocumentsDirectoryList.class
  • WEB-INF\classes\com\bsi\datalogic\admin\ModuleList.class
  • WEB-INF\classes\com\bsi\datalogic\admin\SuiteSystemSettings.class
  • WEB-INF\classes\com\bsi\datalogic\admin\TabList.class
  • WEB-INF\classes\com\bsi\datalogic\admin\UserList.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\InvoiceApprovalList$1.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\InvoiceApprovalList.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\InvoiceDetailList.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\corridor\CorridorSettings.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\corridor\IBSI_SI_ServiceHttpBindingStub.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\corridor\IBSI_SI_ServicePortType.class
  • WEB-INF\classes\com\bsi\datalogic\invoice\ebilling\GenericInvoiceImport.class
  • WEB-INF\classes\com\bsi\datalogic\matter\LkupPlayerPersonList.class
  • WEB-INF\classes\com\bsi\datalogic\matter\MatterDelete.class
  • WEB-INF\classes\com\bsi\datalogic\matter\MatterList.class
  • WEB-INF\classes\com\bsi\datalogic\matter\MatterPlayerUpdate.class
  • WEB-INF\classes\com\bsi\datalogic\matter\MatterUpdate.class
  • WEB-INF\classes\com\bsi\datalogic\outputadmin\OutputUpdate.class
  • WEB-INF\classes\com\bsi\datalogic\peopleentity\CompanyUpdate.class
  • WEB-INF\classes\com\bsi\datalogic\peopleentity\CompanyView.class
  • WEB-INF\classes\com\bsi\datalogic\peopleentity\EmploymentList.class
  • WEB-INF\classes\com\bsi\datalogic\peopleentity\EvaluationList.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$1.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$BoxInfo.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$CurrentVisioShapeProperty.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$LineInfo.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$OwnershipInfo.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter$ShapeFontColorInfo.class
  • WEB-INF\classes\com\bsi\datalogic\secretariat\corpcharts\CorpChartsBULToVisioExporter.class
  • WEB-INF\classes\com\bsi\datalogic\timekeeper\TimekeeperFileImport$1.class
  • WEB-INF\classes\com\bsi\datalogic\timekeeper\TimekeeperFileImport.class
  • WEB-INF\classes\com\bsi\datalogic\userfield\ModuleUserFieldList.class
  • WEB-INF\classes\com\bsi\datalogic\userfield\UserFieldPseudoList.class
  • WEB-INF\classes\com\bsi\datalogic\userfield\UserFieldPseudoView.class
  • WEB-INF\classes\com\bsi\datalogic\userfield\UserFieldSearcher.class
  • WEB-INF\classes\com\bsi\doccreation\ExtSaxParser.class
  • WEB-INF\classes\com\bsi\importexport\ecounsel\ecMapSupport.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\AddInEnabledInterceptor.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\controller\FilesController.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\dao\AppointmentData.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\dao\FileData.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\dao\InvoiceData.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\dao\MatterData.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\auth\AuthServerConfig.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\exception\ApiGlobalExceptionHandler.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\model\Appointment.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\model\Setting.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\model\Invoice.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\service\FileServiceImpl.class
  • WEB-INF\classes\com\bsi\officelink\rest\v1\service\SettingServiceImpl.class
  • WEB-INF\classes\com\bsi\repository\BaseDataset$FindItem.class
  • WEB-INF\classes\com\bsi\repository\BaseDataset$LGSecurity.class
  • WEB-INF\classes\com\bsi\repository\BaseDataset$MruFilter.class
  • WEB-INF\classes\com\bsi\repository\BaseDataset.class
  • WEB-INF\classes\com\bsi\repository\invoice\InvoiceApprovalDataset.class
  • WEB-INF\classes\com\bsi\repository\invoice\InvoicesDataset.class
  • WEB-INF\classes\com\bsi\repository\matter\MattersDataset.class
  • WEB-INF\classes\com\bsi\repository\peopleentity\CompanyPersonDataset.class
  • WEB-INF\classes\com\bsi\repository\peopleentity\CourtPersonDataset.class
  • WEB-INF\classes\com\bsi\repository\peopleentity\V_EntityDataset.class
  • WEB-INF\classes\com\bsi\scheduler\dataclasses\MatterVendorInfo.class
  • WEB-INF\classes\com\bsi\scheduler\task\CollaboratiInvoiceTask.class
  • WEB-INF\classes\com\bsi\scheduler\task\CorrCostManagementTask$1.class
  • WEB-INF\classes\com\bsi\scheduler\task\CorrCostManagementTask$InvoiceAttachment.class
  • WEB-INF\classes\com\bsi\scheduler\task\CorrCostManagementTask$ThisVendor.class
  • WEB-INF\classes\com\bsi\scheduler\task\CorrCostManagementTask.class
  • WEB-INF\classes\com\bsi\scheduler\task\CorrMattersForVendorsTask.class
  • WEB-INF\classes\com\bsi\security\DataFilter.class
  • WEB-INF\classes\com\bsi\security\bsicommon\BSIDataFilter$LGSecurity.class
  • WEB-INF\classes\com\bsi\security\bsicommon\BSIDataFilter$SqlTableInfo.class
  • WEB-INF\classes\com\bsi\security\bsicommon\BSIDataFilter.class
  • WEB-INF\classes\com\bsi\security\bsicommon\UserValidator.class
  • WEB-INF\classes\com\bsi\servlets\AppLaunchServlet$ApplyAppParams.class
  • WEB-INF\classes\com\bsi\servlets\AppLaunchServlet$ShowEnvironment.class
  • WEB-INF\classes\com\bsi\servlets\AppLaunchServlet.class
  • WEB-INF\classes\com\bsi\util\BSICryptRC4SHA1.class
  • WEB-INF\classes\com\bsi\util\ClassParser$1.class
  • WEB-INF\classes\com\bsi\util\ClassParser$AdhocField.class
  • WEB-INF\classes\com\bsi\util\ClassParser$HelperGetter.class
  • WEB-INF\classes\com\bsi\util\ClassParser.class
  • WEB-INF\classes\com\bsi\util\CollaboratiIntegrationUtils.class
  • WEB-INF\classes\com\bsi\util\DarUtil$1.class
  • WEB-INF\classes\com\bsi\util\DarUtil$DateTimeType.class
  • WEB-INF\classes\com\bsi\util\DarUtil$RetryConnectionException.class
  • WEB-INF\classes\com\bsi\util\DarUtil.class
  • WEB-INF\classes\com\bsi\util\DataClassParser.class
  • WEB-INF\classes\com\bsi\util\DocumentStorageSettings.class 
  • WEB-INF\classes\com\bsi\util\Metadata.class
  • WEB-INF\classes\com\bsi\util\SearchCondition.class
  • WEB-INF\classes\com\bsi\util\bsicommon\GenConstants.class
  • WEB-INF\classes\com\bsi\util\invoice\InvUtil.class
  • WEB-INF\lib\collaborati-rest-client.jar
  • WEB-INF\lib\jackson-annotations.jar
  • WEB-INF\lib\jackson-core.jar
  • WEB-INF\lib\jackson-databind.jar
  • xsl\bsicommon\accrual_notification_scheduler.xsl
  • xsl\bsicommon\calendarview_appointment.xsl
  • xsl\bsicommon\contactinfolist.xsl
  • xsl\bsicommon\documentuploadprompt.xsl
  • xsl\bsicommon\duplicatecheck_entity.xsl
  • xsl\bsicommon\editlobbycomments.xsl
  • xsl\bsicommon\edittemplates.xsl
  • xsl\bsicommon\generictemplates.xsl
  • xsl\bsicommon\groupsummarydetail.xsl
  • xsl\bsicommon\installers.xsl
  • xsl\bsicommon\listtemplates.xsl
  • xsl\bsicommon\loginprompt.xsl
  • xsl\bsicommon\reportpromptwizard_main.xsl
  • xsl\bsicommon\reportscheduler_detail.xsl
  • xsl\bsicommon\reportscheduler_recipients.xsl
  • xsl\bsicommon\reportschedulerDetailDeleted.xsl
  • xsl\bsicommon\ruleprofilesummaryassociationmultiple.xsl
  • xsl\bsicommon\summarytemplates.xsl
  • xsl\bsicommon\timekeeperfileimportwizard_list.xsl
  • xsl\bsicommon\timekeeperfileimportwizard_rejection.xsl
  • xsl\bsicommon\timekeeperfileimportwizard_results.xsl
  • xsl\bsicommon\timekeeperfileimportwizard_selection.xsl
  • xsl\bsicommon\tools.xsl
  • xsl\bsicommon\tools_usersummary.xsl
  • xsl\bsicommon\viewprofilesummarylist.xsl
  • xsl\bsicommon\viewprofilesummarytools.xsl
  • xsl\elobby\lobby_limitedrights.xsl
  • xsl\elobby\sop_newcorrtimekeeper.xsl
  • xsl\elobby\sop_newmatter.xsl
  • xsl\elobby\sop_newtimekeeper.xsl
  • xsl\elobby\sop_newvendor.xsl
  • xsl\homepage\homepagetemplates.xsl
  • xsl\invoice\invoicedetailview.xsl
  • xsl\invoice\invoicediscount.xsl
  • xsl\invoice\invoicereject.xsl
  • xsl\invoice\invoicesummary.xsl
  • xsl\matter\matter_prefs.xsl
  • xsl\matter\newmatter.xsl
  • xsl\peopleentity\companyview_template.xsl
  • xsl\peopleentity\timekeepermappedmessage.xsl
  • xsl\peopleentity\vendormappedmessage.xsl
  • xsl\SecrEntity\copydatawiz_positionslist.xsl
  • xsl\SecrEntity\copydatawiz_registrationlist.xsl
  • xsl\SecrEntity\entitycswizard_page1.xsl
  • xsl\SecrEntity\entitylist.xsl
  • xsl\SecrEntity\securitytransactionview.xsl
  • xsl\SecrPeople\globaprwiztitlesheldlist.xsl
  • xsl\widgets\alerts_lobby.xsl
  • xsl\wizards\wizardtemplates.xsl
  1. Restart the Bridgeway Suite application on the Java application server.

Database Script Instructions

  1. Using your preferred database tool (SQL Server Management Studio, Oracle's RMAN utility, Oracle's export data pump utility, etc.), make a backup of your Suite database.
  2.  Login to your query tool as an administrative user.
  3.  Open the appropriate scripts .ZIP file for your database: 
    • suite8.11.0.sp13.1-Scripts-Oracle.zip for Oracle databases
    • suite8.11.0.sp13.1-Scripts-SQL.zip for SQL databases
  4. Open and run the SQL script.

Update Manager Installation Instructions

  1. Stop the Update Manager application on the Java application server.
  2. Backup the existing Update Manager war or ear file on the Java application server.
  3. Copy the downloaded war or ear file from the Downloads section of these release notes and replace the current file with the new file.
  4. Restart the Update Manager application on the Java application server.

Suite Manager Installation Instructions

  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.

Bridgeway Link Installation Instructions


If you are not using Bridgeway Link, disregard these instructions.

  1. Uninstall the previous version of Bridgeway Link.
  2. Extract the Bridgeway Link.exe file from the .zip file.
  3. Start the Bridgeway Link.exe installation in the directory in which the file was extracted.
  4. Click Next on the Welcome and Uninstall Previous Versions screens.
  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 and click Next.
  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.

Mitratech Office Link Installation Instruction

  1. Uninstall the existing add-ins using the “Add and Remove” feature in the Microsoft Windows Control Panel or by double-clicking the original installation files and selecting the Remove Mitratech Office Link Add-in option.
  2. Extract the contents of MitratechOutlookAddInSetup.zip.
  3. Click the setup.exe file to run the installer and follow the instructions on the installation wizard.
  4. When prompted, enter the appropriate information:
    • In the Login URL field, type the login URL for your instance of Suite. Include http:// at the beginning or the URL and a trailing slash (/) at the end of the URL.
      • If left empty, the Login URL field will be populated from the default information in OfficeSetting.ini when the add-in is installed. The user will be prompted for the correct URL when Microsoft Outlook or Office application is opened.
      • For situations in which eCounsel and Secretariat are installed but the user only has access to Secretariat and not to eCounsel, the URL must include -2 at the end of the URL before the trailing slash (/). For example:
        https://suite.companydomain.com:7002...1/~database-2/
    • In the Login URL Editable field, type TRUE or FALSE:
      • TRUE enables the user to change the login URL after the add-in is installed.
      • FALSE ensures that the user cannot edit the login URL and is only applicable if a login URL is designated.
      • If left empty, this field defaults to TRUE.
  5. To make an add-in available for other accounts on the same machine, run the installer for each user account and select the Repair option. The Repair installation must be run for each add-in. If the OfficeSettings.ini from the default directory path contains a valid login URL, the add-ins will be available without any error. If it does not have the login URL information, ignore the exceptions until the system requests the credentials and saves the valid login URL in OfficeSettings.ini from User directory path.
  6. Repeat these steps for the MitratechOfficeAddInSetup.zip.
  7. Repeat these steps on each machine that uses Mitratech Office Link.

For more information, see the installation instructions in the Mitratech Office Link Administrator’s Guide or Mitratech Office Link User’s Guide.

Rule Installation Instructions

New Matter Alert/New Player Alert Rule Installation Instructions

  1. Depending on the encryption that you use (standard or unlimited), extract the contents from the following .ZIP files to a location accessible by the Bridgeway Suite server:
    • NewMatterAlert.zip
    • NewPlayerAlert.zip
  2. Open Suite Manager.
  3. On the Suite Manager control panel, click the Rules Engine component in the Tools & Utilities area.
  4. On the Rules Engine window, click the Alerts tab at the top of the window.
  5. Click the NewMatterAlert rule to select it, click the Delete button, and click Yes to confirm deletion.
  6. Click Import, navigate to the NewMatterAlert.bsi and/or NewPlayerAlert.bsi file from Step 1, and then click Open.
  7. In the dialog box, configure the parameters for the rule, and click Save and Close.
  8. After importing the rule, click the Refresh All Application Server Settings button on the General tab of System Settings to trigger a cache refresh so that the rule is implemented immediately.

Timekeeper Employment Validation (Oracle Only) Rule Installation Instructions

  1. Depending on the encryption that you use (standard or unlimited), extract the contents from the following .ZIP files to a location accessible by the Bridgeway Suite server:
    • TimeKeeperEmploymentValidationORA.zip
  2. Open Suite Manager.
  3. On the Suite Manager control panel, click the Rules Engine component in the Tools & Utilities area.
  4. On the Rules Engine window, click the Validation tab at the top of the window.
  5. Click the TimekeeperEmploymentValidation rule to select it, click the Delete button, and click Yes to confirm deletion.
  6. Click Import, navigate to the TimekeeperEmploymentValidationORA.bsi file from Step 1, and then click Open.
  7. In the dialog box, configure the parameters for the rule, and click Save and Close.
  8. After importing the rule, click the Refresh All Application Server Settings button on the General tab of System Settings to trigger a cache refresh so that the rule is implemented immediately.

Invoice Amount Minimum/Rate Validation Rule Installation Instructions

  1. Depending on the encryption that you use (standard or unlimited), extract the contents from the following .ZIP files to a location accessible by the Bridgeway Suite server:
    • InvoiceAmountMinimum.zip
    • RateValidation.zip
  2. Open Suite Manager.
  3. On the Suite Manager control panel, click the Rules Engine component in the Tools & Utilities area.
  4. On the Rules Engine window, click the Alerts tab at the top of the window.
  5. Click the InvoiceAmountMinimum rule and/or RateValidation rule to select it, click the Delete button, and click Yes to confirm deletion.
  6. Click Import, navigate to the InvoiceAmountMinimum.bsi file and/or RateValidation.bsi from Step 1, and then click Open.
  7. In the dialog box, configure the parameters for the rule, and click Save and Close.
  8. After importing the rule, click the Refresh All Application Server Settings button on the General tab of System Settings to trigger a cache refresh so that the rule is implemented immediately.

Maximum Expense Values/Maximum Expense Values with Configuration Installation Instructions

  1. Depending on the encryption that you use (standard or unlimited), extract the contents from the following .ZIP files to a location accessible by the Bridgeway Suite server:
    • MaxExpenseValues.zip
    • MaxExpenseValuesWithConfigFile.zip
  2. Open Suite Manager.
  3. On the Suite Manager control panel, click the Rules Engine component in the Tools & Utilities area.
  4. On the Rules Engine window, click the Alerts tab at the top of the window.
  5. Click the Max Rate, Maximum Expense Rate, Expense Rate, Expense Code per Unit, and Maximum Expense Amount rules to select each, click the Delete button, and click Yes to confirm deletion. 
  6. Click Import, navigate to the MaxExpenseValues.bsi file or MaxExpenseValuesWithConfigFile.bsi from Step 1, and then click Open.
  7. In the dialog box, configure the parameters for the rule, and click Save and Close.
  8. After importing the rule, click the Refresh All Application Server Settings button on the General tab of System Settings to trigger a cache refresh so that the rule is implemented immediately.

Line Item Date Past Matter Close/Require Corridor Attachments Task Rule Installation Instructions

  1. Depending on the encryption that you use (standard or unlimited), extract the contents from the following .ZIP files to a location accessible by the Bridgeway Suite server:
    • LineItemDatePastMatterClose.zip
    • RequireCorridorAttachmentsTask.zip
  2. Open Suite Manager.
  3. On the Suite Manager control panel, click the Rules Engine component in the Tools & Utilities area.
  4. On the Rules Engine window, click the Workflow tab at the top of the window.
  5. Click Import, navigate to the LineItemDatePastMatterClose.bsi file or RequireCorridorAttachmentsTask.bsi from Step 1, and then click Open.
  6. In the dialog box, configure the parameters for the rule, and click Save and Close.
  7. After importing the rule, click the Refresh All Application Server Settings button on the General tab of System Settings to trigger a cache refresh so that the rule is implemented immediately.

Database Script Instructions for Extracting Timekeepers

To extract Timekeeper information from eCounsel, the following parameters are validated in order to transfer consistent data into Corridor:

  • Entity vendor Tax ID (Tax ID) IS NOT NULL
  • Entity (Name) IS NOT NULL
  • People Timekeeper ID (Admin Number) IS NOT NULL
  • People Job Classification IS NOT NULL
  • People (First Name) IS NOT NULL
  • People (Last Name) IS NOT NULL
  • Employment (Primary Rate) IS NOT NULL
  • Employment (Billing Method) IS NOT NULL
  • Employment (Currency) IS NOT NULL
  • Employment (Begin Date) IS NOT NULL
  • Employment Status =”A'
  • People Timekeeper = 'T’

Note: All timekeepers must have all the required information, or the records will not be extracted from eCounsel.

Database Script Instructions for Microsoft SQL Server Databases

  1. Using SQL Server Management Studio, make a backup of your Suite database.
  2. Login to your query tool as an administrative user.
  3. Make the following changes in the SQL Server Management Studio console:
    • Select the Tools menu, and select Options.
    • On the Options dialog box, select the Query Results node, then select the SQL Server node.
    • Change the Default destination for results dropdown to “Results to text”.
    • Select the Results to Text node under the SQL Server node.
    • Uncheck the Include column headers in the result set checkbox.
    • Change the Maximum number of characters displayed in each column to “8000” instead of “256”.
    • On the Options dialog box, select the Query Execution node, then select the Advanced node.
    • Uncheck the Show completion time checkbox.
    • On the Options dialog box, click OK.
  4. Run the Suite81103001-ExtractTimekeepersFromSuite-SQL.sql script with the "Results to Text" option configured in Step 3.
  5. The query will return the results in the results area. Copy these results to a file named “ImportTimekeepersByVendorFromSuite.sql”.
    • Note: If the resulting file contains dotted lines (- - - - - - - - - - -) that divide some parts of the script file, this content will not be valid. In this case, open a new connection in order to apply the previous changes and rerun the script.
  6. Verify the resulting script file by opening the new script file in SQL Server Management Studio, and select the Parse button. The Results area should indicate the query was parsed successfully.
  7. Provide the results of the SQL script to Mitratech eCounsel Support to upload to Corridor.

Database Script Instructions for Oracle Databases

  1. Using your preferred database tool Oracle's RMAN utility, Oracle's export data pump utility, etc.), make a backup of your Suite database.
  2. Navigate to the Oracle database server machine, and copy the Suite81103001-ExtractTimekeepersFromSuite-ORA.sql file to the C:/ drive or any path accessible from the server.
  3. Open a Command Prompt console as an administrator user.
  4. Type the following command and press enter:
    sqlplus /nolog
  5. Connect to the database from which you want to extract the timekeepers by typing the following command:
    connect <DatabaseSchema>
    where the <DatabaseSchema> is the name of the Suite database.
  6. Enter the password of the database to which you want to connect.
  7. Now type the following and press the Enter key on the keyboard:
    @<Path><FileName>
    where <Path> is the filepath where the script was copied in Step 4, and <FileName> is the Suite81103001-ExtractTimekeepersFromSuite-ORA.sql file you copied in Step 2.
  8. The command will create a file in the same <Path> with the name “ImportTimekeepersFromSuite.sql”. Open the file and verify the contents.
  9. Provide the results of the SQL script to Mitratech eCounsel Support to upload to Corridor.

Note: If the file is generated with no records, this means that NO timekeeper records are available in the active vendors/law firms or the records do not comply with the fields required specified in the “Overview” section.

 

  • Was this article helpful?