> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/add-objects-to-forms.md).

# Add objects to forms

You can link a form to an object during work execution.

This keeps inspection or maintenance data tied to the right asset.

### Why this matters

Object-linked forms help you:

* keep a clear service record
* separate forms per asset
* review object-related documentation later

{% stepper %}
{% step %}

### Open the work order form

Open the relevant form from the work order.
{% endstep %}

{% step %}

### Select the object

Use the object field or selector in the form.
{% endstep %}

{% step %}

### Complete the form

Fill in the form for that specific object.
{% endstep %}

{% step %}

### Save the form

Save or send the form.

The form data stays linked to the selected object.
{% endstep %}
{% endstepper %}

### Optional setup

If your process requires it, make object selection mandatory in the form setup.

That prevents forms from being saved without the right object.

### Frequently asked questions

<details>

<summary>Can one form cover multiple objects?</summary>

Usually one form is linked to one object.

Use separate forms when each object needs its own record.

</details>

<details>

<summary>Can technicians choose the object in the app?</summary>

Yes, if the form and app setup supports it.

</details>

<details>

<summary>Does the form appear in the object history?</summary>

That is the usual goal of this setup.

Exact behavior depends on your configuration.

</details>

### Related topics

* [**Add objects to work orders**](/marketplace-packages-and-power-ups/power-ups/object-management/add-objects-to-work-orders.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/add-objects-to-forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.