Other Useful Logic

Top  Previous  Next

<<Org_AdminMode>> == 1

Makes whatever this is attached to only show  up when in admin mode.

 

<<Org_DateAndTime>> < '2/9/2009 9:00 AM'

This is the format you would use to reference dates in the system for any field that uses specific dates.  This particular example would make the item show up if the date is “less than” February 9th at 9 AM.

 

<<CartParticipantProduct_DaysUntilBegins>> (and also <<CartParticipantProduct_DaysUntilEnds>>) Returns the number of days until the Start or End date of the program

 

This is used when you want to make generic late fees based on the relative registration date (i.e. “show late fee starting 5 days before registration”) as this is not an option in the Financial Option display tab to be created through the user interface.

 

EXAMPLE:

Apply if there are 5 or less days until the event begins.

<<CartParticipantProduct_DaysUntilBegins>> >= 5

 

 

 

 

<<Account_IDAccount>> < 0

 

<<Participant_IDParticipant>> < 0

 

What these can be used for: NEW Accounts/Participants are tagged with a negative ID until they are confirmed.  So an Account is negative if they select “New User”.  A participant is negative if it is a brand new account, or if they are adding a new participant to a confirmed account.  Good way to give something to “First-Time” users

 

 

 

<<Account_Balance>> > 0

 

<<Participant_Balance>> > 0

 

What these can be used for: You can put up a page that wont let them continue to register if they have an outstanding balance, can be effective, especially if you only have “Force Login” forms.

 

 

<<CartParticipant_IDCategoryOptionHistory>>

and

<<%_FinancialOptionHistory>>

Can be used to see if these things have been previously selected or purchased, has a variety of uses.  Is referenced in the format:

'######' in <<CartParticipant_IDCategoryOptionHistory>> or '######' in <<%_FinancialOptionHistory>> where the ###### is the ID of the specific category option or financial option you want to know if they have previously chosen.  This looks in the prefixs entire history and not just the current registration instance.

 

 

<<%_EventAssignmentNumber_AmtOrderGL>> - The assignment number of this event for participant in the data center and cart. Order is greatest to least on amount purchased. The most expensive event would be 1, second most expensive event 2, etc.

 

<<%_EventAssignmentNumber_AmtOrderLG>> - The assignment number of this event for participant in the data center and cart. Order is least to greatest on amount purchased. The least expensive event would be 1, second least expensive event 2, etc.

 

EXAMPLES:

Apply to every event but the most expensive

!(<<CartParticipant_EventAssignmentNumber_AmtOrderGL>> == 1)

 

(<<Cart_EventAssignmentNumber_AmtOrderGL>> == 1) && (<<Cart_ParticipantAssignmentNumber_SignupOrder>> == 2)

1st = $90

2nd = $100

2nd gets Discount

 

1st = $100

2nd = $90

No Discount

 

(<<Cart_EventAssignmentNumber_AmtOrderLG>> == 1) && (<<Cart_ParticipantAssignmentNumber_SignupOrder>> == 2)

1st = $90

2nd = $100

No Discount

 

1st = $100

2nd = $90

2nd gets Discount

 

 

(<<Cart_EventAssignmentNumber_AmtOrderGL>> == 1) && (<<Account_ParticipantCount>> == 2)

1st = $90

2nd = $100

2nd gets Discount

 

1st = $100

2nd = $90

1st gets Discount

 

(<<Cart_EventAssignmentNumber_AmtOrderLG>> == 1) && (<<Account_ParticipantCount>> == 2)

1st = $90

2nd = $100

1st gets Discount

 

1st = $100

2nd = $90

2nd gets Discount