Cookbook - Forms Management

Last modified by Denis Pavlov on 2018/08/16 22:36


Any shop has a number of different types of form that customers can interact with. One of the basic examples are registration form - every commerce shop has it and it is different for almost every shop. Reason behind this is that each business wishes to collect different types of information. 

In order to approach this problem in a dynamic way YC offers a number of tools for configuring typical forms.


Each shop can define several supported customer types, which essentially means the types of customers that can register on the site. This is defined by shop attribute SHOP_CUSTOMER_TYPES  which accepts a localised free form list of values. Typical definitions could be B2C, B2B, B2E but it is at business user discretion what customer types to create. Note that there is a special type B2G which is reserved for guest checkout customer type.

Typical configuration may look like this:


For each of these types it is now possible to define list of CUSTOMER group attributes that will represent this form. This list is set in shop attributes SHOP_CREGATTRS_XXX where XXX is the customer types defined above.

For example:


From the screenshot it can be observed that for each type of customer there is a different list of attributes. 


These attributes can be viewed in the admin application System > Attributes > CUSTOMER group 


Therefor each property can have a full definition of the labels, validation properties and type of values that allows to automatically create registration forms specific to customer type in each shop. The fields are ordered in the same sequence as defined in the SHOP_CREGATTRS_XXX attribute, so sorting field as simple as rearranging the list. Changing the type of the attribute definition will result in specific form field type. For example Boolean value will be displayed as checkbox, CommaSeparatedList - select box etc

There are special system values that are associated with each customer account such as email and password. Prior to version 3.5.0 these are build into templates. However in versions 3.5.0+ there are no more fixed fields and everything is configurable. To identify these special attributes the attribute definition's value has to be set with: email, password or confirmPassword.

This gives flexibility to have multiple configurations. E.g. create one attribute with [CODE=email, VAL=email] with one regex and then [CODE=another_email, VAL=email] with different regex. 
Thus you can define different set of the email attributes per shop or even per customer type. 

Adding password and confirmPassword attributes with enable customers to specify password of their choosing during registration (see password managemen cookbook for more details).

Adding email attribute is mandatory for versions 3.5.0+ for registration form to work.

After set up the shop registration form will look something like this:


Registration attributes cheat sheet

Below are mandatory/special attributes for registration forms that are defined in the CUSTOMER attribute group

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.
email email   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.
passwordpassword  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
confirmPasswordconfirmPassword  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
regAddressFormregAddressForm  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: email,salutation,firstname,middlename,lastname,CUSTOMER_PHONE,MARKETING_OPT_IN,password,confirmPassword will be replaced to email,regAddressForm,MARKETING_OPT_IN,password,confirmPassword if your shipping address form had salutation,firstname,middlename,last name,phone1
companyname1  3.5.0B2B company name "proxies" companyName1 property on the Customer object
companyname2  3.5.0B2B additional company name (e.g. suffix) "proxies" companyName2 property on the Customer object
companydepartment  3.5.0B2B department within company "proxies" companyDepartment property on the Customer object

B2E Registration YCE

B2E is a feature of  YCE 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 required customer to enter the name of the sub shop they are registering in.

If this attribute is not preferment in the list of registration form attributes for that type the customer is registered in master shop

This configuration provides flexible mechanism for categorising customers. For example by departments in large customers or to provide privileges access to products.


Similarly to registration form attributes the profile form can be configured as list of CUSTOMER group attributes. This configuration is separate to registration form thus allowing flexibility to specify additional properties or hide some which were captured during registration.

Profile forms are controlled by shop attributes of the form SHOP_CPROFATTRS_VISIBLE_XXX and SHOP_CPROFATTRS_READONLY_XXX for list of customer type specific profile form and list of attributes which cannot be edited on that form respectively. To specify common definition of the profile form SHOP_CPROFATTRS_VISIBLE and SHOP_CPROFATTRS_READONLY (without the customer type suffixes) can be used.


Guest Checkout

Guest checkout is viewed as a special case of registration form. In fact it can be seen from Registration form overview above that there is SHOP_CREGATTRS_B2G is used to define the guest checkout form. Therefore the configuration of the form itself is exactly the same as for normal registration.

One subtle difference is that this type of checkout has to be enabled by setting shop attribute SHOP_CHECKOUT_ENABLE_GUEST. When this attribute is set to true the form will automatically appear as an option on the checkout page for non-logged in customers .


Email 3.5.0+

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 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 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.

This definition provides validation configuration for login, contact forms and newsletter forms across the whole shop.


Address form takes on the same principle discussed for registration and profile, however it deals with attribute definitions defined in ADDRESS group.

The linking of attributes is different as all configurations for address forms are done via ADDRESS group attributes. The rationale for this is that whereas registration and profile forms are shop specific (and hence are forms are defined in shop attribute), address form are country specific in most cases and thus can be shared by many shops.

