> 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/review-the-suite-structure.md).

# Review the Suite structure

### The Suite Designer

The Suite Designer contains three principal areas:

* The left panel contains the Suite’s fields and the toolbox.
* The center canvas displays the Suite launcher.
* The right properties panel displays settings for either the entire Suite or the currently selected field.

<figure><img src="/files/XglT5inJaOtkqmUgGPbs" alt=""><figcaption></figcaption></figure>

*The Getting Started Suite displayed in the Suite Designer.*

The toolbar above the canvas also provides controls for viewing and adjusting the design workspace.

### Suite fields

Select **Fields** in the left panel to view the elements currently included in the Suite.

The template initially contains the **Asset Check-In** launcher button created from the Applet selected during Suite creation.

Select a field in the left panel or directly on the canvas to display its properties.

<figure><img src="/files/fOKR9dfLMSoSrharM8li" alt=""><figcaption></figcaption></figure>

*The Fields panel lists the elements placed on the Suite launcher.*

### Suite properties

When no Applet button, logo, or other field is selected, the right panel displays the general **Suite Properties**.

The properties are organized into four tabs:

* **Info** — Controls the Suite’s general configuration and behavior.
* **Layout** — Controls how fields are organized within the Suite.
* **Background** — Changes the Suite’s background color, adds a background image, and sets the loading indicator color.
* **Actions** — Configures specific actions to run when the Suite launches.

<figure><img src="/files/Qm5a1iqY08B8JqCKqVHJ" alt=""><figcaption></figcaption></figure>

When an Applet button, logo, or another field is selected, the right panel changes to display the properties and actions for that specific field.

### Select and position a field

Select the **Asset Check-In** button on the canvas.

A border appears around the selected field, and the right panel changes from **Suite Properties** to **Field Properties**.

You can reposition the selected field by dragging it on the canvas. Its size and placement can also be adjusted through its field settings.

### Field properties

The available properties depend on the type of field selected. For a launcher button, the settings include controls for:

* Field type
* Displayed text
* Position and size
* Text and font appearance
* Border and background styling
* The linked Applet

These settings allow each launcher button to be positioned and styled independently.

### Link a button to an Applet

A Suite launcher button must be linked to the Applet it should open.

For the generated button, the linked Applet is:

`Asset Check-In`

To review or change the connection:

1. Select the launcher button.
2. Locate **Linked Applet** in the Field Properties panel.
3. Select the Applet the button should open.

<figure><img src="/files/qYhHpXSHrhVUfuhBYTw0" alt=""><figcaption></figcaption></figure>

*The Linked Applet property determines which Applet opens when the user selects the button.*

{% hint style="warning" %}
Adding a button to the launcher does not by itself determine which Applet it opens. Confirm that the correct Applet is selected under Linked Applet.
{% endhint %}

### Fields and Toolbox

The left panel contains two tabs for managing the fields in the Suite:

* **Fields** — Displays fields already added to the Suite. Select a field here to locate it, view its properties, or modify it.
* **Toolbox** — Contains the field types that can be added to the Suite.

#### View or modify an existing field

1. Select **Fields** in the left panel.
2. Select the desired field from the list.
3. Modify it using the field properties displayed in the right panel.

You can also select a field directly on the Suite layout.

#### Add a field

1. Select **Toolbox** in the left panel.
2. Locate the type of field you want to add.
3. Drag the field type from the Toolbox and drop it onto the Suite layout.
4. Position and configure the new field using the properties panel.

{% hint style="info" %}
Selecting a field type is not enough to add it. Drag the field from the Toolbox and drop it onto the Suite layout.
{% endhint %}

For an Applet launcher field, also confirm that its **Linked Applet** property identifies the Applet that should open when the field is selected.

### Arrange the launcher

Fields can be selected and repositioned directly on the canvas. Use the canvas and Field Properties together to create a clear launcher layout.

When arranging Applet buttons:

* Keep adequate spacing between buttons.
* Use clear, recognizable labels.
* Maintain consistent button sizes and styles.
* Confirm that every button is linked to the intended Applet.
* Consider the screen size and orientation of the devices that will run the Suite.

For this tutorial, the launcher only needs the logo and the **Asset Check-In** button.

### Save the Suite

Changes made in the Suite Designer should be saved using the **Save** control in the upper-right corner.

Saving creates a new revision of the Suite. Save after changing its layout, properties, fields, or linked Applets.

{% hint style="warning" %}
Save the Suite before leaving the Designer or testing it so that the latest changes are included.
{% endhint %}

### Run the Suite

Unlike an Applet, a Suite cannot be tested directly from the Suite Designer. A Suite must be run through one of these methods:

* On an enrolled device
* As a Web App

Before running the Suite, save the latest revision and ensure it is assigned to the appropriate device or Web User.

### Next step

The **Getting Started** Suite now contains the **Asset Check-In** Applet and is ready to be assigned.

Continue to the next guide to assign the Suite to a Web User or Device User and make it available for use.


---

# 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/review-the-suite-structure.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.