CSI Lawyer 11.0 update package 16.5.23

Today we’ll release a new update package for CSI Lawyer 11.0. Besides fixing software errors, the update package also brings some new features: information about deactivated customers in the Conflict Check report, a possibility to set the reason for price adjustment ass non-mandatory, and a possibility to override the default customer and matter IDs in the NetDocuments integration. Of these improvements we’ll publish a separate description.

The software defects corrected in the update package are as follows:

• When a window with the Notes tab was opened in full screen size, a vertical scroll bar appeared to the right of the window and the scaling of the window was ugly.
• It was not possible to set the ‘Created Transactions by Matter’ view as the default view.
• When a time interval filter was set for a view (e.g. Transactions view) and the view was pinned to the quick selection list, the user received an error message when opening the pinned view if the area data had occasionally been reloaded using the ‘Reload’ function.
• When the user interface language of the software was Swedish, the date column filters either lacked language translations or the language translations were incorrect.
• It was possible to close the software by selecting the X button in the main window, even if the user was adding a new transaction and had not yet saved it.
• When a customer identification event was attached to an existing identification event, its Responsible and Assistant fields were not updated according to the existing identification event.
• When a matter was created by using the ‘Use Matter as Template’ function, it was not displayed in the Favorites list of the user. 
• When a party was opened in the Parties folder, the magnifying glass in the Invoicing Contact field clicked, and a user tried and add a new invoicing contact from the New button, the button was not active.
• When a new archiving number series was created and a matter was archived, the software left the archiving number series empty.
• When a transaction was set as non-billable, the software gave an error and set the transaction to non-billable only after selecting ‘OK’ in the error window.
• When the ‘Warn about zero priced transaction’ parameter was in use, the software incorrectly informed the user about saving a zero-priced transaction even when the matter had a default subscription.
• When a matter had several payers, a trial to create an advance invoice for it in the Advance Invoices folder failed and the software gave an error message.
• When a preliminary invoice or an invoice was created from the selected main and sub-matter transactions, and the expenses were selected to be included, the preliminary invoice and invoice only included the costs of the main matter.
• In a preliminary invoice of a matter having foreign currency and multiple payers, when the payer shares were changed and their total was not 100 %, the software gave an error message with the amounts in the accounting currency instead of the foreign currency. 
• Creating a preliminary  invoice from the selected transactions of the main and sub-matters led to a timeout and a wrong error message.
• When a preliminary invoice containing transactions from both the main and sub-matters was created, and the date of the preliminary invoice was then changed, the date of the sub preliminary invoices remained incorrect.
• When the ‘Use invoice date as entry date’ parameter was in use and a periodical invoice was created with the end date of the invoicing period in the past, the adjustment date of the advance was not the current date but the end date of the invoicing period.
• If the ‘Hide bank accounts from invoice footer’ parameter was enabled, two footers were printed on the invoice, one showing bank accounts and the other not.
• The attempt to create LEDES invoice file crashed and the function was not performed.
• If the invoice had several transactions with the same total amount, the invoice preview from the matter displayed the general expense as too small.
• By selecting the magnifying glass in the Payer field of the invoice window, it was possible to change the payer of the invoice to any customer, even if it was not a matter party having a payer role.
• In addition to important and normal notes, the ‘Cover page’ report of the matter incorrectly displayed also notes which were archived. 
• It was not possible to create a new user with the same name that was already found for a user, even when the existing user was deactivated.
• By default, the integration logs displayed all log events instead of displaying only unhandled errors and warnings that required action.
• When an advance payment set the customer’s invoice as paid, the accounting integration still did not move the zero-sum invoice to the status ‘Paid’.
• If two payments had been mistakenly created for the same invoice in the accounting program, the integration incorrectly imported both payments into the CSI software, even though one of them was not adjusted to the invoice.
• When an overpayment was adjusted to an invoice in the accounting system, the accounting integration transferred the payment to CSI software without posting the excess.
• When advance was applied to the invoice of a customer having a discount percentage, the integration transferred the invoice to Procountor giving discount to the ‘Advances Received’ row which led to an incorrect total amount.
• Fortnox authentication in CSI Lawyer failed because the software opened an empty browser window where data could not be entered.
• When the Due integration was in use and, in CSI Lawyer, the ‘Check status in Due AML’ function was selected for a customer identification event which already had the ‘Completed’ status in Due, the software incorrectly indicated that the current identification date was in the future.
• When M-Files was integrated to CSI Lawyer where several matters were first protected per user group with the Permissions button, and then user group members were either added or removed, updating the permissions in M-Files had to be confirmed with the OK button for each matter.
• When a plugin changing row data was in use, running it did not check whether the user wanted to save the unsaved changes made in the window.