Overview
The FileBound platform, version 9.0
will complete several planned deprecations of legacy components.
These updates focus on:
• Streamlining the product experience
• Improving performance and security
• Reducing technical debt to accelerate innovation
Below is a detailed outline of each deprecated feature, the rationale, and guidance for
migration.
1. Windows Viewer
What’s changing: The legacy Windows Viewer will be fully retired. No further updates, patches, or
enhancements will be provided.
Why:
To consolidate all viewing functionality under the Web Viewer, which has seen
significant performance, UX, and accessibility improvements since version 8.3.
Impact:
• Any entry points invoking the Windows Viewer are considered legacy and
unsupported.
• No further maintenance will occur.
Recommended actions:
• Transition all users to the Web Viewer.
• Update SOPs, user training, and scanning workflows.
• Rewrite any custom plugins for the Web Viewer.
Timeline:
Deprecation effective with FileBound 9.0 (Q1 2026).
2. Mastersheets
What’s changing: Mastersheets move to read-only mode in 9.0. Data remains viewable, but no edits or
new records can be created.
Why: To simplify data structures and focus on scalable indexing models.
Impact:
• Create/update operations will be disabled.
• Data will remain accessible for reference.
Recommended actions:
• Identify any areas referencing Mastersheets.
• Transition to Index Fields or Additional Fields (enhanced since 8.3).
• Adjust reporting and workflow dependencies.
Timeline: Effective with FileBound 9.0 (Q1 2026).
3. Vendors
What’s changing: The Vendors tab in Administration will be removed. Vendor records will no longer be
accessible through the interface.
Why: To streamline administrative configuration and retire an underutilized area.
Impact:
• Admin access to Vendors will be removed.
• Data is not automatically deleted but becomes inaccessible in-app.
Recommended actions:
• Backup or export vendor data.
• Update SOPs referencing the Admin tab.
• Use eForms, workflows, or integrations for vendor management going forward.
Timeline: Effective with FileBound 9.0 (Q1 2026).
4. Print Barcode Window
What’s changing: The standalone Print Barcode window will be removed.
Why: To consolidate barcode-related capabilities into Document Stencils, which support
barcode generation, stamping, and workflow integration.
Impact:
• The Print Barcode window will be unavailable.
• Barcode generation should now occur through Document Stencils or
capture tools.
Recommended actions:
• Update internal SOPs referencing barcode printing.
• Shift to Document Stencils for barcode generation.
Timeline: Effective with FileBound 9.0 (Q1 2026).
Upland Integration (Boomi)
What’s changing: Support for Upland Integration (also known as Boomi) will end. Existing processes will
continue to function but will no longer be supported or updated.
Why: To simplify the integration ecosystem and focus on direct APIs and modern
middleware approaches.
Impact:
• No new Boomi projects will be accepted or supported.
• Maintenance and technical support end with 9.0.
Recommended actions:
• Catalog any current Boomi integrations.
• Begin transitioning to FileBound REST APIs or other supported integration
methods.
• Plan migration prior to the full deprecation (expected post-9.0).
Timeline: Support ends with FileBound 9.0 (Q1 2026).
© 2025 Upland Software, Inc. All Rights Reserved V2025-11