Highlights
- Define schemas and fields, including configuration for general, security and table-view use.
- Browse, add and maintain records through dedicated data lists and forms.
- Compose ordered logic elements in the first Web IDE, then validate, save and debug the result.
- Inspect job details, logs and results in a browser operations workspace.
- Configure schedules and work with event and webhook operational views.
In detail
Model data before building behavior
Model data before building behavior
The new Resources area gives builders a browser home for data definitions. A schema can be managed separately from its fields, and field configuration is split into the concerns that matter while designing an application: the general definition, security-oriented settings and how a value should appear in a table. That separation makes the model easier to review before it is used by logic or exposed in an operational screen.Once a definition exists, the data workspace carries the flow into records. Teams can open a record list, add a new item and return to the detail flow to maintain it. This makes the release useful for both configuration and day-to-day application data, rather than treating schemas as an isolated administration feature.
Compose logic in the browser
Compose logic in the browser
0.0.2 introduces the first Web IDE workflow for logic. Builders work with an ordered list of elements, giving each item a key, type, timeout and visibility setting before saving the assembled definition. The editor validates the assembled logic before it is saved, helping teams catch structural problems while they are still in the authoring flow.The same workspace includes a debugger. A builder can provide inputs, run the current set of elements and inspect the returned debug output in the browser. This is especially important for an early low-code experience: it shortens the loop between changing a definition and seeing how that definition behaves. Logic history is available from the underlying product flow, establishing the basis for working with a definition over time; a dedicated side-by-side comparison experience arrives later.
Operate automation from the same application
Operate automation from the same application
The release also makes automation visible to operators. The Jobs area introduces lists and detail screens, with separate presentations for logs and results. Instead of asking an operator to infer a run from a single status, the workspace provides places to inspect the run, its execution information and its returned data.Schedules receive a list-and-detail configuration flow, including the controls needed to manage a schedule as a first-class definition. Event workspaces and webhook views sit alongside them, making it possible to navigate the different ways automation can be initiated and to review associated operational information in one product area.The result is a clearer hand-off between the people who define behavior and the people who monitor it. A builder can create the data and logic; an operator can follow the resulting jobs and scheduled work without reconstructing the context from separate tools.
Also in this release
- Shared navigation for Resources and Automation workspaces.
- Logic-element validation and debug feedback in the editor.
- Routed views for event and webhook operational information.