Determine The Properties Of Every Miscellaneous Field

At this point, you have amalgamated all miscellaneous fields required for the campaign and its packages. Now you have to define the following for each field:

• Prompt On Order. This is the prompt that will prefix the field when the order is taken. The following table provides examples.
• Campaign Applicability. This controls whether the field is optional , required, or only applicable on package(s).
  • A value of required means the order taker must enter a valid value before packages are displayed for selection.
  • A value of optional means the order taker can leave the field blank prior to package selection. You can make an optional field required on individual packages. For example, you would probably make Date of birth required on the Senior package.
  • A value of only applicable on packages is used for fields that are only captured for specific packages. Fields of this type are suppressed prior to package selection. When you setup a package, you indicate if the field is applicable (if so, the user is only prompted for the field if the package is selected).
• Type Of Response. This controls where the field is stored when the order is completed and how it is validated. You have two options: characteristic or column.
  • If a field is a Characteristic, you must define which entity the characteristic value is to be stored on when the order is completed ( Person, Account, Premise or Order ). You must also define the Characteristic Type as this controls the characteristic value entered by the user.
  • If a field's value resides is a column (as opposed to a characteristic value), you must define the column reference. A field's column reference controls three things:
• How the field's value is retrieved. A field's value is retrieved when an existing person / account / premise is referenced on an order.
• How the field's value is validated. A field's value is validated before package eligibility is determined and before the order is completed.
• How the field's value is posted (i.e., updated on the database). A field's value is posted when an order is completed.

• Default Value On Order. This controls whether the order taker is supplied with a default value when an order is created. Note well: for optional and only applicable on package fields, you can specify a different default value on each package.