Read field feedback
- Farina Fehmer
- Former user (Deleted)
Analytics
This support article provides insights into reading the field feedback/warnings within the e-form fields
Note: Please note that this is a generic example and does not encompass an exhaustive list of all possible warnings. The forms contain numerous fields, each requiring specific input, so consider this article as a guide to comprehend the feedback. Additionally, it's important to be aware that each mandatory field may have dependencies on other fields within the form, and the feedback may be interconnected.
Front-end feedback
Example: The expected format is an amount like 1234.56
The input of the field is invalid, the expected input is numeric, instead of text. Bear in mind that front-end errors have a simplified text and are quite straight forward, in this case you must enter a numeric value.
Let’s take a look at a more complicated field feedback, Back-end feedback.
Back-end feedback
Example: For a given lot, if 'Maximum number of candidates to be invited for the second stage of the procedure' (BT-51) was set, then 'The criteria will be used to select the candidates to be invited for the second stage of the procedure' (BT-40) must be 'yes' for at least one of 'Selection criteria' (BG-702) of lots (forms 16, 17, 18, 20, 21, 22, 23 and 24)
In this instance, there is a correlation between field BT-51 in the Second stage (Procedure) and a field located within the Selection Criteria (Participation) subsection, specifically field BT-40.
You have two options: either include a Selection criteria, and select ‘Yes’ on field BT-40 (See image below). Or (Text continues under the image)
Modify the current selection within the Second Stage subsection, where field BT-51 is situated.
