PDF Download Feature

Overview

This page introduces the PDF Download feature in Case Management, along with the configuration steps for enabling it for clients.

Prerequisites

• HV Central Config GitHub repository access.

Purpose & use case

Clients can download a PDF of an application and store it for use cases like:

• Auditing
• Debugging

Who is this document for?

• Support teams
• SA/IE teams
• Reviewers

Feature overview

Users can now download a PDF version of any application or transaction directly from the Case Management dashboard. This provides an easy way to store, share, or audit application details.

Where the Download button appears

A new Download button is available on the top action bar of the application page, next to existing actions like Copy Link and navigation controls.

TODO

Screenshot: Application page top action bar highlighting the new Download button. (Pending migration from Notion.)

How the download works

When the user clicks the Download button:

1. A browser-native Print to PDF popup appears.
2. The default destination is set to Save as PDF.
3. The user clicks Save, and the PDF is downloaded.

TODO

Screenshot: Browser Print-to-PDF dialog after clicking Download. (Pending migration from Notion.)

Feature availability (feature flag)

This feature is not enabled by default. It is controlled by a feature flag inside Case Management.

The feature is free to enable — support teams and SA/IEs can enable it for any client.

How to enable the feature

Follow these steps to enable PDF download for a specific client.

1. Open the HV Central Config GitHub repository

Go to audit-portal/prod/client-configurations.

2. Create or update a client config file

For clients with no existing configuration file:

1. Create a new file named <client-id>.json (e.g., abc123.json).

2. Add:

   {
     "featureFlagConfig": {
       "application-details/download-button": {
         "default": true
       }
     }
   }

For clients with an existing configuration file:

Open the client configuration file and:

1. If featureFlagConfig key exists, add:

   "application-details/download-button": {
     "default": true
   }

2. If featureFlagConfig key does not exist, add:

   "featureFlagConfig": {
     "application-details/download-button": {
       "default": true
     }
   }

3. Raise a merge request

Raise an MR with the updated config and have it reviewed and approved by peers.

4. Sync to S3

Once merged, the configuration syncs to our S3 buckets.

tip

The feature will be live for the client within ~15 minutes of merge.