> 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/create-and-configure-a-suite.md). # Create and Configure a Suite Learn how to create a Suite, select its initial launcher design, add Applets, and configure its access, offline, update, and loading settings. A Suite groups one or more Applets into an interface that can be deployed to enrolled Android devices or made available as a Web App. Before creating a Suite, create and test the Applets that it will contain. ### Before you begin Confirm that: * The required Applets have been created. * The Applets have been saved and tested. * You know whether the Suite will run on Android devices, as a Web App, or both. * You know whether users must sign in. * You know whether offline operation is required. * A suitable logo is available, if the Suite will display one. The Applets can be changed later, but establishing the Suite’s purpose first makes its layout and deployment settings easier to plan. ### Create a Suite To begin creating a Suite: 1. Open **Suites** from the main navigation. 2. Select **Create Suite +**. 3. Select a launcher template. 4. Enter the Suite name. 5. Configure the initial Suite settings. 6. Upload a logo if required. 7. Select the Applets to include. 8. Select **Create**. ### Select a launcher template A launcher template provides the Suite’s initial layout and appearance. Choose a template that suits: * The number of Applets being included. * The intended device dimensions. * The desired icon or button size. * Whether the Suite will display a logo. * The preferred light or dark appearance. The template provides a starting point. Its fields, layout, background, logo, and other properties can be modified later in the Suite Editor. In the **Getting Started** example, the Suite was created using the **Blank Launcher** with the **Dark**, **Small Icons**, and **Logo** options.
Select a launcher design that provides an appropriate starting structure for the Suite. ### Name the Suite Enter a descriptive Suite name that identifies its users, location, or workflow. Examples include: * Equipment Checkout * Warehouse Operations * Receiving * Cycle Counting * RMA Processing * Store Operations The Suite name appears in the Suites workspace and identifies the Suite during assignment and deployment. To rename the Suite after it has been created, return to the Suites list and select the pencil icon beside its name. ### Configure the initial Suite settings The Suite-creation process includes settings that control user access, offline operation, and updates. These settings can also be changed later from **Suite Properties > Info**. #### Require User Login Enable **Require User Login** when users must authenticate before accessing the Suite. Use this setting when access must be associated with an individual user or when the workflow should not be available without signing in. Leave it disabled when the Suite is intended to open without requiring an additional user login. #### Offline Support Enable **Offline Support** when the Suite must support operation without a continuous network connection. Offline support is useful in locations where wireless coverage may be unavailable or unreliable. The Applets, records, actions, and tables used by the Suite must also be planned and configured appropriately for offline operation. #### Auto Update Enable **Auto Update** when deployed instances should receive updated Suite configurations automatically. This setting is useful when the Suite or its included Applets will continue to be revised after deployment. After changing a deployed Suite, test that the updated configuration reaches the intended devices or Web App users. #### Show Loading Indicator Enable **Show Loading Indicator** when users should see a visual indicator while the Suite launcher is loading. The loading-indicator color can be configured under **Suite Properties > Background**. Choose a color that remains visible against the Suite background. ### Add Applets during creation Use the **Applications** selection to choose the Applets initially included in the Suite. To add an Applet: 1. Open the Applications selection. 2. Locate the required Applet. 3. Select the Applet. 4. Repeat for any additional Applets. 5. Review the selected Applets before creating the Suite. In the Getting Started example, the **Asset Check-In** Applet was added to the **Getting Started** Suite. An Applet must already exist before it can be selected for a Suite.
Select the Applets that users should be able to open from the Suite. Additional Applets can be added after creation. Detailed instructions are provided in **Add and Organize Applets**. ### Add a Suite logo Upload a logo when the Suite launcher should display company, department, customer, or workflow branding. Choose an image that: * Remains clear at the intended screen size. * Provides sufficient contrast with the background. * Does not obscure App Buttons or other fields. * Uses an appropriate aspect ratio. * Contains only the branding required for the Suite. After the Suite is created, select the Image field containing the logo to adjust its size, position, and appearance. ### Complete Suite creation Review the selected template, name, settings, logo, and Applets before creating the Suite. Select **Create** to generate the Suite. After creation: 1. Locate the Suite in the Suites workspace if it does not open automatically. 2. Select the Suite name to open the Suite Editor. 3. Review the generated layout. 4. Confirm that the selected Applets and logo are present. 5. Adjust the Suite properties as needed. 6. Save the Suite. ### Configure Suite Info properties To display the Suite’s overall properties: 1. Open the Suite Editor. 2. Select an empty area of the Main Workspace. 3. Select **Info** in the Properties Panel. The Info properties include: * **Applets** * **Require User Login** * **Offline Support** * **Auto Update** * **Show Loading Indicator**
Use the Info properties to modify the Applets included in the Suite and its primary runtime settings. #### Change the included Applets Use **Applets** to change which Applets are included in the Suite. Adding an Applet makes it available for use by an App Button. Removing an Applet from the Suite does not edit the Applet’s internal pages, fields, records, or actions. After changing the included Applets, review the App Buttons and their **Linked Applet** properties. #### Change Suite behavior Enable or disable **Require User Login**, **Offline Support**, **Auto Update**, and **Show Loading Indicator** as required. Save and retest the Suite after changing any runtime setting. ### Configure the initial layout After creating the Suite, review how its Applets and other fields are arranged. Confirm that: * The logo is clearly displayed. * App Buttons are easy to locate. * Button text identifies the linked Applets. * Frequently used Applets are prominent. * The layout fits the intended screen dimensions. * The background provides sufficient contrast. * The Suite does not contain unnecessary elements. Detailed layout and appearance instructions are provided in **Style and Configure the Suite**. ### Save the Suite Select the save control in the Taskbar after creating or modifying the Suite. Save after: * Changing the Applets included in the Suite. * Changing access or offline settings. * Enabling or disabling Auto Update. * Changing the loading-indicator setting. * Adding or modifying the logo. * Rearranging Suite fields. * Changing App Button links. {% hint style="info" %} The Suite Editor does not provide a Play or test-run control. Test the saved Suite on an enrolled Android device or as a Web App. {% endhint %} ### Review the Suite before deployment Before deploying the Suite, confirm that: * Its name clearly identifies its purpose. * The correct Applets are included. * Every App Button opens the intended Applet. * Login requirements are appropriate. * Offline Support is enabled when required. * Auto Update is configured as intended. * The loading indicator is visible against the background. * The logo and fields fit the intended screen. * The latest changes have been saved. The Suite can continue to be refined after creation and before deployment. ### Next Continue to **Add and Organize Applets** to learn how to include additional Applets, configure App Buttons, and arrange the Suite launcher for its users. --- # 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/create-and-configure-a-suite.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.