We’ll publish today a new CSI Lawyer 12.1 update package. The version fixes the software defects reported by customers.

General

• When the note was in read-only mode (the user did not have permission to modify it or the database in a “history” mode), attachments could not be opened or downloaded.

Transaction

• The transaction change history did not work correctly when the transaction status was changed between Billable and Non-billable.
• When a transaction was created from a work time entry, the manually selected transaction type on the work time entry was not applied if the user had a default transaction type defined in the parameters.
• When a transaction was created from a work time entry and the billable hours were manually changed before the first save, the transaction’s billable hours were incorrectly updated to match the duration of the work time entry.
• When a work time entry was created via the calendar and an internal transaction was generated from it, the value of the transaction’s “Billable hours” field was updated to match the duration of the work time entry, even though the value should have been 0 (zero).
• When a transaction was created from a work time entry via the work time entry window and a transaction type with the “Bypass other pricing” option was selected, the software incorrectly set both billable hours and worked hours to zero. If the entry was created in the calendar by dragging a matter and the same transaction type onto the work time entry, the duration of the work time entry was correctly transferred to both worked and billable hours.

Invoice material

• Finvoice 3.0 caused issues in the invoice data if the computer’s number formatting (decimal and thousand separators) was not set Finnish.
• In certain situations, advance payments were calculated incorrectly in the Finvoice 3.0 data because canceled advance payment adjustments were not included as negative amounts in the “InvoicePaidAmount” element.

Customer funds

• In a specific situation, using the “Use as template” function on a customer funds transaction caused the transaction to appear under two different customers, one being a company and the other a private person.

Settings

• In the User window’s User Groups list, it was possible to remove multiple groups at once using the Delete key, even though the ribbon’s Delete action was disabled. After the fix, user groups can no longer be mass-deleted using the Delete key either.
• The record_guid of the default transaction type set in the business unit parameters was saved to the transaction in the database, even though the transaction type was not enabled in the system-level parameters.

Integrations

• In the cost center transfer of the Fennoa bookkeeping integration, the existence of a cost center was incorrectly checked based on the cost center name instead of the cost center ID.