> 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/suites-and-deployment/add-and-organize-applets.md).

# Add and Organize Applets

Learn how to include Applets in a Suite, create App Buttons that open them, and arrange the Suite launcher for its users.

Adding an Applet to a Suite and displaying it in the launcher are related but separate tasks:

1. Include the Applet in the Suite’s **Applets** selection.
2. Add or configure an **App Button** linked to that Applet.

The Applet must be included in the Suite before users can open it from an App Button.

### Before you begin

Confirm that:

* The required Applets have been created.
* Each Applet has been saved and tested.
* The Suite has been created.
* You know which users or workflow the Suite will support.
* You know which Applets should be most prominent.

Only include Applets that are relevant to the Suite’s purpose.

### Open the Suite Editor

To open the Suite Editor:

1. Open **Suites** from the main navigation.
2. Locate the Suite.
3. Select the Suite name.

The pencil icon beside the Suite changes its name; it does not open the Suite Editor.

### Include an Applet in the Suite

The Suite’s **Info** properties contain the **Applets** selection.

To add an Applet to the Suite:

1. Open the Suite Editor.
2. Select an empty area of the Main Workspace.
3. Select **Info** in the Suite Properties Panel.
4. Open **Applets**.
5. Select the Applet to include.
6. Repeat for any additional Applets.
7. Save the Suite.

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

Use the Applets selection to determine which Applets are included in the Suite.

The Applets list displays Applets that are available to the Suite. For example, it may contain Applets such as:

* Asset Check-In
* Equipment Checkout
* Equipment Lookup

Including an Applet does not change its pages, fields, records, actions, conditions, or appearance.

{% hint style="info" %}
An Applet is designed independently in the Applet Editor. Adding it to a Suite makes it available to the Suite but does not modify the Applet itself.
{% endhint %}

### Understand App Buttons

An **App Button** is an action field that users select to open an Applet.

Each App Button contains a **Linked Applet** property that determines which Applet it opens.

An App Button can also have its own:

* Field name.
* Displayed text.
* Position.
* Size.
* Color.
* Border.
* Text alignment.
* Hidden or disabled state.

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

Select an App Button to configure its displayed text, linked Applet, and appearance.

### Add an App Button

To add an App Button:

1. Select the **+** button beneath **Fields**.
2. Locate **App Button** under **Action** in the Add Fields menu.
3. Click and drag **App Button** into the Main Workspace.
4. Drop it at the desired location.
5. Select the new App Button.
6. Configure its properties.
7. Save the Suite.

### Link an App Button to an Applet

To configure the App Button:

1. Select the App Button in the Main Workspace or Fields list.
2. Open its **Info** properties.
3. Enter a descriptive **Field Name**.
4. Enter the text users should see under **Field Text**.
5. Select the required Applet under **Linked Applet**.
6. Save the Suite.

<figure><img src="/files/1AYJJltQZdZMfhQZPh8w" alt=""><figcaption></figcaption></figure>

Field Text identifies the Applet to users, while Linked Applet determines which Applet opens.

For example:

| Field Text          | Linked Applet      |
| ------------------- | ------------------ |
| Equipment Lookup    | Equipment Lookup   |
| Check Out Equipment | Equipment Checkout |
| Return Equipment    | Equipment Return   |
| Review Equipment    | Equipment Status   |

Use short, action-oriented text that clearly identifies the button’s purpose.

### Distinguish Field Name from Field Text

**Field Name** identifies the App Button inside the Suite Editor.

**Field Text** is the label displayed to Suite users.

For example:

* **Field Name:** Equipment Checkout Button
* **Field Text:** Check Out Equipment

Use descriptive internal field names so that App Buttons are easy to identify in the Fields list.

### Select an existing App Button

Existing App Buttons appear in the **Fields** list.

To modify one:

1. Locate the App Button in Fields.
2. Select it.
3. Change its settings in the Properties Panel.
4. Save the Suite.

