New data structure for managing verification fields

[taitus]

Related Issue: #24

Why is this Needed?

• Allow to relate each of the new fields that are added in each verification process with your controller
• Store the information entered by the user on the front verification page
• Save your possible response

Description

VerificationFields
Table where each of the verification fields added in each of the verification processes are stored. The fields contained in this table are:

• name: Name of the new field introduced by the administrator in each process.
• alias: To relate the parameters sent to the WebServices (Remote Census, SMS) with the new defined fields. 🤔 (Do we really need it?)
• position: This field will help us to define the order in which we want to show in the frontend verification page, all the fields defined in the verification methods.
• controller: This field will not be editable by the user, but will be saved automatically with the controller associated to each verification method. For example: For all the fields added in the Verification Process of the Remote Census, the field controller will be filled with RemoteCensusController (that is the new controller that we are going to create to manage the verification of remote census).
• required: In the "Custom Verification" method there will be the possibility to check your fields as optional.

VerificationValues
Intermediate table between User and VerificationFields in order to store both the information entered by the user in the frontend verification page and the possible response of the server to which we send this information. The fields contained in this table are:

• verification_field_id
• user_id
• user_submitted_value: To save the value entered by the user on the frontend verification page.
• server_response_value: To save the value of the possible response of the server to which we will send this information (Remote Census, SMS).

VerificationFieldTranslations
Translation table to allow the user to define the labels that will appear for each of the fields entered on a user's frontend verification page. The fields contained in this table are:

• label: It will allow to store the label for each available locale of the application.