Displaying Workflow Inputs on Applications Table

Overview

This guide explains how to store workflow inputs corresponding to an application on the Applications tab of the HVOne dashboard.

Who is this for? SA/IE teams.

When should this be used?

Storing inputs to be displayed on the applications table
Storing inputs to be added to the CSV report downloaded from the applications tab

Update the client configuration file to define how inputs should be stored and displayed.

Clone the HV Central Config GitHub repository.
Navigate to buckets/hv-central-config/client-configurations/${appId}.json.
- If there's no existing file, create a new one.
- Replace ${appId}.json with the App ID for which you want to configure storing inputs.
Raise an MR enabling the configuration:

For existing configurations, add the inputsConfig key to the existing configuration:
```
{
  // ...existing configurations
  "inputsConfig": {
    "shouldStore": "yes"
  }
}
```
For new configurations, add the following to the JSON file:
```
{
  "inputsConfig": {
    "shouldStore": "yes"
  }
}
```

The backend receives the inputs sent to the SDK in the startTransaction API call.
The backend stores inputs in two formats:
- Encrypted — used later to display the inputs on case management applications table or CSV reports.
- Hashed — used to search on the values sent in the inputs. Values are lowercased before hashing.
  - Only full searches are allowed. Example: if the value is Karnataka, searching kar will not return results but karnataka will.
  - Search is case insensitive: karnataka, Karnataka, KaRnaTaKA all return the corresponding results.

PII Considerations

Since this is opt-in, we only store inputs for clients who want it.
Data is stored encrypted & hashed in our database.
Our database is located in the INDIA region only. For other-region clients, their encrypted data will be stored in INDIA.

Q: Do we store PII in raw plain text? A: No.

Q: Where is the data stored? A: In our database, located in INDIA.