Xerox® DocuShare® 8.0 - Release Notes

What's New in this Release

Content Assistant for Summarization with Advanced-AI

Users can now instantly generate concise, AI-powered summaries of lengthy documents directly within DocuShare. these summaries are automatically saved to the document’s summary field, making them easy to reference and ideal for downstream use.

Key Features:

Smart Summarization: Extracts only the most important information from lengthy documents using advanced AI models.
Multi-language Summarization Output: Choose the number of sentences (1–10) and the output language (supports EPFIGS: English, Portuguese, French, Italian, German, Spanish).
Flexible Access: Summarization can be triggered:
- On-demand via the UI (document-by-document)
- Automatically via content rules

NOTE: this feature requires a Content Assistant license to be purchased and configured, as well as enough Content Assistant Normalized Page Packs to cover expected usage.

Content Assistant for Data Extraction with Advanced-AI

Users can now leverage advanced AI to automatically extract structured data from a wide range of document types, eliminating the need for manual data entry. this streamlines workflows and ensures faster, more accurate data capture.

Data can be extracted using Content Rules from:

Scanned documents
Typed and handwritten text
Images and scanned pictures
Emails and other digitized sources

Key Features:

Automated via Content Rules: Set up rules to trigger extraction workflows without user intervention
Fuzzy Matching: Accurately identifies data even when formats or spellings vary.
Multilingual Support: Works across EPFIGS languages (English, Portuguese, French, Italian, German, Spanish).

NOTE: this feature requires a Content Assistant license to be purchased and configured, as well as enough Content Assistant Normalized Page Packs to cover expected usage.

Xerox Intelligent Document Platform (IDP) Support

IDP is part of Xerox’s Capture and Content Services, designed to automate and streamline the processing of both physical and digital documents. DocuShare supports content intake from IDP via a new Custom Intake Module (CIM).

Content Assistant for Search – with Semantic Search

DocuShare now features Semantic Search, enabling users to find content based on meaning and context rather than exact keywords. this enhancement significantly improves search accuracy and efficiency across documents and data. We call this powerful new capability ‘Content Assistant for Search’.
Users can now ask complex, natural language questions across multiple documents they have access to in DocuShare.

Example Content Assistant Searches include:

“Which contracts from HealthCare providers have unlimited liability?”
“Which publishing contracts grant digital or audio rights?”
“Which contracts grant rights to publish in Spanish?”
“Which contracts before January 1, 2000, grant digital rights?”

Key Features:

Contextual Q&A: Ask follow-up questions with retained context.
Filtered Results: Only documents that the user has access to are searched.
Relevance-First: Results are ranked by relevance; irrelevant documents are excluded.
Date Filtering: Use natural language date filters like “before January 1, 2000.”
Fast Responses: Answers returned in seconds.
Document traceability: View which documents were used to generate the answer.

NOTE: this feature requires a Content Assistant license to be purchased and configured, as well as enough Content Assistant Normalized Page Packs to cover expected usage. Additionally, it can only be configured for systems that use PostgreSQL as their database.

Concurrent User Licensing

Starting with DocuShare 8.0 and in all future versions, organizations can take advantage of a concurrent user licensing model in addition to the current named user licensing model.

When a system is running under the concurrent user licensing model:

Licenses are still by user type (CPX, DS, Read Only) as they are for named users
Any number of users can be registered for each user type
At any given time, up to N users per type (based on your license count for that type) can be logged in concurrently.
- For example, if you have 6 CPX, 2 DS, and 100 Read Only licenses, those are the maximum concurrent logins allowed for each respective type.
Login restrictions are enforced per user type. If the concurrent limit for one type is reached (e.g., DS), users of that type will be prompted to wait. However, users of other types (e.g., Read Only) can still log in if their type-specific limit has not been reached.

View and Edit Office Documents

