> 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/mobile-app/ios-outsmart-app/module-overviews/work-order/objects/object-history.md).

# Object History

## Object History

Use **Object History** to review previous activity for an asset.

History can switch between work-order and form views when both are enabled.

### What you can do

* review history filtered by object context
* switch display type when the segmented control is shown
* open related work orders, PDFs, or forms

{% stepper %}
{% step %}

### Open the object

Open the object you want to inspect.
{% endstep %}

{% step %}

### Open **History**

Open **History** from the object screen.
{% endstep %}

{% step %}

### Review previous activity

Use the available filters and open the entries you need.

Switch the display type when the screen shows multiple history views.
{% endstep %}
{% endstepper %}

### Keep in mind

History visibility depends on the object data and current setup.

Opening a work order can use the normal preview or the workflow preview.


---

# 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/mobile-app/ios-outsmart-app/module-overviews/work-order/objects/object-history.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.