Desktop
Sign up page V0 (Screenshot to update)
Element’s Name | Default value(s) or Behaviour(s) | How to configure it | |
---|---|---|---|
Default settings Included in V0 Same rules for all | Title of the page |
| i18n: |
Introductory text |
| i18n:
| |
Firstname field |
| ||
Lastname field |
| ||
Email field |
| ||
Email tooltip |
| ||
Password Field |
| ||
Password field tooltip |
| ||
Company |
| ||
Terms of use Checkbox |
| ||
Sign up button |
| i18n : | |
|
| i18n : | |
Optional settings (not in V0) | Additional fields can be added to the form
|
Content Picker
Non applicable. Sign up button is not displayed on content pickers’s login page.
Mobile
Same rules as for desktop
Advanced configuration
The registration form is automatically generated based on the REST resource for storing account requests.
Adapting the registration form structure
As a default, the REST resource is /data/userregistration
which targets the structure userregistration
.
You can change the target resource by overriding the default value in config entry $.register.targetPath
.
Adding fields to the registration form is a 2 steps process:
Adapt the structure targeted by the REST resource (add / remove / edit fields of
userregistration
)Update the restful service description so that changes are reflected on the REST service
Enrich automatically generated form
Based on the structure configuration, the form fields will automatically honour the structure properties description: type, label, compulsoriness, max-length. You can still enrich this default configuration by adding config in portal to fine tune the registration form.
Adding properties to fields description for the targeted structure can be done in $.edit.<targetstructure>.fields
For instance, the default email property in the base configuration is defined as follow:
{ default: { "validators": { "email": null, }, "description": { "tip-i18n": "signin.loginForm.mail.description" } } }
Such configuration will apply a validation rule to the field to check that the value is a valid email address and add a description below the field corresponding to the tip-i18n key.
Disable the accept terms of use
You can deactivate (not show) the “I accept terms of use” checkbox by setting $.register.displayCGU
to false