> For the complete documentation index, see [llms.txt](https://docs.amltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amltd.com/dc-works/applets.md).

# Applets

Applets are the primary building blocks of a DC Works solution. Each Applet provides the pages, fields, records, data, actions, and conditions needed to complete a particular task or workflow.

An Applet might be used to:

* Receive inventory.
* Perform a cycle count.
* Check an asset in or out.
* Complete an inspection.
* Look up or update information.

Applets are created independently and can then be added to one or more Suites for deployment to enrolled Android devices or as Web Apps.

### In this chapter

This chapter follows the general process of planning, building, and managing an Applet, including:

* Planning the Applet and its workflow.
* Preparing the required data structure.
* Using the Applet Editor.
* Creating an Applet.
* Defining table-based records and local records.
* Creating local variables.
* Working with list records.
* Creating and organizing pages.
* Adding and configuring fields.
* Binding fields to records and data.
* Creating actions, events, and conditions.
* Configuring styles and appearance.
* Testing, saving, and publishing Applets.
* Managing existing Applets.

Records and local variables are established near the beginning of the Applet-building process because they determine how fields, actions, conditions, and pages access and exchange information.

An Applet record may be connected to a database table or created as a local record used only within the Applet. Local variables can also be created for individual values needed by the Applet’s workflow.

{% hint style="info" %}
If you are new to DC Works, review **Core Concepts** before continuing. It explains how Applets, Suites, records, tables, actions, and conditions work together.
{% endhint %}

### Next

Continue to **Plan Your Applet and Workflow** to define the Applet’s purpose, users, process steps, data requirements, and expected results before beginning its configuration.


---

# 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://docs.amltd.com/dc-works/applets.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.