Release Notes: Records Management Universal File Share Connector 6.3
Release Date: September 1st, 2026
Overview
Records Management Universal File Share Connector 6.3 includes focused updates that make file share processing faster, more reliable, and easier to manage. The release is designed to help teams scan large file share environments with fewer interruptions and less manual follow-up.
This release is part of the Records 6.3 release stream and supports on-premises file share scanning where organizations need to identify content that should be managed under records retention policies.
What’s New
· Improved large-scale performance: UFSC now handles larger file share environments more efficiently, helping crawls run faster and more consistently.
· Greater processing reliability: The connector is better able to keep moving when it encounters isolated access, network, or processing issues.
· Reduced administrative effort: Crawls are less likely to require manual restarts or repeated follow-up when temporary issues occur.
· Discover integration improvements: UFSC works more smoothly with Discover so file share content can be used more effectively in downstream workflows.
Key Benefits
· Improved operational efficiency: Teams can complete large crawls with fewer disruptions and less hands-on monitoring.
· Better resilience: Processing improvements help limit the impact of temporary errors, permission issues, or environmental interruptions.
· Stronger records coverage: File share content can be identified more consistently for records management and retention workflows.
· Better downstream usability: Discover integration updates make it easier to use UFSC results as part of broader information governance processes.
Features
|
Item |
Ticket # |
Description |
|
Records (UFSC): Improving large-scale performance |
113811 |
Improves UFSC performance and resilience for larger file share environments. |
|
Records (UFSC): Discover integration |
113931 |
Improves how UFSC works with Discover. |
Known Issues
Known issues are items found during release testing that are not fixed in this release. They are listed here so teams understand the possible impact and any recommended workaround.
|
Item |
Ticket# |
Description / Workaround |
|
Stale rows should be purged after the value set in the classification configuration file |
116994 |
Inconsistent behavior may occur if internal configuration values are changed after a crawl has already run. Workaround: Do not change rl.denial_corroboration_threshold after a crawl has been performed. |
|
Record properties are sent as strings without datetime kind information |
117374 |
Record properties are sent as strings without datetime kind information, which may affect environments running in UTC+n time zones. |
|
Reconciliation log level for crawl status entries |
117376 |
Some reconciliation messages may appear as higher-priority log entries even though they should be treated as debug-level messages. |