> 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/getting-started/next-steps.md).

# Next Steps

You have completed the DC Works Getting Started tutorial.

You now know how to:

* Create a database and table.
* Create an Applet from an existing table.
* Review and test the generated Applet.
* Create a Suite.
* Add an Applet to the Suite.
* Enroll a mobile device.
* Run the Suite and Applet on the enrolled device.

Your **Asset Check-In** solution can now create, display, and update records using DC Works.

### Continue to Core Concepts

Before exploring the Applet Designer and other features in greater detail, the next section explains the core concepts behind DC Works.

Understanding these concepts will help you plan solutions correctly and understand how the different parts of DC Works work together.

In **Core Concepts**, you will learn about:

* How DC Works is organized.
* Databases, tables, records, and stored information.
* Applets and their role within a solution.
* Suites and how they organize Applets.
* Records and data binding.
* Actions, conditions, and workflows.
* Pages and navigation.
* Devices, Web Apps, and deployment.
* Offline operation and synchronization.
* Planning a solution before building it.
* Recommended design practices.

Continue to **Core Concepts** to learn how the components introduced in this tutorial fit together.

{% hint style="info" %}
Keep the Getting Started database, Asset Check-In Applet, and Getting Started Suite. They will continue to serve as practical examples throughout the documentation.
{% endhint %}

### After Core Concepts

After completing **Core Concepts**, continue to the detailed product sections to learn how to build and configure:

* Applets
* Suites
* Databases and tables
* Fields and actions
* Conditions and workflows
* Device and Web App deployments


---

# 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/getting-started/next-steps.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.