Determine Account / Premise Dependency For Each Column Reference

Later in the design process (see Determine How The Campaign Behaves), you define on the campaign whether an account (and premise) is required, optional or not allowed on its orders. Your selection impacts how you setup column references. This is a little complicated so let's use an example:

• Assume you've setup a campaign to indicate a premise can optionally be defined on its orders.
• If the order-taker doesn't define a premise on an order, any premise-oriented questions and miscellaneous fields (Q&MF) should be suppressed on the order.
• It's easy for the system to know which Q&MFs to suppress when a Q&MF's response is held in a characteristic (because you must define on the campaign if the response will reside in an account, premise, person or order characteristic). For column reference Q&MFs, the system doesn't know if the response is account-oriented, premise-oriented or neither because algorithms handle the validation / updating of the response.
• Therefore, when you use column references on a campaigns Q&MFs, you must define if the responses are account-oriented or premise-oriented (so that the system can suppress the Q&MF when the user doesn't enter an account or premise on the order).

The following table contains the column references defined above as well as their dependency

You'll notice that each column reference is account-oriented (this is because automatic payment fields are stored on the respective account).