STP Input Management

Input Management is operated as a cloud service. Updates are rolled out on an ongoing basis – there is no version that you need to install or update yourself.

For integration with existing law firm or customer infrastructure, on-premise components continue to be used to exchange documents, emails, and master data with the cloud (e.g., STP Document Collector, STP E-Mail Collector, STP LEXolution Connect, STP OnPremise Connector, STP winsolvenz.p4 FLOW Connector). These release notes summarize the changes per release date and indicate when one of these on-premise components needs to be updated.

Please note: If a release requires action on your part (e.g., updating an on-premise component such as DocumentCollector or FLOW Connector), this is indicated in the respective entry under "Please note."

On this page: New Features · Bug Fixes

New and Enhanced Features

Release – October 29, 2026

LEX.connect 26.10.15.1: new storage location for DMS master data

Starting with version 26.10.15.1, LEX.connect transfers DMS master data (system definition, collectors, schemas, and case file registers) to a new storage location in Input Management. The previous storage location (MetaDataService) will be decommissioned in the near future. Nothing changes for users: the features and operation of LEX.connect remain the same, and master data will continue to be transferred automatically as before. (124715)

Please note: Updating LEX.connect to version 26.10.15.1 is required. Older versions will continue to use the previous storage location and will no longer function as expected once it is decommissioned. Please install the update before the MetaDataService is shut down. It can be installed as a standard LEX.connect update; no configuration changes are necessary.

Faster detection of e-invoices (XInvoice)

The processing of e-invoices has been technically optimized. Previously, every XML file was sent to a Documents (Cloud) service that generates PDF files from e-invoices. Input Management now checks upfront whether the XML file is actually an e-invoice and only calls the service for genuine e-invoices. Unnecessary calls are eliminated, resulting in faster processing. (82268)

Sample upload for classifications: experimental methods removed

There were previously four ways to upload sample documents to a classification class, three of which were explicitly marked as experimental. These three have been removed. The recommended standard method remains unchanged. (128825)

Please note: This only affects direct use of the interface as well as the SDK and CLI. No action is required when working within the Input Management interface.

What is being removed?

• On the service side: api-version=2 and api-version=3 of the endpoint POST api/tenants/{tenantId}/pipelines/{pipelineId}/classes/{classId}/examples, as well as the tus upload endpoint POST /api/uploads/class-examples-tus1. Since api-version=3 had no additional endpoint, the Swagger document v3 will no longer be generated. The v1 and v2 documents remain available.
• In the SDK and CLI (STP.IM.Service.Client version 7.1.0 and later): the methods AddClassExampleStreamedV2, AddClassExampleStreamedV3, and AddClassExampleTus; the flags --stream2, --stream3, and --streamTus of the CLI command add-examples; and the setting IMClientOptions.AccessTokenProvider, which was used exclusively for the tus upload.

What remains?

The standard method AddClassExample or POST .../examples?api-version=1 with chunked upload is unchanged and is now the only supported method. It was already the default in the CLI; the removed flags had to be explicitly set.

What do you need to do?

• If using the SDK or CLI: update to STP.IM.Service.Client version 7.1.0 or later. If you were using any of the removed methods or flags, switch to AddClassExample or to calling without any flags.
• If using the HTTP interface directly: use api-version=1 of the .../examples endpoint. Calls with api-version=2 or api-version=3, as well as calls to /api/uploads/class-examples-tus1, are no longer supported.

Software component updates

Following the update of Input Management to .NET 10, the software components used by Input Management (including Aspose) have also been comprehensively updated to the latest versions. (127437)

Bug Fixes

Release – October 29, 2026

• Issue (ZD 167781): Large documents (e.g., 160 pages or more) would get stuck during page image generation and were moved to failed documents after approximately 3 hours. This issue has been resolved. (115293)
• Issue (ZD 132199): Digitally signed PDF files lost their signature when imported via a scan folder with batch processing in STP Document Collector, even when the document did not need to be split. Such documents are now uploaded without modification, preserving the signature. This issue has been resolved. (111421)

Please note: This fix is included in the STP Document Collector. Please update the Document Collector to the current version 26.10.16.2. For more details, see the FAQ under "Is the digital signature of a PDF document preserved when uploading via the Document Collector?"

Release – August 3, 2026

• Issue (ZD 187469): An increased number of faulty documents were being generated. The cause was an error in the font size (FontSize) calculation. This issue has been resolved. (124830)

Release – July 29, 2026

• Issue (ZD 185819): Blank page detection during the incoming mail process in Input Management stopped working. The cause was a missing Aspose.Imaging license. This issue has been resolved. (23802)