Selecting the button directly in the Main Workspace produces the same result.

### Arrange App Buttons

Arrange App Buttons so users can quickly find the Applet required for their task.

Use the App Button’s **Position** and **Size** properties to control its placement and dimensions.

When arranging App Buttons:

* Place frequently used Applets prominently.
* Keep related Applets together.
* Use consistent dimensions.
* Maintain even spacing.
* Avoid overlapping buttons.
* Keep button text readable.
* Design for the intended device or Web App dimensions.

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

Arrange App Buttons according to workflow, frequency, or task category.

Detailed position, size, color, and border instructions are provided in **Style and Configure the Suite**.

### Use the Suite layout settings

The Suite’s **Layout** properties control the general horizontal arrangement of its fields.

To open the layout settings:

1. Select an empty area of the Main Workspace.
2. Select **Layout** in Suite Properties.
3. Select the required horizontal alignment or spacing option.
4. Review the arrangement.
5. Save the Suite.

Available options allow fields to be aligned or distributed across the Suite’s available width.

Use Suite-level layout settings for the general arrangement, then adjust individual App Button properties where needed.

### Organize Applets by workflow

When a Suite contains several Applets, arrange them according to how users perform their work.

For example, an equipment-management Suite might present Applets in this order:

1. Equipment Lookup
2. Check Out Equipment
3. Return Equipment
4. Update Equipment
5. Review Equipment Status

A warehouse Suite might group Applets by operation:

* Receiving.
* Putaway.
* Picking.
* Cycle counting.
* Shipping.

Keep each Suite focused on a related group of tasks. Create separate Suites when different user groups require substantially different Applets.

### Use hidden or disabled App Buttons

App Button properties include **Hidden** and **Disabled**.

Use **Hidden** when the button should not be displayed.

Use **Disabled** when the button should remain visible but unavailable for selection.

These settings can help control which operations are available in a particular Suite configuration.

Confirm the resulting behavior on an enrolled device or as a Web App.

### Change an App Button’s linked Applet

To assign a different Applet:

1. Select the App Button.
2. Open its **Info** properties.
3. Change **Linked Applet**.
4. Update **Field Text** if necessary.
5. Save the Suite.
6. Test the button.

Confirm that the newly linked Applet is included in the Suite’s **Applets** selection.

### Remove an App Button

Remove an App Button when users should no longer see that launcher control.

Before removing it:

* Confirm that it is no longer needed.
* Determine whether another App Button opens the same Applet.
* Review the Suite’s workflow.
* Confirm that users will not lose access to a required task.

Removing an App Button affects the Suite launcher. It does not delete the underlying Applet.

{% hint style="info" %}
Removing an App Button does not delete its linked Applet. The Applet remains available in the Applets workspace unless it is deleted separately.
{% endhint %}

### Remove an Applet from the Suite

When an Applet should no longer be included:

1. Review any App Buttons linked to it.
2. Remove or relink those App Buttons.
3. Select an empty area of the Main Workspace.
4. Open **Suite Properties > Info**.
5. Open **Applets**.
6. Remove the Applet from the Suite’s selection.
7. Save and test the Suite.

Removing an Applet from the Suite does not delete the underlying Applet or its associated data.

### Save and test the Suite

Save the Suite after:

* Adding or removing an Applet.
* Adding or removing an App Button.
* Changing Field Text.
* Changing a Linked Applet.
* Rearranging App Buttons.
* Changing the Suite layout.

Because the Suite Editor does not have a Play or test-run control, test the Suite on an enrolled Android device or as a Web App.

Confirm that:

* All required App Buttons appear.
* Button labels are clear.
* Each button opens the correct Applet.
* Applets appear in a logical order.
* Buttons fit the intended screen.
* Users can navigate back to the Suite launcher.

### Next

Continue to **Style and Configure the Suite** to learn how to adjust its layout, background, logo, fields, App Buttons, and loading indicator.


---

# 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/suites-and-deployment/add-and-organize-applets.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.