AgriDex + Query resolver (consent artifact provided by consent manager dynamically)
Objective
To test the entire consent cycle including
- Farmer defined access to data fields
 - Creation of consent artifact based on farmer permission
 - Bank requesting access to farmer data (to auto-fill loan application form)
 - Resolution of query when compared to the Consent artifact
 - Final rendering of the data requested by bank on the application form
 
Demo setup

Screens involved
Farmer screen - To enable farmer to chose consent for all data field for credit use case
Bank screen - To enable bank to request data that will be filled up
CA screen - Screen to help anyone testing or demoing to view
- CA creation
 - CA call
 - CA and query resolution
 
Blocks of the demo
- Consent Manager
 - Query resolver
 - Database (a sample from KO to be used)
 - 3 UI screens
 
Steps and test cases
- Farmer - Selects fields for giving consent (Screen 1)
- Data
 - Field names with checkbox
- Name
 - Aadhar
 - Phone number
 - Marital status
 
 - Button to allow consent for selected fields
 - Button to revoke consent (for all fields)
 
 

- CA - Render CA on screen 2 to view 
- Test 1 - Is the CA correct (how can we check this? @CG)
 
 - Bank manager - Requests farmer data to fill form, screen to include
- Application form with the following
- Name
 - Aadhar
 - Phone number
 - Marital status
 
 - Request button to request for these 4 entries
 
 - Application form with the following
 - Bank Manager - The application form gets filled or not based on the consent artifact
 
