Release Notes for Lexolution 9.3

With Lexolution 9.3, new features have been introduced, numerous improvements have been made, and known issues have been fixed. The highlights include:

  • Display Outlook (Exchange Online/MS365) calendars in Lexolution
  • VAT ID and tax number can be stored per location
  • New field for invoice code (BT-3 in the e-invoice)
  • New placeholders for invoice code, account holder, second signer, Secretariat 2, RVG version

The STP Lexolution Team wishes you continued success with Lexolution!

Important Notes for Updating to Version 9.3.72

  • Major releases, feature packs, and service packs are cumulative and always include the complete current version.

  • Lexolution 9.3.72 requires the Microsoft .NET Framework 4.8 on both server and client sides.

  • If not already installed, please install .NET Framework 4.8 in advance (e.g., during a scheduled maintenance window) on the Lexolution server and clients to ensure the Lexolution update runs smoothly and without interruption.

  • Lexolution 9.3.72 requires the Microsoft Visual C++ Redistributables 2015-2022 (x64 and x86) – 14.30.30704 on the client side. If a current Lexolution.DMS or winsolvenz.p4 installation is already present on the system, the C++ runtime is already installed.

  • If you are using the central STP User Management (UM), we recommend updating to version 1.7.506 and updating the STP common services to version 1.6.530 as well as updating the STP On Premise Connector to version 1.6.35. However, Lexolution 9.3.72 also works with older versions of STP User Management starting from version 1.5.

  • You can find downloads for .NET Framework 4.8, UM, and common services on our download page for Lexolution.

  • Lexolution 9.3.72 is approved for Windows 11, Windows Server 2022, Windows Server 2025, Office 2021, and Office 365.

  • The Lexolution server update (final step in setup with the Start Lexolution Server button) may take over 15 minutes when updating from a version older than 6.4, especially with large Lexolution databases containing millions of entries (times, expenses).

  • Lexolution 9.3.72 requires IKAROS 2022 or higher.

Lexolution.BI

  • Lexolution 9.3.72 requires Lexolution.BI 9.3

ADB Tool for Updating the Reporting Database

  • If you use the ADB Tool, it must also be updated to version 9.3.72 on the relevant server (usually the SQL server). Please use the new config from the zip package and adjust the settings accordingly (database connection, number of threads, port, tables to exclude).

Documents (Lexolution.DMS)

  • Starting with Lexolution.KMS 6.4.244, Lexolution.DMS is only used via the new interface. Note: The entry in the Lexolution server config is now equivalent to . No manual changes to the config are necessary.

