SR · BOOTv0.1 · 2026READY ●
SR
02.Case study · Document intelligence

Claim Shark DMS

Modernising a document workflow platform with in-browser PDF viewing, advanced search, text extraction and metadata analysis.

Project snapshot
Category
Document management
Project year
2024
Core stack
Angular 17 · TypeScript · RxJS · PDF.js · Node.js · REST APIs
01 / Context

A document workflow built for everyday use

Claim Shark DMS is a document workflow platform designed to make document-heavy work easier to navigate. Its capabilities include advanced search, in-browser PDF viewing, text extraction and metadata analysis.

The work included carrying a legacy Angular application forward through a major framework upgrade while keeping the core document workflows usable and maintainable.

02 / Challenges

Modernise without losing the workflow

01

Framework evolution

Move the application from Angular 10 to Angular 17 and address compatibility and maintainability across the upgrade.

02

Document handling

Keep document discovery, PDF viewing, extracted text and metadata useful within one workflow.

03

Reusable capability

Create a reusable document-viewer library that other parts of the organisation could use instead of rebuilding the same capability.

04

Responsive performance

Use application modernisation and server-side caching to improve responsiveness and reduce repeated backend work.

03 / Approach

A modern Angular foundation

01

Upgrade the application

Advance the legacy Angular 10 application to Angular 17, working through major-version changes and aligning dependencies with the updated framework.

02

Support document discovery

Bring advanced search, text extraction and metadata analysis together with in-browser PDF viewing to support document-focused tasks.

03

Reuse the viewer

Package document-viewing functionality into a reusable library to reduce repeated implementation work in downstream applications.

04

Improve backend efficiency

Use server-side caching where appropriate to reduce repeated processing and improve response performance.

04 / Reported outcomes

Impact beyond the upgrade

40%

Performance improvement

Reported improvement following the Angular 10 to Angular 17 upgrade.

50%

Lower server load

Reported server-load reduction from the caching strategy.

60%

Less downstream dev time

Reported reduction in downstream development time from the reusable viewer library.

Outcome figures are project-reported results from the supplied website content.

05 / Technology

Tools behind the workflow

Angular 17TypeScriptRxJSPDF.jsNode.jsREST APIsServer-side caching
Have a complex workflow?

Let's make your software work harder.

Discuss a document management system, business application or modernisation project with SR Technoware.