the Office Connector viewer is available for viewing and editing Office documents in DocuShare Online installations (formerly known as DocuShare Private Cloud/DSPC). (this capability will be available for DocuShare On-Premises in a future release.) this feature requires administrator configuration before it can be used. Supported document types will have "Open in Office Viewer" or "Edit in Office Viewer" actions to open the document in the Office Connector viewer. For DocuShare Online (formerly known as DSPC) users with the Prizmdocs add-on enabled, these options will appear alongside the existing Document Viewer options, enhancing the document management experience. Integrating the Office Connector viewer enables seamless and efficient document viewing and editing, allowing users to work with various document types while ensuring compatibility and ease of use.

Supported Document Types by Office Connector:

Text Documents: doc, docx, docm, dot, dotm, dotx, epub, fb2, fodt, htm, html, mht, mhtml, odt, ott, rtf, stw, sxw, txt, wps, wpt
Spreadsheets: text/csv, fods, ods, ots, sxc, xls, xlsb, xlsm, xlsx, xlt, xltm, xltx
Presentations: fodp, odp, otp, pot, ppt, potm, potx, ppsm, ppsx, pptm, pptx, sxi
Other Formats: djvu, oxps, pdf

Additional Content Rule Actions

Users can now choose to select Assign Routing Data and Create Advanced Routing Task as a content rule action.

Assign Routing Data: Provides a mechanism to copy information from routing events into the properties of the associated document.
Create Advanced Routing Task: Provides a mechanism for creating various types of routing workflows that are typically created manually using routing slips.

NOTE: these actions were previously provided to some customers via a custom package. Content rules created using earlier versions of these actions may not function after an upgrade and must be recreated using the new content rule actions instead.

Auto Complete Fields

Administrators now have powerful new controls to configure AutoComplete behavior for class fields directly from the Object Properties interface.

Feature Highlights:

AutoComplete Toggle: When editing any field in a class, Administrators can now enable or disable AutoComplete functionality.
Custom table Integration: Once AutoComplete is enabled, selecting a custom table from existing system tables becomes mandatory.
Column Selection: After choosing a table, Administrators must select one or more columns to define the data source.
Label Configuration: Build user-friendly labels by selecting multiple columns and specifying a delimiter to separate them./li>
Where Clause Support: Optionally define a custom WHERE clause to filter the AutoComplete results dynamically.
Improved Admin Experience:
- Streamlined configuration process for dynamic field suggestions
- Enhanced flexibility and control over how AutoComplete values are sourced and displayed

Routing Task Improvements

the My Tasks list now appears directly on the main page for faster access and a cleaner experience. Instantly see all your pending tasks, sorted by Date (latest first)—so you never miss what’s most urgent. Not the view you want, you can change the list filter to view Tasks assigned to you, Tasks assigned by you, or deleted tasks right from the list. You can change the sort by any of the columns that are presented simply by clicking on any column section. Click to view any task’s details, and you can navigate through all of the tasks, view and update document properties, and approve, reject, or comment on the task from there!

SMTP OAuth 2.0 authentication with Microsoft Office 365 Support

DocuShare now supports SMTP OAuth 2.0 authentication with Microsoft Office 365, enhancing email security and compliance. this update enables organizations to configure DocuShare to send system-generated emails using OAuth-based authentication via Microsoft Entra ID and Exchange Online. this feature is ideal for enterprise environments requiring modern authentication standards and tighter security controls.

Drag and Drop with Folder Hierarchy

Users can now drag and drop files while preserving the folder hierarchy, making file organization more intuitive and efficient. Note: Empty folders will not be created. the drag-and-drop functionality with folder hierarchy simplifies file management, saving users time and effort.

Repository Log Files Formats

Users can now choose to output Repository Log Files in JSON or CSV format, providing flexibility in managing and analyzing their data. the ability to choose between JSON and CSV formats for Repository Log Files allows users to tailor their data output to their specific needs.

System Requirements

Upgrade from earlier versions of DocuShare are supported as follows:

DS 7.0 update1p3 to DS 7.7p1 to 8.0
DS 7.5 + DS7.5p2 to DS 7.7p1 to 8.0
DS 7.6 + DS 7.6 p6 to DS 8.0
DS 7.7.p1 to DS 8.0

