Apps, Tables, labels and automations
Operations Studio maintains Apps, Tables, Labels, Automations and Document templates. Keep the site and environment consistent across connected assets. Input questions and their logic belong to ordinary App source and optional App settings; there is no separate Forms editor.
| Asset | Defines | Guide |
|---|---|---|
| App | The user interface, input controls and task logic | Building Apps |
| Table | Typed stored records shared by permitted Apps | Custom Tables |
| Automation | A separate reusable process, when needed | Automations |
| Label | Physical print layout and data bindings | Labels and printing |
| Document template | Reusable report layout and source bindings | Report templates |
Assemble data collection
Save or reuse the Table, connect it as a named App data source, and author the input screen in the App. Save directly through the connection. Evidence about an existing order or position can instead be linked to that object. Add an Automation only when separate processing is needed. See Collecting data with Apps.
Assemble a label workflow
Create a Label, bind its fields, verify preview and physical dimensions, and publish it. Connect a supported event or manual Automation with its printer target, copies and data. Publish and activate the workflow separately, then verify an authorized test and its print job. A queued job is not physical print confirmation.
Maintain dependencies
Inspect the Apps and Automations that reference a shared asset before changing it. Table schema changes protect existing record compatibility. An App publication does not activate an Automation or replace previously finalized report documents. Copied App source is independently editable, rather than a live link to its starter.
Use Publishing and governance to distinguish saved drafts, publication, activation and Test/Production release. Check the downstream result after changing a connection or shared asset.