The basic form definition for address form is defined in default_addressform attribute definition of the ADDRESS group. This is the configuration for the globally shared address form (effectively a master fallback for address form) and looks something like this:


As depicted on the screenshot of the Options tab, the default value lists all ADDRESS group attribute codes that define this form. Each attribute listed can be found in the same attribute group listing.


Each of these attributes definitions provides the label, validation and type of field configurations in similar fashion as registration and profile forms are configured. One important difference to note is that all field specific attributes must specify field where values are written to in the value of attribute definition. This is similar concept to email and password fields attributes described previously.

Inspecting for example default_city attribute will show that its value is set to write to the city property on the address object.


Address attributes check sheet

Value mapping

Table below depicts value options are available for the address object. Note that values marked mandatory must be present in the form as these are defined as mandatory on Address object.

Value Mandatory Since  Description 
name   3.5.0 Address name e.g. "Home", "Work"
city   2.x.x City
postcode   2.x.x  Post code / Zip code
addrline1   2.x.x Usually street
addrline2   2.x.x Usually house number or apartment details
countryCode   2.x.x Special field which automatically lists countries available for this type of address in a select box
stateCode   2.x.x Special field used when states are defined for countries in locations section of admin
phone1   2.x.x Phone
phone2   2.x.x Another phone
mobile1   2.x.x Mobile
mobile2   2.x.x Another mobile
salutation   2.x.x Saluation
firstname   2.x.x First name
lastname   2.x.x Last name / Surname
middlename   2.x.x Middle name
email1   2.x.x Email (this is not customer email but rather an email address to use with this address e.g. like company email if delivered to warehouse)
email2   2.x.x Another Email
companyName1   3.5.0 B2B company name
companyName2   3.5.0 B2B additional company name e.g. suffix
companyDepartment  3.5.0B2B department within company
custom0   2.x.x Custom field 0
custom1   2.x.x Custom field 1
custom2   2.x.x Custom field 2
custom3   2.x.x Custom field 3
custom4   2.x.x Custom field 4
custom5   2.x.x Custom field 5
custom6   2.x.x Custom field 6
custom7   2.x.x Custom field 7
custom8   2.x.x Custom field 8
custom9   2.x.x Custom field 9

Each address object allows to capture some core fields that have specific names but also has 10 custom fields that can be used for anything. Therefore depending on the attribute definition these fields can have own labels, validation rules etc.

Declaring address form attribute

In order to create forms which are address type specific or shop specific or both we can use prefixes. Consider the following example where we have two shops with shop code SHOP10 and SHOP20, which are ordered in the sequence of rank (i.e. default lookup sequence)

Form definition attribute code Eligible for 
SHOP10__B2B_addressform_S  SHOP10 definition for B2B customer type definition for shipping addresses
SHOP10__B2B_addressform_B  SHOP10 definition for B2B customer type definition for billing type addresses
SHOP10__B2B_addressform  SHOP10 definition for B2B customer type definition for shipping and billing type addresses 
SHOP10__default_addressform_S  SHOP10 definition for shipping type addresses
SHOP10__default_addressform_B  SHOP10 definition for shipping type addresses
SHOP10__default_addressform  SHOP10 definition for shipping and billing type addresses
B2B_addressform_S  Global definition for B2B customer type definition for shipping addresses available to SHOP10 and SHOP20 
B2B_addressform_B  Global definition for B2B customer type definition for billing type addresses available to SHOP10 and SHOP20 
B2B_addressform  Global definition for B2B customer type definition for shipping and billing type addresses available to SHOP10 and SHOP20 
default_addressform_S  Global definition for shipping type addresses available to SHOP10 and SHOP20  
default_addressform_B  Global definition for shipping type addresses available to SHOP10 and SHOP20  
default_addressform  Global definition for shipping and billing type addresses available to SHOP10 and SHOP20 

Contact YCE

Configurable contact forms is YCE feature that allows to generate any type of contact form by creating a form definition and then calling the form by ID.

The configuration process is virtually the same as address forms, however for contact forms a separate attribute group CONTACTFORM.

Once the forms are configured they can be rendered on pages using a url include using two parameters formId which is the attribute code of the CONTACTFORM attribute that has the form declaration and view ("ContactsForm" is default but your theme may have own special template):

ctx.includeurl "/internal/contactform?formId=default_contactform&view=ContactsForm";

Because the contact form submission is done via AJAX you can also place any arbitrary form in any part of the CMS content using script include

<script type='yc-include'>/internal/contactform?formId=default_contactform&view=ContactsForm</script>


Created by Denis Pavlov on 2018/05/19 14:31 © 2009 - 2018