OPERATING SYSTEMS

Windows Server 2019, 2022, 2025
RedHat 8, 9
Ubuntu 22.04
Solaris 10.x is not supported currently.

Minimum RAM required to utilized Content Assistant features: 16 GB

WEB

Tomcat 9.0.106
Web Server
- Apache 2.4.x
- IIS 10

FILES

Databases
- Microsoft SQL server 2022, 2019
- Microsoft SQL Server 2022 Express Edition
- PostgreSQL 13, 15, 16, 17
- Oracle 19c, 21c, 23ai

WEB BROWSER SUPPORT

Google Chrome (latest)
Microsoft Edge-Chromium (latest)
Safari (latest)

LICENSING

A new license is needed for DocuShare 8.0.
DocuShare supplies a 30-day grace period to apply the new license after the upgrade.

Installation Notes

DOCUMENT VIEWER

For new Document Viewer installation, PrizmDoc 13.x runs the client and the server on the same box.
For upgrades with Document Viewer installed, PrizmDoc will continue to run the client on the DocuShare server and the PrizmDoc 12.x on another server.
For upgrades without Document viewer, PrizmDoc 13.x runs the client and the server on the same box.

SOLR

Currently, we do not support running multiple DocuShare instances on a single VM with Solr.
the Solr engine is started automatically after DocuShare 8.0 Installation (both Linux and Windows). However, if Linux machine is restarted, the Solr engine must be started manually before starting DocuShare
Upgrades from 7.6p6 and 7.7p1 will require reindexing as the version of Solr has been updated
Only a net new install will provide the Solr engine. Upgrade from DocuShare 7.0 IDOL Service will keep IDOL engine. Also, upgrade from DocuShare 7.5 that is still running IDOL server will keep IDOL engine.

Amazon Corretto

Updated from version 11 to 21 for improved security and long-term support.

Additional Notes

A migration/upgrade path exists to move from IDOL to Solr search engine (KeyView/IDOL to Tika/Solr). Please get in touch with support for more information.

Bug Fixes in this Release

AR Number	SPAR Number	Description
50372	2517	Html content should now download from DocuShare without issue.
59066	4614	DBs using native French version that need a timestamp format differently from en-US prevents installation, DocuShare load initial object's creation data can't fill in that collate.
44952	1143	Addressed CVE-2024-3566 which is a command injection vulnerability that affects Windows applications that indirectly depend on the CreateProcess function.
51754	3217	When an HTML file is uploaded to DocuShare and then viewed, the formatting of the HTML file is removed.
16340	?	When configuring the Multiselect view, in the Edit tab, if no property is chosen for a class, there will be an error displayed when using the Multiselect view functionality.
55455	4062	The version list will be sorted by version number and not date/timestamp. This way any versions with the same date/timestamp will be in the expected order.
46641	1713	When creating a new content rule and set the property conditions to use the "Is Not Empty" condition. the content rule will now trigger only when the metadata is not empty.
43520	839	CKEditor configuration updated to turn on basicEntities so that the HTML tags can be used in wiki pages.
53246	3405	Settings can now be configured as expected on the Management Home < Services and Components < WebDAV settings screen.
27933	2084995 (258)	When there is no Abstract to display, the value will be blank.
42749	528	Entering return in the quick search box will now execute the search.
45860	1404	SAML configuration will be retained during upgrade from 7.6 or 7.7.
45208	806	PDF File with no extension should now open in the web interface.
55550	4094	Routing slip setup not longer includes inactive users.
51648	3150	Acecss Logs will now honor the access log file size and the access log rolling index settings.
42563	ZD502	Subsequent searches will not remember the documents checked in previous searches.
43190	692	DSServer#getLastSchemaChangeTime() returns correct value now.
49079	2140	CSV Export from Quick Search results should now be correct for Custom and Standard Objects.

Known Issues

