| Audience: DocuShare 8.0 administrators |
Xerox® DocuShare® 8.0
Patch 4. Release notes.
© 2026 Xerox Corporation. All rights reserved. Xerox® and DocuShare® are trademarks of XRX Brandco LLC in the United States and/or other countries.
DocuShare 8.0 Patch 4 (ds800p4) is a cumulative patch for DocuShare 8.0. It includes the field issue fixes listed below, a range of security fixes, and an upgrade of the bundled Solr search engine to version 9.10.1. No configuration change is required once this patch is installed.
This patch also addresses Google's removal of XSLT 1.0 support from Chrome. On Google's published schedule, Chrome currently shows deprecation warnings, XSLT stops working for standard Chrome users in Chrome 158 (November 2026), and the remaining enterprise policy and origin trial options are withdrawn in Chrome 176 (August 2027); Mozilla and Apple have indicated that Firefox and Safari will follow. DocuShare relied on browser-native XSLT to render several pages, including Quick Search and the content rules pages, and those pages did not work when XSLT was disabled in the browser. This patch replaces the client-side XSLT transformation with a JavaScript bootstrap, so the affected pages continue to work in Chrome after XSLT support is withdrawn.
System Requirements
DocuShare 8.0 Patch 4 can only be installed on an existing DocuShare 8.0 system. See the DocuShare 8.0 release notes for the paths to get upgraded from other versions to 8.0. The remainder of the system requirements for DocuShare 8.0 Patch 4 are the same as the system requirements for DocuShare 8.0.
Before You Install
This patch upgrades the bundled Solr search engine to version 9.10.1 through an automated installation process. Whether a reindex is required depends on the patch level you are upgrading from:
1. If Patch 2 (ds800p2) was not previously installed, run dsindextool index_all after applying this patch to reindex your content.
2. If Patch 2 (ds800p2) was previously installed, no reindex is required.
3. If the PDF Forms add-on is installed, reinstall the PDF Forms add-on after applying this patch.
4. If you have not previously installed the DocuShare Tomcat 9.0.120 patch. You should do so. It can be installed before or after this patch.
Bug Fixes in this Release
| AR Number | SPAR Number | Description |
| 55662 | 4141 | In an approval workflow with more than one approver, a content rule using the (PS) Assign Routing Data action did not populate the fields for the second approver, and that approver's comments were not added. |
| 65238 | 6165 | Scanning from a Xerox ConnectKey device failed when SAML authentication was enabled on the DocuShare server. |
| 82184 | 7666 | In ConnectKey, the "Scan another document" link shown after a scan completed was not clickable, so a further scan could not be started from that page. |
| 83451 84665 | 8443 | Cutting, pasting or deleting documents and collections could stop responding, and the server had to be restarted to recover. This has been corrected. |
| Various security fixes. |
Known Issues
| AR Number | Description | Work Around |
| 85751 | On systems with Content Encryption enabled, documents added after Content Encryption was turned on may not be returned by content (full-text) searches. Property and metadata searches are not affected, and documents indexed before Content Encryption was enabled remain searchable, so the condition may not be immediately apparent. This affects systems upgraded from an earlier DocuShare release. New installations are not affected. | Add the content encryption library to the Index Server classpath: 1. Stop DocuShare. 2. In <DSHome>\config\Monitor.xml, locate the <Server> block whose <Name> is IndexServer, and append ;+DSH+\lib\cryptoContent.jar to the <StartJVMClassPath> element within that block. 3. Save the file and restart DocuShare. 4. Confirm the change took effect. The effective classpath is written to Monitor.log each time the JVM launches, and the dsix command line must now list cryptoContent.jar. 5. Only after step 4 is confirmed, re-index the affected content. The classpath change is not retroactive. |
| Do not re-index before step 4 is confirmed. Re-indexing while content is still unreadable re-adds the affected documents with metadata only, which removes the extracted text of documents that were previously searchable. |
Additional Information and Support
Click here for any updates to this document. The latest information regarding DocuShare can be found on the DocuShare web site. For information on a solution, search the Knowledge Base.
Comments
0 comments
Article is closed for comments.