> 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/core-concepts.md). # Core Concepts DC Works combines data storage, user interfaces, workflow logic, and deployment tools into a single no-code platform. Before building more advanced solutions, it is helpful to understand how these components work together. A well-planned DC Works solution begins with the workflow and the data—not with the screen layout. ### The basic structure A typical DC Works solution follows this structure: ```mermaid flowchart TD P["Plan the workflow"] --> D["Structure the data"] D --> A["Build Applets"] A --> S["Organize Applets into Suites"] S --> R["Run on devices or as Web Apps"] ``` * **Databases and tables** store the information. * **Applets** allow users to capture, view, and update that information. * **Suites** organize one or more Applets into a launcher. * **Devices and Web Apps** provide access to the Suite. * **Actions and conditions** control what happens as users move through the workflow. ### Plan before you build Planning the solution before opening the Designer is one of the most important parts of building successfully in DC Works. Before you begin, consider: * What process or problem is the solution intended to address? * What information needs to be collected or displayed? * How should that information be organized into tables? * What steps will users follow? * What decisions or conditions affect the workflow? * Which users or devices will run the solution? * Does the solution need to operate without a network connection? The structure of the data affects almost every part of the solution. Taking time to plan the workflow and its information at the beginning can prevent unnecessary rebuilding later. {% hint style="info" %} Start by describing the real-world workflow in plain language. Then identify the information created, viewed, or changed during each step. {% endhint %} ### What you will learn This section provides short introductions to: * How DC Works is organized * Databases, tables, and records * Applets and Suites * Records and data binding * Actions, conditions, and workflows * Pages and navigation * Devices, Web Apps, and deployment * Offline operation and synchronization * Planning a solution before you build * DC Works design best practices These pages provide the foundation needed to understand DC Works. The later sections of this documentation explain each feature and configuration process in greater detail. ### Using the Getting Started example The **Getting Started** database, **Asset Check-In** Applet, and **Getting Started** Suite will continue to serve as examples throughout this section. Later in the documentation, you may build a new solution from scratch to apply these concepts without relying on an automatically generated Applet. ### Next Continue to **How DC Works Is Organized** for an overview of the main DC Works components and their relationships. --- # 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/core-concepts.md?ask=&goal= ``` `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.