You are here : Resources > How-to Guides
There are no categories in this blog.
More Info

Actravia is an innovative web based platform for Training and Event organizers. Actravia brings online marketing, registration, enrollment, administration and payment processing into a single online center of operations.

Actravia developed by 3rd i

How to Guides
Aug 16

Written by: howto
8/16/2011 8:13 AM  RssIcon

Actravia form templates are xml files, which can be attached to an event to customize the registration process for that event. The templates follow a table-like structure with a form, rows and cells. Directives can be applied through attributes to the xml to customize the look and behavior of the form. You save and edit templates using the template manager module. All templates are available to all instances of Actravia on the website.

The following are the xml tags recognized by the parser.


Key Attributes




This is the top level element of the form and will contain a ParticipantForm element


Currently mark as “1.0”



Information only


text/csv – when exporting an event data which is assigned this template, the file generated will be of this type


The stored procedure to call to generate the export data


Tokenized filename for exporting the participant data for an event



<ActraviaDataTemplate version=”1.0” templatename=”my template” exportcontenttype=”text/csv” exportprocedure=”3rdi_mytemplate” exportfilename=”[EVENTTYPENAME] – [STARTDATE].csv” >

<ParticipantForm width=”{[nnn][px|%]}”>










This is the main form element and contains the definition of the participant registration form. Consider the form as a html table for layout purposes.

Supports width=”xxx” where xxx is the width in pixels or % of the container that the form will use.


fixedgroupsize – specific a fixed number of participants to register on the form. Must be at least one. Use in conjunction with participantgroupid for each control to give a participant index to data collected from a specific control.


<ParticipantForm width=”{[nnn][px|%]}”>








Allows control over the checkout forms to govern how they will be displayed.

Contains elements for each of the checkout forms:







Within each element you can control the display of the individual form label fields. See example. When processing the control name is found and the attribute specified is modified such as visible, text etc.




            <control name="lblFreeOrderPaymentDetails"  text="Final Details" />

            <control name="cmdFreeMakeBooking" text="Confirm" />



                    <control name="txtCCShipPhoneNumber" visible="false" />

                    <control name="PayCCPhone" visible="false" />






Define stored procedure list to call after an enrollment has been processed.

Control elements

<sqlprocedure procedurename=”{string}”/>

Specify a stored procedure to call


<parameter /> Each sqlprocedure contains an optional list of parameters. Parameter values can be tokenized with information from the order processing as illustrated.



                <sqlprocedure procedurename="dnn_myprocedure">

                                <parameter name="@signupid" type="int">[ord:SIGNUPID]</parameter>

                                <parameter name="@randomvar" type="int">2</parameter>






Each participant form contains 1 or many rows.





Each row can contain one or many cells as an equivalent html table cell (<td>).

Supports colspan, rowspan, align, valign, tooltip,visible,backcolor,forecolor, borderwidth, width, height

<cell colspan=”{nn}” rowspan=”{nn}” align=”{left|right|centre}” valign=”{top|bottom|middle} visible=”{true|false}” tooltip=”{text}” backcolor=”{colorname}” forecolor=”{colorname}” borderwidth=”{n}” width=”{[nnn][px|%]}” height=”{[nnn][px|%]}”>



Each cell can contain one or many controls. Controls are the equivalent of form controls and are used for commands and data capture.

Attributes mostly depend on the control type, however standard attributes apply to all controls. Standard attributes are: type,id,width,height,forecolor,backcolor,class,



Use participantgroupid as a zero based index to identify the control contents as being mapped to a particular participant. i.e. for a fixed group of four players, participantgroupid =”0” is for player 1, participantgroupid=”1” is for player 2 etc.

<control type=”{label|textbox|dropdownlist|checkbox|html|validator|



eventoptions}” participantgroupid=”0”>





<control type=”label”>


Adds a text label to the form.

text – Text to display

iserrormessagefield – use this label to display error messages on the form.

<control type=”label” text=”Address :” forecolor=”red” iserrormessagefield=”false”>

<control type=”textbox”>


Adds an input control for text to the form.

defaulttext – allows input control to have default text

textmode –{0|1|2} meaning singleline, multiline or password

mapfield – map to standard input field on form

participantgroupid – For forms that use the fixedgroupsize attribute, this value specifies the participant number from 0 to assign the contents of this control to.

signupfield – auto transfer content from this field to the checkout form.

lock – If using the signupfield, specifying lock=”true” will disable input for this field on the signup field.



<control type=”textbox” defaulttext=”type here” textmode=”0”/>


signupfield accepted values:

·         firstname

·         lastname

·         address1

·         address2

·         city

·         zip

·         country

·         email

·         phone

·         company

·         custom1

·         custom2

·         custom3

·         ponumber


<control type=”dropdownlist”>


Generates a dropdownlist on the form

Accepts sub elements <listoption> with text/value pairs.


Supports mapfield, signupfield, lock, participantgroupid.

<control type=”dropdownlist” mapfield=”listitem” id=”ddlList”>

