4.1.5 Beneficiary Manager Configuration Admin Panel

BR-CBF-4.1.5.1: Manage Form Fields

1. The system shall provide an administrative interface for managing form fields used in beneficiary applications.

2. This interface must allow administrators to create, edit, and delete form fields.

3. Each field must have configurable properties, including a unique field_name, a user-friendly display_label, a field_type (e.g., text, number, date, email), and a boolean flag for is_required.

4. The admin panel must prevent the creation of fields with duplicate field_names to ensure data integrity.

BR-CBF-4.1.5.2: Configure Document Types

1. The system shall provide a facility for administrators to define new document types that correspond to Verifiable Credentials (VCs).

2. This functionality must support the definition of a unique identifier and a descriptive name for each document type (e.g., AadhaarCard, IncomeCertificate, ProofOfAddress).

3. The system shall allow for the upload and association of a JSON schema with each document type. This schema will be used to validate the structure of the corresponding VCs and their data.

BR-CBF-4.1.5.3: Map Fields to Documents

1. The system shall provide a configuration panel to map form fields to specific document types and JSON paths.

2. This mapping will be the basis for automatically pre-populating a beneficiary's application form with data from their VCs.

3. The user interface must provide a visual, tree-based selector for navigating the JSON schema of a document type to help administrators select the correct VC field for mapping.

4. The system must perform validation to ensure that the field_type of the form field is compatible with the data type at the specified JSON path within the VC's schema.