Attributes

Attributes

About Attributes

Attributes represent additional data to capture for a unit or on a transaction. PanatrackerST includes several pre-defined system attributes used for standard reporting. Attributes can be assigned to transactions, item templates, container setup, project templates, shipping templates, and maintenance templates.

You can add attributes at any time, but it's best to define them before setup so you know where they'll be assigned.

Create a New Attribute

  1. Go to Settings on the left menu and select Attributes.
  2. Review the list of current attributes in the grid view.
  3. Select New Attribute to open the create screen.

Create Attribute screenCreate Attribute screen: define the name, label, help text, and data type

  • Name: The database name for the attribute.
  • Label: The display name shown to users. The name and label can be the same.
  • Help Text: Optional text displayed below the attribute field during transactions. Use this to provide a fuller description when the label is abbreviated.
  • Data Type: Select the data type for the attribute:
    • Text
    • Date
    • Integer
    • Memo
    • Dropdown List
    • Text Editor
    • Checkbox
    • DateTime
    • Currency

Where Attributes Can Be Assigned

When creating attributes, define where each one can be used. This limits the available attributes in each context and avoids confusion about the attribute's intended purpose.

Item Master

Attributes assigned to the item master record. This data applies to all units of that item code. Examples: model, manufacturer.

Serialized Item Units

Attributes specific to each individual serial-tracked item. Examples: serial number, warranty end date.

System attributes available:

  • SystemWarrantyEndDate
  • SystemWarrantyStartDate
  • SystemSerialNumber

Lot Item Units

Attributes associated with the item-lot combination. Attribute data assigned to an item-lot is inherited if additional quantities are added later. For example, if ITEM-A / LOT123 has a color attribute set to "blue," adding more of that item-lot later displays the color as read-only with the value "blue."

Lot Expire Date and Lot Manufacture Date are system fields enabled by item template rules. You do not need to create separate attributes for these.

Transactions

Many transactions support header-level attributes. For example, create a "Vendor Packing List Number" attribute to capture on PO Receiving or Receive New Unit transactions.

Available transactions:

  • Receive New Unit
  • PO Receive
  • Check Out
  • Check In
  • Receive Transfer
  • Usage
  • Unit Return
  • Deploy Unit
  • Order Pick

Transactional Templates

Attributes create forms and checklists for transactions like Place-In-Service and Unit Maintenance. Attributes can also be captured on transactions based on the item category (configured under the attribute tab on item templates). This builds historical data: for example, capturing a condition at check-in for specialty equipment lets you generate condition history reports.

Available transactions:

  • Create
  • Receiving
  • Allocate to Project
  • Build Shipment
  • Build Unit (for the master unit)
  • Check In
  • Check Out
  • Deploy Unit
  • Dispose Unit
  • Maintenance
  • Place-In-Service
  • Retire Unit
  • Return Unit
  • Transfer Ownership
  • Transfer Site Location
  • Usage

Movable Containers

Attribute data can be captured on movable containers since they are also serialized units. Project and PO Number reference data is managed using a container template rule option.

Projects

Define additional attributes for projects or jobs: for example, a contract number or billing account. Standard project fields include Customer and Location.

System attribute available:

  • SystemProjectStartDate

Shipments

Shipment templates are required for transfer or customer orders. Define additional data fields based on the type of shipment.

System attributes available:

  • SystemBOLNumber
  • SystemFreightBillTo
  • SystemFreightChargeTerms
  • SystemShipDate
  • SystemSpecialInstructions
  • SystemUNNumber

Group Templates

Grouping lets you tag serialized items with a group ID for reporting. A common use is grouping assets by a financial asset record ID. For example, 30 laptops received under one purchase order share a single financial record for depreciation. The asset record becomes the Group ID while each laptop is tracked individually in PanatrackerST, supporting audit requirements. Add attributes to the group template to track additional data.


Attribute assignment overviewAttribute assignment overview


    • Related Articles

    • Reclassify Unit Transaction

      This transaction reassigns an existing unit to a different Item Master. Common use cases include correcting a unit that was received under the wrong item master, or consolidating units when duplicate item masters exist for the same item. This ...
    • Templates

      Templates define rules and attributes (data to capture) for various parts of the system. Templates must be set up before creating the records that depend on them. Templates are required for: Items — Item templates define rules and attributes for item ...
    • Item Master Setup

      Before adding Item Master records, define your item templates. Item templates control how each item is tracked: by unique handle (serial) or by quantity, along with rule and attribute assignments. About Item Masters Item Masters are often referred to ...
    • Release Notes for May 2022

      The mid-May release included the following enhancements: Item Master Attributes on Grid Views — Added the ability to define item master attributes to display in the Item Master, Item Stock Level, and Below Min Quantity grid views. Configure under ...
    • Unit Maintenance

      Record maintenance activities for any serialized unit with the Track Maintenance Activities for this Item rule enabled on its item template. All maintenance is completed against a maintenance template. Set up all maintenance activities regardless of ...