<listoption text=”option 1” value=”0”/>


<control type=”checkbox”>

Generates a checkbox control.



checked – checked=”true” to default control to checked.

mapfield, signupfield, lock, participantgroupid.

<control type=”checkbox” checked=”true” mapfield=”myfield” id=”chkField”/>

<control type=”html”>


HTML Literal control for standard html content on the form


<control type="html"><![CDATA[<br/>]]></control>

<control type=”validator”>

Supports 3 validator types

validatortype {RequiredFieldValidator | RegularExpressionValidator | Rangevalidator}


controltovalidate – specify the id of the form control to validate.

errormessage – text to display if the validation fails

validationgroup – group controls, validators and commands together under the same validation group to trigger validation

display – Corresponds to static/dynamic display of the validator. {0|1|2} correspond to validator controls none|static|dynamic display.

validatorexpression – For RegularExpressionValidators, allows you to specify a regular expression

minimumvalue – used with RangeValidator type

maximumvalue – used with RangeValidator type


More than one validator can be assigned to a control


              <control type="validator" validatortype="RegularExpressionValidator" validationexpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*" validationgroup="form" controltovalidate="txtEmail" display="2" errormessage="Please provide a valid email." visible="true" forecolor="red"/>



<control type=”participantlist”>

Shows a list of participants added to order (Add participants not fully implemented yet for Forms)


emptydatatext – Text to display if no participants added to order

onclickdelete – allow delete participants already added


<control type=”eventdetails”>

Displays a full list of event dates and locations if required.

<control id="eventDetails" type="eventdetails"  />

<control type=”rateselector”>

Shows a list with the selectable rates that a user can choose. This will only be active if the event has enabled alternative rates for booking. Default display is radiobutton list but supports the attribute format=”dropdownlist” as well.

<control id="rateList" format="dropdownlist" type="rateselector" />

<control type=”salutationlist”>

Displays the list of salutation “Mr, Ms, Miss” etc. defined in the module settings. Supports format attribute.

<control id="lstSalutation" type="salutationlist" format="dropdownlist" selectedindex="0" repeatdirection="horizontal" width="100px" height="50px">

<control type=”countrylist”>



<control type=”instructions”>

Generates the participant signup instructions screen on the form and processes the tags on the form.

<control type=”instructions”>

<control type=”radiobuttonlist”>

Standard Radio Button List. Contains a list of <listoption> text value pairs. Supports attributes selectedindex={nn}, repeatdirection {horizontal|vertical}, repeatflow={flow|table},repeatcolumns={nn}.

             <control id="rdoList" type="radiobuttonlist" repeatcolumns="2" >

             <listoption text="Option 1" value="0" />

             <listoption text="Option 2" value="1" />

             <listoption text="Option 3" value="2" />

             <listoption text="Option 4" value="3" />


<control type=”command”>

Inbuilt command buttons for your form. Attributes supported are commandtype={link|button}, commandname={back|addparticipant|process}. Addparticipant is currently now supported for forms.


For commandname=”process”


<control id=”cmdProcess” commandname=”process” />

<control type=”calendar”>

Provides a date picker for entering a date. Required a boundfield specifying a control to place the selected date.

<control id="txtCtl" type="textbox"/>

<control id="calfld" type="calendar" boundfield="txtCtl" />       

<control type=”eventoptions”>

Shows a list of booking options for the user defined in the event settings.

<control id="evtOpts" type="eventoptions"  />


mapfield attribute

Applies to: textbox, dropdownlist, checkbox, salutationlist

Purpose:Maps that collected on the participant form to the database fields that will store the information.





Firstname field in the participant table


Lastname field in the participant table


Stored in the email field of the participant table


Stored in the “should notify” field of the participant table


Store in the MobileNumber field of the participant table


Stores 0 (Female) or (1) Male in the ParticipantGender field in the participants table


Participanttitle field in the participants table


SpecialNeeds field in the participants table

Other (Anytext)

Stores the field value in the ParticipantSettings table as a name/value pair linked to the participant

*These fields must be mapped for each participant


Location: Blogs Parent Separator How to Guides

4 comment(s) so far...


Re: Using Templates and the Template Manager

i wanted to know if its possible to simulate a table in a table cell layout eg

By Goerge on   9/28/2011 8:12 AM

Re: Using Templates and the Template Manager

Hi There

Not sure your message was displayed correctly but the answer is yes. The form layout consists of rows and cells.

By howto on   9/28/2011 8:13 AM

Re: Using Templates and the Template Manager

Is there a user guide for the actravia events booking module? I cannot locate one, and there a a host of configurations that have no explanation.

By Peter on   9/29/2011 3:14 PM

Re: Using Templates and the Template Manager

If you email we will forward a copy of the manual to you.


By host on   9/29/2011 3:15 PM

Your name:
Gravatar Preview
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Security Code
Enter the code shown above in the box below
Add Comment   Cancel 
Please email support[at] for pre-sales assistance & support. 
Contact support [@] for assistance.