Introduction / Overview
- This guide explains how to build custom request forms by creating additional order fields that will appear when users submit requests for your events and assets.
- Request forms allow you to collect specific information from users based on your business needs, whether for ticketed events, non-event assets, or specific categories.
- Before starting, ensure you have admin access and understand your organisation's data collection requirements.
Activation & Set-up
- Step 1: Go to your company settings
- Step 2: Click on the "Lists" tab,
- Step 3: Scroll down to locate the "Additional Order Fields" section - this is where you'll build your request form
Steps / How-To
-
Add Your First Form Field
- In the Additional Order Fields section, click "Add Order Field"
- This opens the field creation interface, where you'll configure each question
-
Select Field Type
- Choose from Content Types (for informational elements):
- Section Header: Creates headings to organise your form
- Text Section: Adds descriptive text or instructions
- Choose from Input Types (for data collection):
- Date Field: Collects date information
- Drop Down List: Provides selectable options
- Email Field: Captures email addresses
- Number Field: Collects numerical data
- Text Field: Allows free-text responses
- Tick Box: Creates tick boxes for yes/no questions
- Email Approver: Designates approval workflow contacts
- Choose from Content Types (for informational elements):
-
Configure Asset Type
- Select where this field should appear:
- Events with Tickets: Shows on ticketed event requests
- Non-Event Assets: Displays on non-event asset requests
- Select where this field should appear:
-
Set Business Objective Parameters
- Choose "All Objectives" to display the field across all business objectives
- Or select "Specific Objectives" and choose from the dropdown which business objectives should include this field
-
Define User Division Access
- Select "All Divisions" to show the field to all users
- Or choose specific divisions that should see this question
-
Apply Category Filters
- Choose "All Categories" to apply the field universally
- Or select specific categories (e.g., separate questions for F1 tickets vs. football tickets)
-
Set Page Placement
- Choose whether the field appears on Page 1 or Page 2 of the request form
-
Build Field Content
- Enter the field name/question text
- For dropdown fields: Add all available options
- For text fields: Set maximum character length if desired
- Use the "Required Field" tick box to make responses mandatory
-
Save and Organise
- Click "Save" to create the field
- Repeat steps 1-8 for each additional field needed
- Use the three-line sort handles on the right to reorder fields by importance
-
Preview Your Form
- Navigate to an event to see how your completed request form appears to users
- Test the form functionality to ensure it meets your requirements
FAQs
- Q: Can I create different forms for different types of events? A: Yes, use the Categories setting to specify which event types should display each field, allowing you to create customised forms for different event categories.
- Q: Can I make fields visible only to specific user groups? A: Yes, use the User Divisions setting to control which user groups see specific fields, allowing for role-based form customisation.
- Q: How do I reorder my form fields after creating them? A: Use the three-line sort handles on the right side of each field in the Additional Order Fields section to drag and drop fields into your preferred order.
- Q: What happens if I don't set a field as required? A: Non-required fields will be optional for users, allowing them to skip those questions when submitting requests.
Related Articles / Resources
Conclusion
- You've now successfully learnt how to build custom request forms using additional order fields, enabling you to collect specific information tailored to your business needs.
- Remember to test your forms after creation and adjust field ordering based on user feedback and data collection priorities.
- For additional customisation options or troubleshooting, refer to the related articles above or contact support for assistance.
Comments
0 comments
Article is closed for comments.