UI Specification
Registration Client UI Specifications
Overview
The registration UI forms are rendered using respective UI specification JSON. This is derived from the ID Schema defined by a country. Here, we will be discussing the properties used in the UI specification of the Registration Client.
In the Registration Client, currently, Registration Tasks(process) forms are configurable using the UI specifications.
Each process has multiple screens and each screen is rendered with one or more fields.
Process/ Task spec JSON template
{
"id": "<NEW/UPDATE/LOST/BIOMETRIC_CORRECTION process name as passed in the packet>",
//order in which the process is displayed on the registration client home screen
"order": 1,
"flow": "<NEW/UPDATE/LOST/CORRECTION>",
//Multi-lingual labels displayed based on the logged in language
"label": {
"eng": "Registration",
"ara": "تسجيل",
"fra": "Inscription"
},
//screen details - follows screen spec structure
"screens": [
{}
],
//caption displays on-hover content
"caption": {
"eng": "Registration",
"ara": "تسجيل",
"fra": "Inscription"
},
//icon is the symbol that appears before the process label
"icon": "registration.png",
"isActive": true,
//group names that should be by default selected during UDPATE UIN process
"autoSelectedGroups": [
""
]
}Screen spec JSON template
Field spec JSON template
Sample correction process SPEC: Biometric Correction
Enabling Handles Feature
Add the following in the properties section of IDSchema:
Example:
Settings spec JSON template
Last updated
Was this helpful?