...
In order to approach this problem in a dynamic way YC the platform offers a number of tools for configuring typical forms.
...
Adding password and confirmPassword attributes with enable customers to specify password of their choosing during registration (see password managemen cookbook for more details).
...
| Attribute | Value | Mandatory | Since | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| salutation | 2.x.x | Salutation is an optional attribute that "proxies" salutation property on the Customer object | ||||||||||||||
| firstname | 2.x.x | First name is mandatory attribute that "proxies" firstname property on the Customer object which is a mandatory field. Attempt to create Customer object without it results in SQL error. | ||||||||||||||
| middlename | 2.x.x | Middle name (second name) is an optional attribute that "proxies" middlename property on the Customer object | ||||||||||||||
| lastname | 2.x.x | Last name is mandatory attribute that "proxies" lastname property on the Customer object which is a mandatory field. Attempt to create Customer object without it results in SQL error. | ||||||||||||||
| 3.5.0 | Email property allows to define email regex. Since shops can have own specific view on what correct email regex is, the attribute is driven by value which must be email. Attempt to create Customer object without it results in SQL error. | |||||||||||||||
| password | password | 3.5.0 | Marks a password field to be used in the form. The input is captured only inside the system to create a password hash. The attribute is not saved on Customer object | |||||||||||||
| confirmPassword | confirmPassword | 3.5.0 | Marks a password field to be used in the form. The input is captured only inside the system to create a password hash. The attribute is not saved on Customer object | |||||||||||||
| regAddressForm | regAddressForm | 3.5.0 | Marker attribute for registration for to include shipping address form for given customer type. Note that because fields such as salutation, firstname, middlename, lastname, companyname1, companyname2, companydepartment and phone1 (CUSTOMER_PHONE) exist on address form there is a fallback mechanism to prevent "double fields". For example CREG shop attribute with our address form:
| |||||||||||||
| companyname1 | 3.5.0 | B2B company name "proxies" companyName1 property on the Customer object | ||||||||||||||
| companyname2 | 3.5.0 | B2B additional company name (e.g. suffix) "proxies" companyName2 property on the Customer object | ||||||||||||||
| companydepartment | 3.5.0 | B2B department within company "proxies" companyDepartment property on the Customer object |
B2E registrationLabel Body
| Body |
|---|
...
SaaS Colour info
| SaaS | |
| Colour | info |
|---|
B2E is a feature whereby a shop represents a market place or a collection of subshops where each registered customer could belong a specific sub shop. In such cases the customer account needs to be associated with specific sub shop. For that purpose a special CUSTOMER group attribute b2bsubshop is used. It is rendered as a text field which requires customer to enter the name of the sub shop they are registering in.
...
This configuration provides flexible mechanism for categorising customers. For example by departments in large customers or to provide privileged access to products and special prices.
Manager assisted registrationLabel Body
| Body |
|---|
...
SaaS Colour info
Label Body 3.7.0+
| SaaS | |
| Colour | info |
|---|
| Body | 3.7.0+ |
|---|
When manager logs in into storefront one of the options available is to register a new customer. This is usability improvement feature which allows manager to have a per customer type focused form with all fields required to register that customer including default address with one click.
...
Email is a very common control around the shop which cane user in login, registration, contact form, newsletter form and effectively in any form that requires email communication with customer. As such it is sometimes important to provide restrictions on which kind of emails can be used.
YC Platform versions 3.5.0+ now have capability to specify shop specific email regular expressions to validate all email fields used in shop.
New special customer type is defined as EMAIL in YC thus the platform thus allowing to created a registration attribute form for SHOP_CREGATTRS_EMAIL. This configuration must have a single CUSTOMER group attribute definition that lists the email field to use.
...
| Code Block |
|---|
{{salutation}} {{firstname}} {{lastname}}
{{addrline1}} {{addrline2}}
P/O: {{postcode}}
{{city}} {{statecode}}
{{countrycode}}
Tel: {{phone1}}
Mob: {{mobile1}}
Email: {{email1}}
|
ContactLabel Body YCESaaS Colour info
Configurable contact forms is a feature that allows to generate any type of contact form by creating a form definition and then calling the form by ID.
...