Validate Prog
Validates a studio prog with xuda's own checker (structure, cross-references, workflow actions, expressions) PLUS a landmine scan for AI-typical mistakes (quotes inside xu-script/xu-style, unknown xu attributes, designer-state $-keys, malformed nodes). RUN THIS BEFORE EVERY save_prog and fix all errors; warnings are real problems too. Pass prog_json (candidate doc, pre-save) or prog_id (existing node).
Request
Response
Errors
An error keeps the envelope: a negative code and a message in data.
Related methods
create_proguserCreates a new studio node (program, table, component, folder...) using the same factory Studio itself uses. Returns the created doc.
delete_proguserSoft-deletes a studio node (Studio's stat 4 convention). The global node cannot be deleted.
get_proguserFetches one studio node (full JSON) by its id.
get_prog_examplesuserCurated, WORKING example progs from the xuda kitchen-sink project. Call without example_id to list (name, type, tags, one-liner); then fetch one by example_id and pattern your build on it. Examples are sanitized reference docs. Create your own progs with create_prog, never save an example verbatim.
save_proguserUpdates an existing studio node with a full doc (must include _id; _rev is checked for conflicts). Pass the doc as prog_json (a JSON-encoded string). Identity/audit fields (docType, created, createdByUid) are server-owned. Javascript progs are COMPILED on save (like Studio's own save): on success scriptData.dependencies is refreshed, on failure the doc is saved with a build_error and the response carries compile.error.
agent_firewall_closeuserClose inbound TCP port(s) on the current app's firewall. Acts only on the current app.
34 of 61 in Applications