Basic Logic Suffixes

<<%_IDFinancialOptions>> - This will display a list of the ID's of all the financial options in the selected prefix (Cart, CartParticipant, Order, etc.).

Typically used to ask a question or set of questions if a specific financial option is selected.

EXAMPLE: There is a financial option that someone can select to attend a meal, you can apply this logic to a question that can ask them what type of a meal they want.

<<%_IDProducts>> - This will display a list of the ID's of all the products/events/camps in the selected prefix (Cart, CartParticipant, Order, etc.).

Typically used to ask additional questions if a given event is in the cart, it is strongly recommended to use the financial option logic listed below if possible, as it will be easier for you to maintain over time.

IMPORTANT NOTE: If you are able to, it is typically better to use Category Option logic instead of Product or Financial Option logic, as it will keep the logic functional year after year without having to consistently update the logic whenever you add new Events or Financial Options. 

<<%_IDCategoryOptions>> - This will display a list of the ID's of all the category options attached to the events that are in the selected prefix (Cart, CartParticipant, Order, etc.), even if those category options were not directly selected by the registrant.

EXAMPLE:

If you wanted a discount/fee/question/text block to display for an entire "group" of events, even if the registrants have no idea that those groupings exist.  It provides a good way to group a set of events and make something apply if any of them are selected.  For example if you had a set of special needs camps that required and additional section worth of questions to be answered you could assign all of those camps to a "special needs" category option, and put section logic that would make it appear if they had selected any camp that has that category assigned to it.

<<%_CategoryChosenHistory>> - This will display the ID's of all the categories that the registrant had selected in the registration process.  This is primarily used as <<CartParticipant_CategoryChosenHistory>> in order to ask specific questions or make specific financial options display if someone has selected a given category.

EXAMPLE:

Scenario: An event wants to know if the person in question is a member, if they do they will be asked what their membership number is, and they will also be given a member discount.

1 .You would first set up a category called "Are you a member?" within that category you would create the category options "Yes" and "No" and apply all the events that are applicable to both of them.  Insert this category choice into the form.

2. You would create a question on the form "What is your membership number?" and a auto-apply in cart Financial option that was a discount of the correct amount. 

3. To both of those you would apply the logic ###### in <<CartParticipant_CategoryChosenHistory>>, this would make both of those only display if they had selected "Yes" for Member.

<<Cart_NumAssignedParticipants>> - Taking the cutoff date into account, the number of participants with at least one active event with the financial option assigned in the account & cart

EXAMPLE:

applied to all participants if more than 7 participants

<<Cart_NumAssignedParticipants>> >= 7

applied to all participants if less than 6 participants

<<Cart_NumAssignedParticipants>> <= 6

applied to all participants if less than 6 and greater than 1

(<<Cart_NumAssignedParticipants>> <= 6) && (<<Cart_NumAssignedParticipants>> >1)

<<CartParticipantProduct_IsWaitlist>> - Will return a 1 if the product is a waitlist.

<<CartParticipant_FinancialOptionQuantity>> - Returns the quantity of financial options purchased by the participant.