Validation - errors, warnings, information and success
The form data entered is checked on the server side. Input requirements, simple field value checks and complex dependency and backend checks can be defined for validation.
The input requirement can be defined statically and dynamically (depending on user input). Additional input patterns are available for blocks, such as "All or nothing" or "Mandatory input with free selection".
Existing checking and business logic from specialist applications can also be easily integrated into AFS forms using web services. The integration of the form and downstream specialist system eliminates the duplication of validation code.
AFS offers two different error states for validation errors. In addition to the classic "Incorrect entry", which must be corrected before the form can be completed again, there is also the "Warning" status. Here, an "Implausible entry" is only pointed out once and accepted as a field value when confirmed again by clicking "Next".In addition to errors and warnings, information and success messages are also available for feedback to the user.
Errors and implausible entries can be displayed at the top of the page and directly next to the field. AFS offers automatic texts for all error and warning states, which can be supplemented or overwritten with specific information texts.
The configuration of validations, errors and warnings is carried out with the help of "parameterizable" extenders. These are described in "Form dynamics & logic".
Special validation & warnings
Google ReCaptcha, currently the most widely used CAPTCHA on the internet, can be used in AFS forms. This is a security mechanism that is used to distinguish fully automatically whether a human or a machine is making entries.
The risk of a session being aborted due to a timeout if the user is inactive for too long is displayed beforehand as a warning message. In general, AFS sessions can be configured to remain active if the browser window is still open. In the case of an e-payment process, the session can be extended until the payment confirmation is received.
Form navigation & progress bar
A navigation bar and progress bar can be added to AFS forms. This makes it possible to combine one or more form pages into a logical step. The bar is also used to call up specific pages in the form (page navigation).
The form navigation can be activated and configured individually for each form. The appearance and positioning of the progress bar can be customized using CSS. The display is available both in the desktop view and in the form view for mobile devices. For the latter, the display is reduced to a minimum. If the user temporarily saves the form entries, the navigation progress is also saved in the form.