Source
project-default or a server-registered external-* profile; connection details never reach the browser.
SOLUTION STUDIO
YOUR WORK. YOUR DESIGN.
Design the solution for your project.
Prepare data fields, screens, analysis and automation drafts for one project in a shared definition; validate and preview them, then bind them to the project only through an approved step.
PROJECT BLUEPRINT
What is managed in this Studio?
Each project has one current workspace draft with up to 200 server revisions. Download a draft to duplicate an idea or open it in another authorized project. Real screens, schema and automation are applied only after validation and explicit approval.
Unbound draftDesign in the browser; download the JSON draft to keep it.
Loading design…
Analyse project data and follow up
Prepare your question here and select your data in your project’s analysis workspace. This transfers the analysis request, not screen designs or schema changes.
This list only prepares the starting request. The project workspace reads the connected source fields and the server capability catalog, then automatically shows analyses that can really run; a newly installed analysis engine appears through that catalog.
The question travels to the project workspace in the browser-only part of the link and is removed from the address when the workspace opens. Do not treat it as secret storage; do not include keys, passwords or private customer data. This does not send data to a model, database or external system.
Build an automation
Choose where data comes from, which fields are used and where the result goes. The system first prepares an immutable review summary; no record is written, API called or job queued until you explicitly approve it. You can also run a safe sample-data test.
Supported actions and limits
Steps / transform
At most 20 rows and 16 fields; V1 supports one-to-one field renames only. SQL, scripts and selectors are not accepted.
Target
Report performs no write. Database appends only through a readwrite profile. API runs only when an active project integration is also in the server allowlist.
These lists contain connections registered for this project and verified for your access. Add a new database or API connection in project settings.
Security boundary: Raw connection strings, URLs, headers, credentials, SQL, scripts, and DOM selectors cannot be entered. The source snapshot is read at execution time; approval binds the source/transform/target scope, not the future row values.
Immutable review summary
The API produced the source → transform → target summary and review hash. Changing any field invalidates this review.
Review hash:
Run and audit records
Queued does not mean completed. Follow the status and error code here.
| Request | Status | Attempt | Error | Created | Completed |
|---|---|---|---|---|---|
| Records load only after project authority is verified. | |||||
Resolve an uncertain result with evidence
If a definite failure occurs before submission, the worker can make at most three controlled attempts. An uncertain post-submit result is never retried automatically; independent evidence is required to avoid duplicate action.
Connect a project · inspect schema differences
Save the design and table/field mappings to your private project draft. This does not change code or a customer database. Raw schema files and sample records are not saved.
For a new workspace, first save your design to your project. The package contains code and setup files for SQL Server, PostgreSQL and MySQL, with your fields and screen bindings. Downloading does not change a database; migration of a running project requires separate review.
Choose an authorized project using “Design in Studio” in project settings. File comparison below is local; ownership and freshness of the schema file are not verified.
Requires an authorized project and a previously registered isolated workspace source. Reads table/column structure only, not records, connection secrets or commands. Opening a file does not establish this binding.
Open a generator TXT definition or a SQL Server/PostgreSQL/MySQL catalog copy in ogan.database.catalog v1 format. The catalog covers selected tables only; its date or filename is not proof of project ownership or freshness.
The file stays in your browser. Passwords, roles, defaults and records are excluded. Only mappings and a structural fingerprint can be saved with a project draft; this does not prove schema freshness. Standard draft downloads contain only the design.
INSTANT VIEW
Form, table and summary share one data definition. Trial records are not saved to a file or server.
Validation and application requirements
Not checked yet. Edit the draft, then choose Check definition.