Other Notes

  • Lexolution 9.3.72 is approved for Office 2024.

  • Lexolution 9.3.72 is approved for Windows Server 2025 (#95691)

  • New version 1.9.110 of STP Integration Services. An update is strongly recommended if you use Exchange Online/MS365.

  • Localizations for German, English, French, and Swiss (de, en, fr, de-ch) are included in the setups starting from Lexolution.KMS 6.3.81 and are installed automatically. If server-side localization is not desired (e.g., on an English app server with English error and info messages in Lexolution), the respective folder (e.g., en) can be removed from the app server.

  • With the rebranding from Lexolution.KMS to Lexolution in version 8.0.122, if you use the STP Updater, you need to adjust the directory in the STP Updater repository:

    • For updates with setup:
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Update\Lexolution Word AddIn
    • For individual file patches:
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Client -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution
      • C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution.KMS Word AddIn -> C:\ProgramData\STP AG\Updater\Repository\Patch\Lexolution Word AddIn

  • Support for Microsoft TLS (Transport Layer Security) versions 1.0/1.1 will end with the next version 9.4 of Lexolution.

    • Microsoft TLS is a security protocol used by Microsoft in its products and services. Starting with Lexolution version 9.4, only Microsoft TLS version 1.2 or higher will be supported.

Version History

  • 10/17/2025 Technical Release 9.3.66 (internal)
  • 11/04/2025 Technical Release 9.3.69 (internal)
  • 11/27/2025 Technical Release 9.3.72 (internal)
  • 12/09/2025 Launch

Changes in Version 9.3.72

Version 9.3.72 includes all changes from version 9.3.69 plus the issue fixes listed below.

Issue Fixes

  • The placeholders RA-Ort and RA2-Ort are empty (#105148)
    • Previous behavior
      • If the attorney's location (Signer dialog in the Word add-in) was different from the file's location, the placeholders RA-Ort and RA2-Ort were not filled.
    • New behavior
      • The placeholders RA-Ort and RA2-Ort are now filled even if the location is different.
  • Error with contact person for party (#105737)
    • Previous behavior
      • If a contact (organization, authority, person) was represented multiple times on the Representation tab by the same contact, and this contact was added as a contact person for the party in the file, a technical error message appeared.
    • New behavior
      • Contacts can now be added as contact persons for the party even if the contact represents the party multiple times.

Changes in Version 9.3.69

Version 9.3.69 includes all changes from version 9.3.66 plus the issue fixes listed below.

Issue Fixes

  • Conflict check does not stay on status “accepted” (#104170)
    • Previous behavior
      • If Lexolution was configured to automatically start a conflict check after a KFC-relevant change (see Administration > System > General Settings > Conflict Check section) and a KFC was manually performed and, for example, accepted or rejected within this time, the KFC would still be executed again and would revert to the status “Review required.”
    • New behavior
      • It now checks first if the KFC has a final status before it is queued for automatic execution after X minutes. This ensures that a KFC that has already been reviewed does not revert to “Review required.”
  • Incomplete conflict check for factual conflict with conflict keywords (#104294)
    • Previous behavior
      • If a conflict keyword with a description was added to a file in Lexolution, or if a description was changed for a conflict keyword, the search index for conflict keywords was not updated during this process, so a factual conflict based on conflict keywords was not detected. For files with conflict keywords created via the cloud (New Matter Intake), this problem did not occur.
    • New behavior
      • If a conflict keyword is added or changed in a file in Lexolution, the search index is updated so that the relevant factual conflicts are detected.

Changes in Version 9.3.66

Syncing Appointments between Lexolution and Exchange Online/MS365

  • Option to disable syncing appointments back to Lx (#95899)
    • In the STP.Idesk.Server.exe.config of the STP Integration Services, there is a new setting in the ExchangeSection. By setting DisablePushNotifications="true", you can disable subscriptions for push notifications. Syncing appointments back to Lexolution when using Exchange Online/MS365 should definitely be disabled using this setting.
    • In Lexolution 9.3, calendars from Outlook (Exchange Online/MS365) can be loaded and displayed (see below).# Syncing back from the cloud and complex firewall configurations are no longer necessary.
    • Syncing appointments, tasks, and deadlines from Lexolution to Outlook (Exchange OnPrem and Online/MS365) continues to work as usual.
  • OAuth2 authentication for Exchange Online/MS365 (#95919)

    • The Lexolution Server can now authenticate with Microsoft 365 using OAuth2.

    • To do this, add the following entries to STP.Kms.Server.exe.config and fill them with the values from Microsoft Entra:

      <add key="Ms365IsEnabled" value="true"></add>
<add key="Ms365TenantId" value=""></add>
<add key="Ms365ClientId" value=""></add>
<add key="Ms365ClientSecret" value=""></add>
<add key="Ms365IsConfidentialClient" value="true"></add>
  • Selecting which Exchange Online/MS365 calendars to display (#96141, #95920)
    • Through a dialog (Ribbon > Load Calendar) in the Appointments > Calendar view, you can now select which employees' Outlook calendars should be displayed.
    • Clicking Refresh pulls the data from the Exchange server for display. The Outlook appointments are only displayed and are no longer stored in Lexolution.
    • The employee must have the valid email address of the Outlook mailbox entered in the vCard communication data record in Lexolution and be linked to a Lexolution user.
  • Display of Outlook appointments with icon, body, and tooltip (#96253)
    • Entries from the selected Outlook calendars are marked with an Outlook icon and cannot be edited in the Lexolution calendar. The appointment displays the calendar (name or email of the calendar owner), location, tooltip, and other data directly from Outlook. For private appointments, only the data provided by the Exchange server is shown (e.g., subject and notes are empty).
  • Quick info for calendar entries from Outlook appointments (#96255)
    • Information for a selected Exchange calendar entry is shown in the quick info for Exchange appointments with the following fields:
      • Calendar: Email of the calendar owner
      • Private: Yes/No
      • Subject: Appointment subject
      • Date and time from and to
      • All day: Yes/No
      • Location:
      • Created by
      • Participants: Email addresses of participants
      • Note: Additional information

Invoices with Own VAT ID or Tax Number Depending on Location

  • E-invoice, own tax ID depending on location (#94091)
  • In Lexolution, you can enter a VAT ID and tax number in the Locations view.
  • When creating e-invoices, the data from the location is used if entered. If no value is entered, the system settings are used as before.
  • In the e-invoice, the VAT ID is shown in field BT-31 or the tax number in field BT-32.

New Field: Invoice Code (Invoice Type)

  • Selection in Invoice or E-Invoice to specify whether it is an invoice or credit note (#93501, #96588)
    • In the invoice draft/invoice views, there is a new selection field for invoice code with the following values:
      • Invoice (380)
      • Credit Note (381)
      • Self-billed Invoice (389) to ensure that invoices display valid values according to regulations.
    • In the e-invoice, the number is shown in the Invoice Type field (BT-3).
    • In the Lexolution Word Add-In, under Billing, there is a new bookmark for invoices: Invoice Code. The content of the bookmark matches the text in the selection field in the invoice (see above).

Bookmarks

  • New bookmark for RVG version (#89920)
    • In the Word Add-In, under Lexolution in the Billing section, there is a new bookmark for RVG Version. This can be used to include the RVG version used in the invoice.
  • Extension of bookmarks for bank details to include account holder (#102372)

    • Since October, as part of International Banking Services (IBS), the account holder is also checked for transfers. Therefore, it is necessary to include the account holder in bookmarks. The existing bookmarks for bank details have been extended to include the account holder field. The value from the account holder field in the bank details will be displayed in the bookmarks.

    • This extension applies to the following bookmarks in the Word Add-In:

      • Word tab
        • Location: Bank details,
        • Location: Customizable bank details
      • Lexolution tab
        • Location: Bank details
        • Invoice: Bank details
  • New bookmark “Payment > 0” (#93490)
    • In the Word Add-In, under Lexolution in the Billing section, there is a new bookmark “Invoice: Payment > 0”.
    • If the amount is > 0, the bookmark will be displayed.
    • This bookmark can be used to hide informational texts when no payment is expected.
    • By default, the following text is pre-filled: “Please transfer the invoice amount to our account by [due date].” The text can be changed. If needed, the due date and/or bank details can be inserted.
  • Extension of the “Second Signatory” selection dialog and additional bookmarks for Attorney 2 and Secretariat 2 (#89901)
    • In the Word Add-In, the “Second Signatory” dialog has been extended to include the selection for the assigned secretariat.
    • In the Word Add-In, under Word in the Employees section, the following new bookmarks are available.
    • Bookmarks for the second signatory:
      • RA2-Email
      • RA2-Fax
      • RA2-Abbreviation
      • RA2-City
      • RA2-Phone
    • Bookmarks for Secretariat 2:
      • Sekr2-Email
      • Sekr2-Fax
      • Sekr2-Abbreviation
      • Sekr2-Name
      • Sekr2-Phone
      • Sekr2-First Name

Lexolution.BI

  • Change to scenario for planned revenue / planned hours due to new data structure (#102902)
    A new feature has been implemented that allows you to explicitly name the scenarios stored in the planning tool in LEXolution.BI. Previously, the scenario was calculated from the import date. This now allows you to specifically address the scenario at a later time. The scenario is used for planned revenue as well as planned duration. To use the scenarios, the planning tool must be updated to the latest version.

  • Missing employees in file responsibility (#102950)

    • Previous behavior
      • A bug was fixed that caused file managers with multiple entries in the Lexolution history (location, FTE, status) to not be fully assigned to the records. The issue was that only the last valid employee was used for assignment, and previous entries were not tracked.
    • New behavior
      • The assignment of file managers now includes the full history of the employee, ensuring correct assignment to all their data such as hours and revenue, even for past records.

  • Error in allocations/transfers for split invoices (#102659)

    • Previous behavior
      • A bug was fixed that caused split invoices with multiple allocations, which fully covered the invoice amount, to not be written correctly to the cube. The issue was that the individual transfers were calculated as one, resulting in an incorrect distribution ratio.
    • New behavior
      • The allocation and transfer assignments are now recalculated for each transfer to ensure the correct distribution ratio.

Bug Fixes

  • File search does not work when the new file view is open in context (#101431)
    • Previous behavior
      • In the invoice draft, right-clicking in the context menu jumps to the corresponding file for the invoice draft. If a different file number (internal) is entered in the quick search and searched, the desired file is not found.
    • New behavior
      • After entering the above example, the desired file is found.
  • Acquisition distribution permission not working (#102717)
    • Previous behavior
      • The user has the permissions 10002 Files - read, 10003 Files - edit, 10004 Files - create new, but not the permission 50030 - Files Acquisition Distribution.
        The user can edit the acquisition distribution.
    • New behavior
      • If the user does not have the 50030 Files - Acquisition Distribution permission, they cannot edit the acquisition distribution.
  • LEDES file - tax per line - inaccuracies in invoice calculation (#94345)
    • Previous behavior
      • Tax is calculated per line.
        The total tax does not match the total tax of the invoice.
    • New behavior
      • The total tax of the invoice matches the total tax of the individual items.
        In the INVOICE_TAX_TOTAL column, the sum of LINE_ITEM_TAX_TOTAL is displayed.
        In the INVOICE_REPORTED_TAX_TOTAL column, the sum of the items is displayed.
------------------------------------------------------------------------------------------------------------------
This article has been automatically translated by an AI and may therefore contain errors.

Related to