An attribute defines a piece of information that you want to gather from a user. For example, the information can be text, integers, dates, or a choice from a predefined list. In Unica Plan, you define attributes to collect these different types of information, and then place them on forms. Then, you can add or more forms to templates as tabs. When users create items, they select a template. Each attribute that is included in the template corresponds to a field or other user interface control on the tabs that collect information.

Standard and custom attributes

Unica Plan delivers a set of standard attributes that can be used to collect information for all marketing objects. The standard attributes include name and description. To collect additional information, you create custom attributes, enable them, and add them to forms.

Before you begin to create custom attributes, Unica Plan attributes can be shared or local, and that they are categorized based on how they can be used on forms.

Shared and local attributes

Custom attributes are either shared or local, depending on whether they can be used repeatedly on different forms or only on a single form.
  • Shared attributes can be imported into and used on any form. You create a shared attribute by clicking Settings > Unica Plan Settings > Template Configuration > Shared Attributes.
  • Local attributes apply to a single form only. You create a local attribute directly on that form by clicking Create a New Custom Attribute.

Attribute categories

Custom attributes are grouped into categories that are based on how they can be used to collect information. The attribute categories follow.

  • Form attributes can be placed on any form.
  • Grid attributes can be used in a grid interface.
The following attribute categories are available when Unica Plan and Unica Campaign are integrated. These attributes collect information that is mapped to Unica Campaign.
  • Campaign attributes can be used in campaign project templates.
  • Cell attributes can be used in Target Cell Spreadsheets.
  • Offer attributes can be used in offer templates. Offer attributes are available when optional offer integration is enabled.

Campaign, cell, and offer attributes are available only as shared attributes.

Marking attributes as required

When you create an attribute, you can specify special behavior characteristics for the attribute, including whether the attribute is Required. When you select this special behavior for an attribute and the attribute is implemented on a form, a red double asterisk (**) appears next to the corresponding field. The system also checks to assure that a value is supplied. Users receive an error if they try to save without selecting a value.

Note: You cannot mark an offer attribute as required. You define special behavior for offer attributes on a form-by-form basis.

Marking attributes and attribute groups as visible based on other attributes

You can define attribute rules that make attributes visible based on a single-select and single-select from database drop-down attribute. You can also make attribute groups visible based on a single-select and single-select from database drop-down attribute. Attribute rules are supported for plan, program, projects, project requests, marketing objects, invoice, and assets. Attribute rules for attribute groups are supported for plan, programs, projects, project requests, marketing objects, invoice, and assets.

To make attributes and attribute groups visible based on other attributes, you must define rules at the form level.

For example, you can configure a form rule to make the State attribute visible if the user selects United States from the Country attribute drop-down list.

Validations of dependent attributes and attribute groups are executed only when the attribute or attribute group is visible after rule evaluation.

For example, if you select any value other than United States for the country, then the State attribute is hidden. Therefore, if there are any validations on it (such as required behavior, check integer only, and so on) , those validations are skipped because the attribute is hidden after rule evaluation.