> 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.md).

# DC Works

Learn how to create, manage, and deploy no-code data collection and workflow applications on devices with AML’s DC Works platform.

DC Works is AML’s no-code platform for creating and deploying data-collection and workflow applications. DC Works runs natively on Android devices, while the DC Works Web App allows Suites and Applets to run through a compatible web browser on PCs, Apple devices, and other supported platforms. 

Using the web-based DC Works Designer, organizations can build applications for tasks such as inventory, receiving, inspections, asset tracking, order picking, check-in/check-out, maintenance, and other operational workflows.

Applications created in DC Works can collect, display, and update information in cloud-hosted databases while providing users with a purpose-built interface on their devices.

## How DC Works is organized

DC Works is built around four principal elements:

* **Applets** are the individual applications (consisting of pages) used to perform a task.
* **Suites** group related Applets together for deployment.
* **Devices** receive and run the Suites assigned to them.
* **Databases and Tables** store the information used and collected by Applets.

```mermaid
graph LR
 
    A["Create Applets"] --> B["Group into Suites"]
    B --> C["Deploy to Devices"]
    C --> D["Collect and update data"]
```

## What you can do with DC Works

DC Works can be used to:

* Create custom data-entry and scanning workflows.
* Collect barcode, text, numeric, date, image, and other field data.
* Display and update records stored in DC Works tables.
* Apply actions and conditions to control how an Applet behaves.
* Group Applets into Suites for different users or operational functions.
* Deploy Suites to licensed devices.
* Continue collecting certain data while a device is temporarily offline.
* Synchronize collected information with the DC Works cloud environment.

## Where should I start?

If you are new to DC Works, begin with **Getting Started**. It will guide you through the basic process of signing in, creating your first Applet, adding it to a Suite, and deploying it to a device.

* **Getting Started** — Create and deploy your first simple application.
* **Core Concepts** — Understand the principal components of DC Works.
* **Applets** — Design the screens and workflows used on devices.
* **Suites** — Organize Applets and prepare them for deployment.
* **Databases and Tables** — Create and manage the underlying data.
* **Deployment** — Assign Suites and configure devices.
* **Administration** — Manage users, devices, licenses, and system settings.
* **Reference** — Find detailed information about fields, actions, conditions, and other features.

## Who is this documentation for?

This documentation is intended for:

* DC Works administrators
* Applet designers
* Operational managers
* IT personnel
* Device users and supervisors

No programming experience is required to create basic Applets, although familiarity with databases, workflows, and conditional logic can be helpful when building more advanced solutions.

## Additional learning resources

For video tutorials, examples, templates, and other learning material, visit the **DC Works section of AML Know-How**.


---

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