Studio, fields and logic units FAQ
Answers about Xuda Studio itself, component fields, and the Alert, Batch, Folder and Workflow building blocks.
Questions people ask about building the logic and data behind a screen: the editor itself, a component's fields, and the four reusable program types every app draws on.
Studio
What is Xuda Studio?
Studio is the project editor: a workspace split into five areas (a top bar, a left tree of Globals, Database, Programs, Routes and AI Agents, a center canvas, a right-hand inspector plus AI chat, and a bottom console for live preview). See Studio overview.
What is in the left tree?
Globals (one shared program every other program can read from), Database (your tables), Programs (components and the Get Data, Set Data, Batch, API, JavaScript and Alert programs that support them), Routes (the page paths that make a component openable), and AI Agents. See Studio overview.
Can I undo a mistake in Studio?
Every save is a revision, so you can roll back to an earlier version, and a restore is itself reversible. See Studio overview for the editor and its build flow.
The right panel is a split pane: an inspector on top for whatever is selected, and the AI chat underneath, both visible at once, not two tabs you flip between. See Studio overview.
Component fields
What is a field?
A named piece of information a component can use: something a user enters, something read from a table or the component's own datasource, or something calculated from other fields. See Component fields.
What is a computed field?
Turn on Computed when a field should be calculated instead of entered directly, for example a display name or a formatted total. See Component fields.
Can a field run its own logic?
Yes. Initiated Actions attaches a workflow to a field, the same Add Action catalog a component event builds from, so a field can validate, save, alert or refresh on its own. See Component fields.
Alert
What is an Alert?
A reusable notification: a title, a body, a severity (info, success, warning or error) and a
display surface, defined once and raised from any component, workflow or JavaScript program with
call_alert. See Alert.
What can an Alert display as?
A toast, a modal dialog, a native browser pop-up, or a quiet console message for developers. See Alert.
Can an Alert log an event when it fires?
Yes, an alert step can write a log entry alongside the message it shows, useful for auditing or debugging. See Alert.
Batch
What is a Batch?
A reusable program that orchestrates several steps as one callable operation, for a multi-step
save, a loop over records, or a sequence of API calls, called with the batch action the same way
you would call a Get Data or Set Data program. See Batch.
Does a Batch need a data source?
No. A Batch can process a list of records, but it can just as easily coordinate a sequence of steps that have nothing to do with a list. See Batch.
Can a Batch run on the server?
Yes, setting a Batch's runAt to server keeps privileged data access or an expensive loop off the
client. See Batch.
Folder
What does a Folder do?
It groups other units under one parent in the Studio tree so a project with many components, tables and programs stays navigable. A folder runs no logic of its own. See Folder.
Where can a Folder sit?
Directly under Programs or under Database, or nested inside another folder. Routes has no folder support, every route sits directly under its own root. See Folder.
Workflow
What is a workflow?
The step language embedded in every program and every element: an ordered array of actions, each
one naming what to do. The same shape appears on a program's on_load, a field's change handler,
and a button's xu-on:click. See Workflow.
What triggers a workflow?
Lifecycle events (load, exit, before and after save), custom events you raise yourself, scheduled jobs and timers, and direct user actions like a button click. See Workflow.
Can a step run without waiting for it to finish?
Yes, a step can carry props.async: true to fire without the workflow waiting on it, which is the
right call for background work, and the wrong one when a later step needs that result. See
Workflow.