Attribute Module is the type of record that an attribute can be attached to. An attribute is one mechanism reused across the system rather than a feature of any single record, so the same category and attribute definitions, the same data types, and the same way of recording a value apply whether the attribute sits on a student, a household, a donation or an action.
Every module works the same way. An administrator defines a Category and then the Attributes inside it, each with a Data Type of Text, Integer, Date, Boolean or Hyperlink, and optionally a Lookup Type so the value is chosen from a list. A user then records a value on an individual record. Please review Attribute, Attribute Category, Creating Attribute and Recording Attribute - Individual for the shared steps.
The order fields appear in follows the category order first and the attribute order inside it, both set with the Reorder buttons on the setup page.
Where attributes are defined
Note: attributes for inquiries, inquiry actions and event categories are defined from Admissions, Administrative Settings.
Where attributes are recorded
An action is a record in its own right, so it carries attributes the same way a student does. The difference is what the value describes: an attribute on a student describes the student and holds one value at a time, while an attribute on an action describes that one event, so a student may hold as many values as there are actions. A school recording community service enters the activity, the hours and a description on each action rather than on the student. Please review Student Action for the fields an action carries, and CMS Widget - Actions for collecting the values through a portal page.
Note: attributes are defined for the school as a whole and are offered on every action. A portal page limits which of them a student sees through the widget settings.