UI specification helps us identify how the data in an ID attribute (attributes of an ID object) is going to be retrieved from the UI. The UI screens in registration client application and pre-registration application are rendered using their respective UI specification JSON. We have different UI Specifications for Registration Client & Pre-registration which is derived from the ID Schema. Here we would be discussing about the properties used in the UI specification of Pre-registration.
UI Specification Properties
Below are the properties in pre-registration UI specification that are used to store ID attributes in an ID object.
Name
Description
Example
ID
The id property is the unique id provided to a fields to uniquely identify it. The fields can be alpha-numeric without any spaces between them.
Description
This is a non-mandatory property used to describe the ID attribute.
Label Name
This property defines label name to be used in UI. This property has sub attributes as the language code (eng, fra, ara) to store data in different languages based on the country's configuration.
Control Type
This property defines what kind of UI component to be used to capture data in UI. Currently the values that can be used are:
textbox
dropdown
date
fileupload
Input Required
This is a mandatory property which decides if the input is to be provided from the UI or not.
Validator
This property enables us to add a the list of validators for the ID attribute. Each validator will have the below fields,
Currently, regex is supported by MOSIP, the adopter can choose to add various types of validators.
Required
This is a mandatory property which is needed to identify if the ID attribute is mandatory or not.