CSI Lawyer 11.0 update package 19.4.23

Today we’ll release a new update package for CSI Lawyer 11.0. Besides, the update package also brings improvements for the Due integration and enables creation of preliminary invoices from selected transactions in the main/sub-matter structure. Of these improvements we’ll publish a separate description.

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

• A parent company could not be deactivated, and the software indicated that the discount table prevented deactivation, even though the customer did not even have a discount table. 
• When a new matter request or matter was saved, the software added an identification event for the customer, although the activation date of the identification functionality was set for the future. 
• When the matter payer already had an identification event and, in the Parties folder, its payer role was first removed and then returned, the software incorrectly created a new identification event for the same payer. 
• When in a customer identification event, a future date was entered in the ‘Completed On’ field, the software did not warn about it, but saved the information as usual. After the correction, a notification will be displayed to the user.
• When customer identification was in use and a new matter was being created for a private person, a trial to save the matter resulted as an error message and the saving failed. 
• When a new customer fund transaction was added to a matter by selecting the New button, the Customer field in the customer fund transaction window was empty and the Look Up Records window listed by default the user’s own corporate customers and instead of the matter parties. 
• If several main matters were found with the same subject, they had sub-matters to be invoiced through the main matter, and the sub-matters had transactions, the ‘Billable Matters until Today’ viewed listed all these main and sub-matters without grouping them. 
• In the Budgeted Matters view, the columns displaying budgeted hours were lacking proper column titles. 
• When a matter had sub-matters with expenses and transactions, the main matter’s views ‘Open Expenses by Matter’ and ‘Open Transactions by Matter’ did not enable changing the value in the Status filter but the list always displayed open expenses or transactions only. 
• The ‘Open Transactions’ and ‘Open Expenses’ views automatically had a status filter ‘Open’ but it was possible to select a value in the Status filter after which the software displayed an empty list of transactions or expenses. After the correction the Status filter is disabled. 
• Although a preliminary invoice still had status ‘Open’, it was no longer possible to include transactions into a subscription.  
• In the Expense window, there was an unnecessary empty field. 
• When a foreign currency matter had the general expense in use and foreign currency was allowed for transactions but not for expenses, previewing the preliminary invoice in euro displayed the expense amounts incorrectly. 
• It was possible to add entirely new users in the Reviewers folder in the preliminary invoice window and the Review Steps folder in the matter window.  
• When a preliminary invoice was not yet approved, a discount table added for the payer after the preliminary invoice was created overrode the discount percent defined earlier for the payer. Thus, after approving the preliminary invoice, the invoice had a discount based on the discount table. From now on, a discount table is ignored if it is added for a payer only after a preliminary invoice has been created.  
• When previewing the invoice with the default invoice template in either English or Lithuanian, the VAT number field was too narrow, so the number continued to the next line making the invoice look unprofessional. 
• When having the main/sub-matter structure in use and rejecting transactions or expenses from the main preliminary invoice, the start date of its invoicing period was incorrectly changed to 31.12.9999.
• When a main matter had a sub-matter which was invoiced through the main matter: If both matters had expenses and transactions and, in the main preliminary invoice, all the transactions were first marked as reviewed after which the expenses were marked as reviewed, the sub preliminary invoice did not get the status ‘Reviewed’.
• When a new expense type and a translation for it were added, and then the expense type was added e.g. to the ‘Expense type’ parameter of the general expense, a new transaction added to a matter and – without actually creating an invoice – its invoice previewed in the translation language of the expense type, the general expense row was displayed as empty. 
• In the invoice specification preview, the expense was always displayed using the user interface language although a foreign language had been set for the matter and for previewing the invoice and, for the expense type, there was a translation in the language in question. 
• When the text of the invoicing memo was edited and then the view was refreshed without saving the changes, the software did not check if the user wanted to save the changes nor did it update the memo.
• If an invoicing memo had been added either for a matter or for a preliminary invoice to replace the invoice specification,  the text removed from the Invoicing memo tab was still displayed in the invoice preview and on the actual invoice.  
• When a main matter had a sub-matter which was invoiced through the main matter, both the matters had expenses and transactions and, in the main matter, an invoice was being created to the selected date, the software gave an error and the invoice creation failed. 
• When a payment was opened and, in its Adjustments folder, the New button was selected, the “Look for” window for searching the desired invoice displayed irrelevant buttons as active.
• The Permanent Insider List report was lacking the contact information for persons belonging to the insider group. 
• In the Fennoa integration, if the matter dimension was incorrectly defined in letters and not as a number, errors occurred due to the missing dimension id were not saved in the integration log. 
• When the Netvisor integration was in use and an invoice was cancelled in CSI Lawyer, the credit invoice was transferred to Netvisor. When it was manually adjusted to the actual invoice in Netvisor, the system incorrectly created a payment which was transferred to CSI Lawyer and left hanging in the Unadjusted Payments list. 
• When power users already had navigation permissions in the settings and then the prospect or opportunity functionality was activated in the software parameters, the Sales and Marketing folders were not displayed in the navigation permission window for power users but the navigation permissions needed to be reset.  
• When the user type of a power user was changed to a normal user, a reminder template which already had been unpublished got published again in case it had been created by the power user in question who had first published it for all user types and then unpublished it. 
• If a power user had set the user’s password to be changed by selecting ‘Force password change when logging in the next time’, the user was still able to set the old password also as the new password. 
• Although the power user had set a user’s password to be changed when logging in the next time, the user was able to log in without changing the password by selecting the Cancel button in the Password Change window.
• The software enabled creating multiple customization tables with the same name leading to errors. If a user had first created a customization table for a corporate customer after which a customization table with the same name was created for a private person, when saving a private person the software tried and add a row to the customization table of corporate customers. 
• When a new target budget was added to the software, its status value was not saved in the database.  A trial to create a new email template resulted as an error and the data explorer parameters were not displayed.