...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Conditional display/conditional visibility is only available in v2 (not v1)
View the webinar that demonstrates these eight examples at Video - v2 Pagebuilder skills
View the webinar on package tickets and conditional visibility at Getting Started - Videos - Events Registration
See also BigCamp sample for v2 pagebuilder
...
| 1 | Create the questions (drop-down), and create a text box that contains the text/information attendees are to see after they make a workshop selection.
|
| 2 | Add a unique field name to the question where "part 1" of the workshops begins. Then, add a conditional visibility rule to the text box, so the text displays when attendees select "part 1" workshop.
|
3. Tickets available according to attendee type - staff/adult/children
E.g. Meal tickets, attendance tickets, activity tickets.
| 1 | Create a drop-down question for attendee type. Create the tickets for one group inside a panel/div/well, create the tickets for the next group in a separate panel/div/well.
|
| 2 | Add a conditional visibility rule to each panel, so it is displayed according to the attendance type selected. Ensure that the text in the rule exactly reflects the text in the drop-down question, including spaces/capitals/etc.
|
4. Enter a promotional code to see a discounted ticket
E.g. Staff receive a promotional code via email, staff enter the code on the event webpage, and then the discounted/free Staff ticket is displayed.
| 1 | Create a short text question that requests the promotional code, give the question a Field name (example below uses "promo" as field name). And, create the ticket to be shown once the promotional code is entered. |
| 2 | Add a conditional visibility rule to the ticket, so it is displayed when promotional code is entered. Note that the code will be case-sensitive.
|
5. Move ticket to a different section
E.g. Ticket has been created in the page builder, but now needs to appear in a different (earlier/later) section of the Event's webpage.
| 1 | Double-click to open the ticket and check the number "Sold."
Zero tickets sold - refer to steps 2 & 3. One or more tickets sold - refer to steps 4 onwards. |
| 2 | If no instances of the ticket have been sold: In the Ticket drop-down list select Save as template and give it a unique name.
|
| 3 | To add a saved template to an Event, open the section where the template is to be added. Click to expand the Search menu, type the template name in the search box. Click on a green template name to preview it. Drag-and-drop the green template name onto the pagebuilder area, the template is inserted into the section.
Icon showing the template can be inserted at this location:
Icon showing the template cannot be inserted at this location:
|
| 4 | If one or more instances of the ticket have been sold Delete the ticket. It will be saved in the Unused tickets list.
Open the Event Tickets menu, deleted ticket should appear in the Unused tickets list (refresh section if ticket doesn't initially appear).
|
| 5 | Open the Section where the ticket is to appear. Click to open Event Tickets. In the Unused tickets list, click to select the required ticket, then drag-and-drop the ticket into the desired location on the pagebuilder.
|
| 6 | The ticket details will open automatically, review those and click Save.
The ticket appears in its new location
|
6. Applications have now closed
E.g. Applications have closed, but there is additional information to be shared to non-registered persons who visit the event webpage.
| 1 | Create a new section, make it the first section for the event (e.g. "Close Page" below). Add the details that are now relevant
|
| 2 | On the Event Details tab, check the Availability options Allow registrations should still be ticked and the End date should be a future date, otherwise visitors to the Event's URL (webpage) will instead see a "Not available at this time" message.
|
...
7. Using Global vs Multi-attendee sections
E.g. Accommodation is to be selected per registration, but each attendee needs to give name/health/address/division details.
| 1 | Review the details that need to be recorded per registration - these are global details. E.g Global details: site/room type, furniture, address, phone, car registration, special requests, additional agreement information, etc. Review the details that need to be recorded per attendee - these should be in a multi-attendee section E.g. Multi-attendee details: division they're attending, workshops, camper fee per person, meal tickets per person, activities, etc. |
| 2 | Sections are global by default. To change a section to multi-attendee, click the Edit Section button
|
| 3 | Tick the box 'Repeat this section for each attendee', click Save
|
| 4 | The multi-attendee icon appears next to the Section name
|
...
Scenario B. Once per attendee
| 1 | Open an existing global section where the tickets are to appear; or, create a new global section by clicking Add new in the Sections area of the pagebuilder (top left)
Type the new section's Title, click Save; ensure the checkbox for 'Repeat this section for each attendee' is not ticked
|
| 2 | Create tickets as required. Ticket names should indicate the total number of family members included; ticket prices should indicate the correct price for the total number of family members included. |
| 3 | If each discounted ticket is made to be a 'package ticket' of the full-priced ticket, note that it will only reduce the full-priced ticket availability by one, it does not reduce it by two, three, four, etc. Final numbers of attendees who are expected to attend will need to take into account how many tickets have been sold for two, three, four, etc attendees. e.g. an attendee purchases a 'three teens' ticket. This reduces the three teens ticket availability by one. If the ticket was a package ticket of the full-priced 'one teen' ticket, the 'one teen' ticket's availability will also be reduced by one. However, the registration is for three teens, so the event organiser needs to adjust final numbers with consideration of this. |
10. Pathfinder and Adventurer registrations
| 1 | Templates have been created for Pathfinder and Adventurer registrations, in v2 |
| 2 | Type 'pathfinder' or 'adventurer' in the Search box. Click on the green template name to preview it. |
| 3 | Drag the template for p1 into the first section in your v2 Event. Drag the template for p2 into the second section in your v2 Event. There are instructions for Event Admins in the red panel at the top of both templates. Edit the questions/tickets as required. |
Related articles
BigCamp sample for v2 pagebuilder
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...