> 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.md). # Suites and Deployment Applets contain the pages, fields, records, actions, and conditions that perform individual tasks. A Suite brings one or more Applets together and provides the interface through which users open them. An Applet must be included in a Suite before it can be made available to users. ```mermaid flowchart TD A["Completed Applets"] --> S["Configured Suite"] S --> D["Enrolled Android devices"] S --> W["Web Apps"] ``` A Suite groups completed Applets and provides access to them on supported runtime platforms. ### Understand Suites A Suite acts as the launcher for a collection of Applets. For example, an equipment-management Suite might contain separate Applets for: * Looking up equipment. * Checking out an item. * Returning an item. * Reviewing equipment status. * Updating equipment information. Grouping related Applets gives users a single starting point for completing connected tasks. A Suite can also define: * Its name and logo. * How Applets are presented. * The arrangement of its interface. * Background colors and images. * Suite-level actions. * Whether user login is required. * Offline-support behavior. * Automatic updates. The Suite controls how users access the Applets. The pages, data binding, and workflow logic remain configured within the individual Applets. ### Understand the deployment process The basic DC Works deployment process is: 1. Create the required database tables and Applet records. 2. Build and test the Applets. 3. Create a Suite. 4. Add the Applets to the Suite. 5. Configure and save the Suite. 6. Make the Suite available on an enrolled Android device or as a Web App. 7. Test the complete solution on its intended platform. This chapter begins after the Applets have been created and tested. {% hint style="info" %} The **Getting Started** section introduced this process by creating a basic Suite and running it on a device or as a Web App. This chapter provides more detailed information about Suite configuration, organization, appearance, testing, and deployment. {% endhint %} ### Choose a deployment method Suites can be made available through two primary runtime methods. | Deployment method | Description | | ------------------ | ------------------------------------------------------------------------------------- | | **Android device** | Runs the Suite through the native DC Works application on an enrolled Android device. | | **Web App** | Runs the Suite through a supported web browser using an assigned Web License. | The same Applets can be organized into Suites for different users, tasks, or deployment environments. #### Android devices Device deployment is intended for users running Suites through the native DC Works application. This deployment method supports device-oriented workflows that may use: * Hardware barcode scanning. * Camera and image capture. * Keyboard input. * Sound. * Printing. * Offline operation and synchronization. * Other device-dependent features. The device must be enrolled before it can receive and run its assigned Suite. #### Web Apps Web App deployment allows users to run a Suite through a web browser without using the native Android application. A Web App deployment requires the applicable user, Web License, and Suite assignment. Users then sign in through the organization’s DC Works Web App address. Web Apps are useful for workflows performed from desktop computers, laptops, tablets, or other devices with a supported browser. {% hint style="info" %} n Applet may behave differently depending on the deployment platform. Test scanner, camera, printing, offline, and other device-dependent functions on the intended hardware. {% endhint %} ### Design Suites for their users A Suite should contain the Applets required by a specific user group or operational process. When planning a Suite, consider: * Which Applets the users need. * The order in which Applets should appear. * Whether different roles require different Suites. * Whether the Suite will run on Android devices, as a Web App, or both. * Whether the workflow requires user login. * Whether the Suite must support offline operation. * Which Applets should be easiest to find. * Whether the layout fits the intended screen dimensions. Avoid placing unrelated Applets in the same Suite. A focused Suite is easier to navigate and reduces the chance that users will open the wrong Applet. ### Configure Suites in the Suite Designer The Suite Designer is used to configure the Suite interface and its contents. Within the Suite Designer, you can: * Add Applets. * Add and configure Suite fields. * Arrange the Suite layout. * Upload a logo. * Configure backgrounds. * Configure launch actions. * Modify the properties of selected elements. * Save Suite changes. The Suite Designer’s **Toolbox** is used to add new elements by dragging them onto the layout. The **Fields** panel lists and manages elements that have already been added. When no Applet, logo, or field is selected, the Suite Properties include: * **Info** * **Layout** * **Background** * **Actions** Detailed instructions for these areas are provided throughout this chapter. ### Test a deployed Suite The Suite Designer does not include a Play button or built-in test mode. To test a Suite, run it: * On an enrolled Android device; or * As a Web App. Testing should confirm that: * The Suite loads correctly. * Its logo, background, and layout appear as intended. * All required Applets are present. * Applet names and icons are clear. * Each Applet opens correctly. * Users can return to the Suite interface. * Suite-level actions execute as intended. * Updates reach the intended users. Test the Suite on each platform and screen size on which it will be used. ### In this chapter This chapter explains how to: * Use the Suite Designer. * Create and configure a Suite. * Add and organize Applets. * Style the Suite interface. * Deploy a Suite to an Android device. * Deploy a Suite as a Web App. * Test and update a deployed Suite. ### Next Continue to **Suite Workspace Overview** to learn about the Suite Designer workspace, panels, properties, and available configuration tools. --- # 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.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.