Variables and Parameters

The variables in the table below are extra back end variables and parameters that allow users to handle unwanted and invalid customer responses.

Variable	Description	Example of Use
{SetField: fieldname,required}	Defines a field that requires a value to be entered before submission.	<input name="{setfield:email,required}" value="{email}">
{SetField: fieldname,validate}	Defines a field that needs to have validation checked before submission. The type of validation check depends on the field data type, viewable in List Manager.	<input name="{setfield:email,validate}" value="{email}">
{GDCForm: NoUpdate}	Restricts records from being updated. Please note this only works for simple anonymised forms.	<form action="{GDCForm: NoUpdate}" method="POST" id="form1">
{GDCForm: NoCreate}	Restricts new records from being created. Please note this only works for simple anonymised forms.	<form action="{GDCForm: NoCreate}" method="POST" id="form1">
{Error}, {Error:fieldname}	Will capture any submission errors (to be used in conjunction with required/validate/noupdate/nocreate). When used with ifequals() function (as displayed in the example column), if returns [blank] then successful, otherwise it will return the error type.	{Error:Email}.IfEquals([][][<strong>Please enter Email</strong><br>]) OR <input disabled value="{Error.GDCForm}" name="GDC Form">

For example:

NOTE Please ensure that for all forms you utilize the Validate variable. If a form is submitted and the data type entered by a recipient does not match the data type required in the list by Email Manager, it will reject the submission. If the correct error handling has not been added this may not be obvious to the recipient submitting the form.


	© Alterian. All Rights Reserved. \| Privacy Policy \| Legal Notice