Skip to Content
OperationsJob Attributes

Job Attributes

Overview

Job attributes let your organization capture details that are important to your work but are not covered by standard job fields. Attributes can appear during job creation, job editing, and template setup depending on how they are configured.

Use attributes for structured information that users should enter consistently. Attributes can also be referenced by job templates to build consistent job descriptions.

Attribute List

The attribute list shows the custom job fields available to your organization. Use it to add new attributes, update existing ones, archive attributes that are no longer useful, or unarchive attributes that should be used again.

Each row shows the attribute name, unit when one is configured, and slug in braces. Before adding an attribute, check whether FieldWRX already has a standard field for that information. Duplicating standard fields can confuse users and make reporting less reliable.

Create an Attribute

Create an attribute when a job needs a repeatable data point that should be captured in a consistent format.

When setting up an attribute, define:

  • The attribute name users will see.
  • The slug used in job description templates.
  • The input type. The input type determines how users enter the information and what options are available for the attribute.
  • The unit, when the value should be displayed with one.
  • The option list, when the input type is Select.

Select options:

Options for a given attribute can be added and edited but not removed once the attribute is in use. This is to avoid breaking existing job records that reference the option.

Input type options

  • Text: Short free-form values.
  • Number: Numeric values, optionally displayed with a unit.
  • Select: A controlled list of options, optionally displayed with a unit.
  • Employee select: A selected employee value.

Slug

The slug is the template-safe identifier for the attribute. FieldWRX uses slugs in description templates with double-brace syntax, such as {{casing-size}}.

Slugs must be lowercase alphanumeric text with dashes. Keep them stable after templates are using them, because changing a slug can affect description templates that reference it.

Avoid using free-form text when the value should be one of a known set of choices. Consistent values are easier to search, filter, and report on.

Job TemplatesOverview