CSI Lawyer 11.0 update package 27.6.23

Today 27.6.23 we’ll release a new update package for CSI Lawyer 11.0. As there will be no update package in July, this one contains corrections to all issues either reported by our customers or identified by our own team.

We warmly recommend regular updates particularly for our customers downloading their new versions from the website.

Our customers needing their own update package are also welcome to request a new update package whenever needed. We’ll always deliver it free of charge.

The new update package will fix the following software errors:

Customer

• The grouping of the conflict check report did not work correctly.
• The risk assessment defined for the customer was not transferred to the customer’s matters.
• In the customer identification window, the name of the “Reason for identification level” field was not displayed in red, even though the field was set to mandatory.
• In the Customer Identification window, a user was able to enter more than 500 characters in the Identification Level Reason field, which resulted in an error message (“String or binary data would be truncated…”) because allowed length in the database was only 500 characters.
• If all fields were selected for tracking in the change history, opening the history data of a corporate customer, a private person or a matter gave the error “Item has already been added”.
• Opening and closing the list of mailing list members gave an error message if there were enough members on the list.

Matter

• When a user registered as an assistant in an insider matter who did not have the right to edit the matter details attempted to edit, for example, the name of the matter, the software first gave an error message about the user’s missing rights and then a useless message “Fill all the required fields and/or check that the input data is valid.”
• If all fields were selected for tracking in the change history, opening the history data of a matter gave the error “Item has already been added”.

Entries

• When an expense was posted to a foreign currency matter in the CSI software user interface, the expense was in the matter currency. After the correction, the expense is displayed in the bookkeeping currency but in the expense window you can change it to the matter currency.
• In the mass transfer of expenses, when part of the expenses already were in the target matter, the user received an unclear error message.
• In the Swedish user interface, there were poor translations in the activity’s Recurrence window and some of the activity status were poorly translated.

Invoicing

• When a price adjustment was made for a preliminary invoice, the status of its fixed-priced transactions was also set to “uplifted/downlifted”, although they are not affected by the price adjustment.
• In certain cases, an incorrect amount was shown as a advance suggestion in the Payers folder of a preliminary invoice.
• If an advance had been allocated to the preliminary invoice and part of the advance had previously been refunded, the adjustment proposal displayed the net amount incorrectly for the preliminary invoice payer.
• When the ‘Specification by matter’ parameter was selected in the preliminary invoice preview and the printing criteria saved, that parameter was not saved for use in previewing, creating or sending the invoice.
• When previewing a preliminary invoice or previewing an invoice through a matter, the Invoice Printing Parameters window ignored system-level parameters in certain situations when the database had been created as a copy.
• When the parameter ‘Hide expenses’ was deactivated and ‘Hide expenses from specification’ was activated, the invoice printing dialog confused those parameters.
• The invoice’s original due date was not shown in the printing parameters window of its payment demand. After the correction, the Due date field shows the original due date of the actual invoice and the date cannot be changed.
• If the reference material in KTL format included payments for invoices which were already paid in the CSI software, those payments were not imported at all. After correction, these payments are imported as overpayments and posted.

Sub-matter invoicing

• Creation of a preliminary invoice for parent/child matters was very slow when the customer has lots of preliminary invoices in the database. After the correction the action is completed in 5 seconds vs. former 1 minute). 
• The software gave an ambiguous error message when a user tried and reject the main preliminary invoice, but it was blocked by one or more approved sub preliminary invoices.
• In preliminary invoices, next to the Entry Date field there was a notification about sub preliminary invoices even when there were no sub preliminary invoices.
• An invoice created in a main/sub-matter structure had an unnecessary Share line when there was only one payer. This was due to incorrect rounding in a situation where both the main and sub-matters had expenses of an appropriate amount.

Views and reports

• The “Status” filtering in the “Registered transactions by matter” view was not correct (default filtering: Open) when that view was set as the default view.
• If filters were selected for the transaction list and the Billable/Not billable status for any transaction was changed, the list was unnecessarily reloaded and the filter selections were lost.
• The “Overdue invoices” folder in the Workplace area only showed invoices where the user was the responsible for the matter, but not those in which the user was the owner or the invoicing contact.
• The “Negative Open Amount Invoices” view was selectable in the “Overdue invoices” folder of the Invoicing group in the Workplace task area, where there should not have been a view selection.
• The country information of the address was not printed in the “Matter details” report.
• If a report added to the quick selections for a certain user group was unpublished, the report still remained in the quick selections and the user always received the notification “You do not have access to this information or it no longer exists. The information will be removed from this list.” After the correction, the user will receive the notification only once, after which the report will no longer be found in the quick selections.
• The Swedish “Lista över aktiva ärenden” report had some Finnish terms and spelling mistakes and the “Lista över ärenden” and “Lista över aktiva ärenden” reports, the country of the address was printed in Finnish.
• It was possible to add also unpublished and deactivated views and reports as a quick selection for user groups.

Document Management, integrations

• When a shared folder (CSI. ModulePlugin.SharedFolder.dll plugin) was used for managing documents, changing the name of the customer or matter gave the error “Sequence contains no elements” in some cases.
• When the customer of a  matter was changed, the change did not affect the metadata of the file associated with the matter in the NetDocuments user interface.
• The NetDocuments integration gave the error “Unable to find a constructor to use for type…” when trying to restrict the matter access to a user group. The problem also related to, for example, defining a matter as an insider matter.
• On a small screen, the NetDocuments “Login to API” window could not be fully displayed because it could not be resized nor its contents scrolled.

Bookkeeping integrations

• When Procountor failed to transfer a payment that did not fall within the allowed date range, the information did not appear as a warning in the integration log, but only as a regular data.
• The Procountor integration gave an error message “Value cannot be null” when exporting invoices, if there were no products configured in Procountor.
• When a product was added in the Procountor integration when transferring invoices, the accounting account linked to the CSI software in the integration parameters was not transferred, but the default Procountor account was used. After correction, the correct ledger accounts are displayed in the Account column.
• When an advance or normal invoice was entered into Procountor and accounting lines were created from the invoice, the lines did not display the specified bookkeeping account.
• The Fortnox integration log did not record a situation where there was a problem with the test connection, for example if the token had expired and could not be updated.
• The Fortnox integration also transferred as expenses credit lines with 0 amount.
• “Importing an expense through a bookkeeping integration to a foreign currency matter left its currency amounts at zero. After the correction, the currency of the expense in the CSI software is the bookkeeping currency, and the amount brought from the bookkeeping system is in the bookkeeping currency. 
• “The “Errors and warnings” view in the integration log (Settings > Software Management > Plugins > Integration Logs) displayed not only unprocessed events, but also processed log rows, and downloaded them all without date filtering.
• The integration log of the CSI software did not show sufficiently detailed information about old logs which were deleted when running the integration.
• In the Settings area, it was not possible to mark multiple error/warning lines in the integration log as processed at once.

Other corrections

• The “Round invoices to whole number” parameter was not inherited from the main business unit to its sub-units. 
• In a specific situation, adding an attachment to the notes produced the error “Unexpected error code 50”.
• It was possible to enter more than the allowed number of 20 characters in the name of the budget group, which produced an unclear error message for the user. After the correction, you can enter a maximum of 20 characters in the name.
• Setting the custom field to read-only did not work.