Skip to content
  • There are no suggestions because the search field is empty.

How-to: Create Different Tasks or Registration Forms for Different Packages using Categories 

When a trip includes different groups of people, such as students and teachers, and they require different packages and tasks—like different profile and registration tasks—you need to display different tasks based on the selected package.

Available with any of the plans: 

How to Create Different Profile Tasks for Checkout Flow

 

Tip: When you manually add a traveler, you can also assign them the correct category, so they will be prompted to fill out the appropriate form and pay for the correct package.

1. Once you've created your categories, go to the pricing package and click on SHOW ADVANCED OPTIONS.

Under the pricing package, click on SHOW ADVANCED OPTIONS

2. Select the correct categorySelect the correct category

3. Create the same number of profile tasks as categories, then edit each task and set its visibility so it aligns with the appropriate category.

NOTE: You can only create one profile task. However, you can either copy the original task and modify it, or add another profile task from the Task Library.

Set the visibility of the associated task to align with its category

4. When travelers check out and select this package, the associated profile task form will be displayed.

When users check out, selecting this package will display the associated task form

API FIELD NAME can be duplicated if Category is distinct

TIP: This feature relies on the Category, so be careful when editing/deleting Categories. Learn more

This allows you to set API FIELD NAME values in your Task Forms to be the same as another Task, as long as the Traveler Category for the Task is not the same as the duplicate. 

This is powerful because it allows you to generate reports that reference the API_FIELD_NAME and get the field that matches for each Traveler.

This matters when you have, for example, a Student and a Teacher registration form. Maybe 40% of the fields are the same data (and would have duplicate API_FIELD_NAMES). Now that this is allowed you can have the FIRST_NAME and LAST_NAME fields in both forms have the same API_FIELD_NAME because the Category of each Task is set to 'Student' or 'Teacher'. 

So your Configured Reports (and exports from Trip CRM) will have just ONE column for FIRST_NAME instead of one for each form as it does now.