AR Number	Description	Work Around
40886	Values for mapped DocuSign properties within Basic eSign Settings and Template Profiles Administration pages that exceed the length of the mapped DocuShare property will not be returned after signing is complete.
	Using SAML override is recommended to be used on a DocuShare only account. It should not be used with an account that is linked to the Identify Provider.
35909	When joining a federation, you may experience the following error: Sorry. Your request could not be processed. 1136: This federation member has failed to respond and will not be touched for a configured amount of time. If that occurs, it is because of a port blockage for connection. You will need to create inbound and/or outbound rules in the firewall that will allow the port to connect the two servers.
36234	When creating a content rule, you are allowed to create actions that without filling in all the mandatory fields, because the current UI framework cannot handle mandatory validation and still allow the back button to work. This change is significant and current direction to the user is - if you don't fill in the fields correctly - regardless of mandatory status - the action will not work. So the user should take care to fill everything out correctly.
50588	SOLR Intermittently fails to restart after Daily backup routine is completed.	Customers experiencing this issue should use the associated Windows Powershell script: start_solr.ps1 [1] put start_solr.ps1 into D:\Xerox\Docushare\bin folder [2] modify their daily batch file, replace line net start docushare-solr to PowerShell.exe -ExecutionPolicy Bypass -File "D:\Xerox\Docushare\bin\start_solr.ps1" This start_solr.ps1 will try to start solr service, then, check if it is healthy, if not, it will try to stop solr service and restart it again (max try 5 times), for every retry "n", it will wait more time (120 + n*30 seconds more) to allow solr have enough time to start.
55747	** Impacts DS Online Only ** PDF Editing is a new feature of the service used for the Office Connector. When "strict" co-editing mode is enabled, the collaboration tab is not shown as expected. This has been reported to the application team. As soon as a fix is available, our instance will be upgraded, and this issue will be resolved for a;ll customers.
56889	Not all strings are currently translated within the Office Connector. This will be corrected in a future release.
58879	When attempting to index documents greater than or equal to 500MB using the Content Assistant fails with the default settings. The log files contain the following error: ERROR - Unexpected error in worker thread, continuing: Java heap space	Increasing the memory allocation from -Xmx512m to -Xmx3072m in the monitor.xml file will resolve the issue.
59596	this setting cannot be used with SAML
59743	The Content Assistant Search does not support Japanese.
59774	You are unable to remove the index on a document attached to a discussion topic when using the Remove Content Assistant Index using "Selected Collections and All Levels of Content" option. To remove the index on a document attached to a discussion topic you must go to the document itself and use the "Remove Content Assistant Index" option.
59842	Disabling Content Assistant does not prevent / hide the Content Assistant Content Rule actions. This allows the content rules to be available for troubleshooting even if the Content Assistant was disabled. Note that Other UI actions are hidden when Content Assistant is disabled.
60033	In order to improve the usage of Routing Tasks for the majority case, some action buttons were purposefully left off. This is specifically the case for the "Do Later" buttons. You can simply use the Next button in the page navigation to move to the next item if you wish to review that task "later". For other functionality that you might need for your workflow, you can use the Document > Properties > Routing menu option to view a more complete view.
60632	Japanese is not a support language for Content Assistant in this release. This functionality will be added in a subsequent release.
61156	The Generate Report page becomes unresponsive or fails to respond when performing a Content Assistant Search if it was launched from the Content Assistant Search Results page. Note: This issue does not occur when the Generate Report is launched from a regular collection view. In that case, Content Assistant Search works as expected within the report page.
61214	Some response messages for the Content Assistant Search are untranslated. These will be translated in future releases.
61143	When configuring the subscription using dsemailservice.bat/.sh with smtp.sendgrid.net, the Subscription type is set to SMTP-TLS (as expected) in the config output. However, after starting DS and checking the Subscription page in the DS Admin UI, the Subscription type appears as SMTP only. The setting is set correctly. This is a display only issue that will be fixed in a subsequent release,

Additional Information and Support

Click here for any updates to this document.

DocuShare web site

Knowledge Base