> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-attributes.md).

# Asset attributes

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/assets/asset-attributes.md).
{% endhint %}

Fill in the register's attributes for a new asset, including a scanned QR code or barcode, or change the attributes of an existing asset or task.

* **Where:** iOS: creating an asset (after the photo, the add-asset flow opens `AssetAttributesVC`), or "Attributes" on an existing asset (the sheet `EditAssetAttributesVC`). Android: creating an asset, or a task's attributes (`AssetAttributesActivity`); the Asset tab of [Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md) edits them in `AssetAttributeBottomSheet`.
* **Who:** the people creating the asset, or who may change it. The screen checks no permission of its own.
* **Feature:** [Asset registers](https://docs.snapfix.com/product/features/assets/asset-registers.md), [Asset codes](https://docs.snapfix.com/product/features/assets/asset-codes.md)

Attributes are the register's fields, set up in [Asset register settings](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md). The web edits them in the attributes dialog on [Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md#attributes-dialog-web), and asks for mandatory ones in "Add an Asset" ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#add-an-asset-web)).

## Layout

* The title: the asset's or task's name (Android's screen title reads "Attributes").
* The register's attributes, grouped under "Attributes" and each other category (such as "Tracking"), one row per rule with its name and its field: a text field for text and number, a date picker for dates, and scan rows for QR, barcode and NFC, each with a scan button and a remove button.
* The button: "Add Asset" on Android; the add button on iOS. Back leaves.

## Inputs

| Field            | Type        | Required                                      | Default                     | Rules and messages                                                                                                                                                                                                                                                     |
| ---------------- | ----------- | --------------------------------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Text, number     | Text        | When the rule is mandatory                    | The current value, or empty | An empty mandatory value stops the save with "Please add mandatory attributes!" (both apps). Android does not trim, so spaces count as a value; iOS trims the value when editing ends.                                                                                 |
| Date             | Date picker | When mandatory                                | The current value, or empty | Android's picker is titled "Select {name}". Stored as a timestamp.                                                                                                                                                                                                     |
| QR code, barcode | Scan row    | When mandatory                                | Empty                       | The scan button opens the [Code scanner](https://docs.snapfix.com/how-the-apps-work/screens/assets/code-scanner.md); the scanned text is the value. Android's prompts read "Scan a QR Code" and "Scan a Barcode Code".                                                 |
| Smart Tag (NFC)  | Scan row    | When mandatory, and only on a device with NFC | Empty                       | Reads the tag's serial. A device without NFC skips the mandatory check for these rows (both apps). Android without NFC: "*Your device doesn't support NFC"; with NFC off: "* Please enable NFC from the settings". iOS without NFC: "Your device doesn't support NFC". |

## Actions

| Action                       | Who                  | What happens                                                                                                                                                                                    | API                                                                                                                                                     |
| ---------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scan a code                  | Anyone on the screen | Opens the [Code scanner](https://docs.snapfix.com/how-the-apps-work/screens/assets/code-scanner.md) (QR or barcode) or the NFC reader (Smart Tag) and fills the row.                            | None                                                                                                                                                    |
| Remove a value               | Anyone on the screen | Clears the row; the change is kept with the save.                                                                                                                                               | None                                                                                                                                                    |
| Add ("Add Asset" on Android) | Anyone on the screen | Checks the mandatory rows, then keeps the values on the device for the new asset or task and continues the flow. On Android, in edit mode the button only closes.                               | Device copy, synced as [`?action=save_pri_jobattribute`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-actionsave_pri_jobattribute) |
| Back                         | Anyone on the screen | New asset: leaves without keeping the values (iOS returns to the list it came from). Existing asset or task: checks the mandatory rows and saves the changed values on the device, then leaves. | Edit: synced as [`?action=save_pri_jobattribute`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-actionsave_pri_jobattribute)        |

Register rules reach the server from the settings screens ([`?action=save_pri_businessjobattributerule`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-actionsave_pri_businessjobattributerule)), not from here.

## States

* **Loading:** none; the rules come from the device copy.
* **Empty:** a register with no rules shows no rows; the flow continues.
* **Error:** the mandatory message above, as a red toast; the screen stays open. A refused camera or an unreadable tag: see [Code scanner](https://docs.snapfix.com/how-the-apps-work/screens/assets/code-scanner.md).
* **No permission:** none on this screen.
* **Offline (mobile):** works offline; the values sync with the asset or task.

## Dialogs and sheets

* The [Code scanner](https://docs.snapfix.com/how-the-apps-work/screens/assets/code-scanner.md) for QR and barcode rows.
* The NFC reader for Smart Tag rows: Android's own sheet with foreground dispatch; iOS's system sheet.
* The date picker.

## Platform differences

| Topic                             | iOS                                                        | Android                                           |
| --------------------------------- | ---------------------------------------------------------- | ------------------------------------------------- |
| Spaces in a mandatory field       | Trimmed when editing ends                                  | Count as a value                                  |
| Save of a new asset               | The add button                                             | "Add Asset"                                       |
| Save of an existing asset or task | Back, or the add button                                    | Back                                              |
| Existing asset's editor           | Sheet `EditAssetAttributesVC`                              | Sheet on the Asset tab, or this screen for a task |
| Scan prompts                      | "Scan a QR Code", "Scan a Barcode", "Scan a QR or Barcode" | "Scan a QR Code", "Scan a Barcode Code"           |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-attributes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
