To set up and configure registration for an event, you must first set the Registration Defaults. The registration defaults set the price list, dictionary, sign-in configuration, and custom fields to use as the default, among other things.
Registration defaults are set on the Define Registration Defaults screen from the Main Menu. Most of the defaults act only as default values, and you can change them on the Registration Setup screen for each individual event if desired. Fields marked with a red asterisk (*) are required for registration setup.
- Price List - Default price list for the registration orders.
- Registrant Type Resource - Default registrant type resource for registrant types.
- Function Resource - Default registration function resource for registration functions.
- Dictionary - Default dictionary for the public registration site.
- Regional Setting - Regional settings used on the public registration site.
- Description - Default description used for the public registration site. The Description field is used with multiple languages and controls which description for items/resources (Primary, Alternate 1, Alternate 2) goes with which language. For example, English is the Primary Description, French is Alternate 1 and German is Alternate 2.
- Sign In Configuration - Default sign-in configuration for the public registration site. You can configure sign-in configurations to include different information, have different requirements, or have no requirements.
- Sign Out Return Link - Defaults the URL the public user is directed to if the sign out link is clicked in public registration. If left blank, the public user returns to the first page.
- Order Status - Order status assigned to new registration orders.
- Form Template - Default form template for the public registration site. The form template is how the public registration pages are laid out, including section headers, page breaks, instructional text, duplicate registrant checking, function information, payment options and confirmation information.
- Web Skin - Default web skin for the public registration site. Web skins control the appearance of the public registration website, including the background color, font style and color, heading, buttons, page setting, and page sections.
- Manage Relationships Section
- Relationships for Registrants - Relationship created, if any, between registrants and organizations when registering.
- Create Account to Contact and Contact to Contact - Creates a relationship between the organization and registrant and a relationship between registrants. Example: You register Clark and Lois who both work for Metropolis Enterprises. A relationship is created between Metropolis Enterprises and Clark (Account to Contact), between Metropolis Enterprises and Lois (Account to Contact) and between Clark and Lois (Contact to Contact). This is often used for Exhibitor Registration.
- Create Only Account to Contact - Creates a relationship between the organization and registrant. This does not create a relationship between registrants. Example: You register Clark and Lois who both work for Metropolis Enterprises. A relationship is created between Metropolis Enterprises and Clark (Account to Contact) and between Metropolis Enterprises and Lois (Account to Contact). No relationship is created between Clark and Lois. This is often used for associations.
- Create Only Contact to Contact - Creates a relationship between registrants. A relationship is not created between an account and contact. This is often used for camp registrations for parent and child relationships.
- Do not create any relationship - No relationships are created. Often used for Professional Conference Organizers (PCO).
- Relationship used when adding multiple Registrant - Relationship created between any new registrants on the same order when registering.
- Relation searched when adding multiple Registrant - Relationship type(s) searched across when adding multiple registrants to the same order.
- Relationships for Guests - Relationship created, if any, between guest registrants and organizations when registering.
- Relationships used when adding Guests - Relationship type created between new guest registrants added to the same order.
- Relationship searched when adding Guests - Relationship type(s) searched across when adding guests to an order.
- Relationships for Registrants - Relationship created, if any, between registrants and organizations when registering.
- Manage Resources Section
- LinkedIn Resource - Resource to identify a LinkedIn group page click through.
- Facebook Resource - Resource to identify a Facebook group page click through.
- Tracking Resource - Resource for tracking promo codes and discounts.
- Other Defaults Section
- Order Department - Order department assigned to new registration orders.
- Allow Registrant Substitution - If checked, registrants can substitute one registrant for another.
- Registration Auto-Add Note Class - Note class for any auto-generated notes during registration.
- Use Price Classes for Registration Orders - If checked, only valid price lists matching the Account Price Class are available when adding a registration order.
- RG Disable Def Add Info for Added Contact - If checked, the address information from the associated account does not default for the contact.
- Disable Address When Editing Company or Contact - If checked, the address information and communication codes from the company do not default for an existing contact when changing the company of the contact.
- Transfer Reason Note Class - Note class for the transfer reason note created when transferring registrants.
- Custom Fields Defaults Section
- Registrant Custom Fields - Default registrant custom fields.
- Registrant Order Custom Fields - Default order custom fields.
- Guest User Fields - Default guest user fields.
- Registration Contact User Fields - Default registration contact user fields.
- Registration Account User Fields - Default registration account user fields.
- Registration Fulfillment Order User Fields - Default registration fulfillment order user fields.
- Allergy Custom Fields - Default allergy custom fields.
- Behavioral Conditions Custom Fields - Default behavioral conditions custom fields.
- Medical Condition Custom Fields - Default medical condition custom fields.
- Medication Custom Fields - Default medication custom fields.
- Check the Registration Conflicts on the Web - If checked, conflicts between registration functions are checked during public registration.
- Check Registration Conflicts in Backoffice - If checked, conflicts between registration functions are checked during back office registration.
- Default Order Account When Adding Reg Items - If checked, the order account defaults in the Add Registration Order Items screen.
- Check-In Badge Format - Default back format for registration check-in.
Comments
13 comments
Is there a way to delete the Registration Options function?
0 upvotes
I assume you are referring to the function that is automatically created when you setup an event for registration. That function cannot be deleted as it contains the registrant type(s) for the event. V20 registration rules and workflows are based on registrant types.
0 upvotes
Yes, that's the function I'm referring to as I'm copying the event in v19 because of Abstract configurations, but will be building v20 registration.
Thanks
0 upvotes
Is there a need to make the Price List and Resource selections mandatory? For many Organisations, there are many applicable Price Lists and Resources for each event.
It is true that supplying a default selection can speed up the setup process for any given event, but by making it mandatory, you are forcing the wrong data into potentially 90+% of events thus making the setup process per event much longer than it needs to be.
Keep the option of a default, just don't make it mandatory.
What are your thoughts Danilo?
2 upvotes
I agree with that Sean; I think we have this in the backlog, I'll review and follow up with you later.
1 upvotes
Hi Danilo,
Any progress on this?
0 upvotes
Hello, We were hoping to update our default custom fields set. We created a new custom field set but when we update in registration default it changes all of our past events as well. Is there a way to have the defaults only apply to future events, or will it always update all events when we update defaults?
What we were really wanting to do is to define what custom field set to use when we were building a form template, but from what we can tell that seems to be controlled only by the registration default. Is there a way to choose which custom field sets we want to use when we are setting up a form template?
0 upvotes
Hi Sara,
The custom fields setup in Registration Defaults are setup to track information about attendees across events, usually, we use these fields for individual profile information, that is the reason you have to setup these within Registration Defaults. We do not delete previous event information; we use the new setup for all events in the organization. Registrant Custom Fields are setup at the event level; you can use different sets on different events. They should be the ones you use to track the registrant's information for a particular event.
Thanks!!
0 upvotes
Hi Sean,
No update yet, we can use event profiles to create events, they should help to alleviate some steps on the process.
0 upvotes
Hi Danilo,
Thanks for the quick response. I understand that when we have custom fields that are event specific that is where we select our custom field set. I am referring to the Account Group fields (screenshot below). These are the question sets we are trying to change as we have created a new, cleaned up list of questions to use for all future events. The only way we could find to change these is to update the custom field set in the registration default (second screenshot below). However, when we update to our new list it changes previous events. We thought that the default would only apply when we create a new event, but it also seems to be changing all previous events when we tried it in test. Is there a way to change the field set/questions for future events only? Or maybe a better way for us to set up our template?
0 upvotes
Hi Sara, The defaults affect previous and future events. The current data won't be deleted, but you will need to update current events that are live. You will be able to see the previous set within the Registration Contacts list. Doing it only for future events is an enhancement.
0 upvotes
Default values not affecting past events is an enhancement? This is not expected behaviour or how any other defaults work in the system.
I think these default values need a rethink. The comment regarding event profiles does not really assist me either but thanks for responding.
PS - can you please address the display of the default resource values? 306|NOCOST looks like an invalid value but that's how it renders after you save causing confusion.
0 upvotes
Hi Sean, this is exactly the same behavior that we have in v19. If you change the organization parameters for accounts in registration, organization or individual (Registration Defaults) or for any other application using UDFs you will find the same behavior. We DO NOT delete the values in table CR073, but we will change the default behavior on any of the parameters we change: Events, Accounts, Bookings, etc. Are you maybe confused?
0 upvotes
Please sign in to leave a comment.