> 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/actions-conditions-and-workflows.md).

# Actions, Conditions, and Workflows

Pages, fields, and records provide the structure of an Applet. **Actions** and **conditions** control what the Applet does and how users move through the process.

Together, they create a workflow.

```mermaid
flowchart LR
    E["User or Applet Event"] --> A["Action"]
    A --> C{"Condition"}
    C -->|Met| Y["Continue Workflow"]
    C -->|Not met| N["Alternate or No Action"]
```

### Actions

An **action** tells DC Works to perform an operation.

Actions can be used to:

* Set or change a record value.
* Retrieve information from a table.
* Add or update table data.
* Navigate to another page.
* Respond to user input or another event.

An action may be initiated by a user, such as selecting a button, or automatically when an event occurs.

### Conditions

A **condition** evaluates information to determine whether part of the workflow should proceed.

For example, a condition might check whether:

* A required value has been entered.
* A scanned item exists in a table.
* A quantity is greater than zero.
* A status matches a particular value.
* A previous step was completed successfully.

Conditions allow the Applet to respond differently depending on its data or the user’s input.

### Building a workflow

A workflow is created by combining fields, records, actions, and conditions in a logical sequence.

For example:

```mermaid
flowchart TD
    S["Scan Asset"] --> R["Set Record Value"]
    R --> C{"Asset Found?"}
    C -->|Yes| D["Display Asset"]
    C -->|No| M["Show Message"]
```

A workflow may be simple, such as saving a form, or may include multiple pages, decisions, and table operations.

### Plan the workflow first

Before configuring actions and conditions, describe the intended process in plain language.

Consider:

* What begins the workflow?
* What information is needed?
* What should happen at each step?
* What decisions must be made?
* What happens when a condition is not met?
* When should information be saved to a table?
* How does the workflow end?

Planning these steps first makes it easier to determine which records, pages, actions, and conditions the Applet will require.

{% hint style="info" %}
Actions perform operations. Conditions determine whether those operations—or the next steps in the workflow—should occur.
{% endhint %}

### The Getting Started example

In the **Asset Check-In** Applet, actions move information between Applet records and the Asset Check-In table.

Conditions can be added to validate that the required information is available before a new entry is recorded.

The detailed configuration of individual actions and conditions will be covered later in the **Applets** section.

### Next

Continue to **Pages and Navigation** to learn how pages organize the steps of an Applet and guide users through its workflow.


---

# 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/actions-conditions-and-workflows.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.