Highlights
- Navigate Components by category, Component and element, with a separate list of changed work.
- See whether an element is new, modified or marked for removal before continuing work.
- Create and manage Component elements from the browser workspace.
- Give each new Endpoint a defined visibility, compatibility, library-loading and memory profile.
- Choose CSV delimiters, Boolean values, NULL representation and JSON encoding for Database downloads.
- Start event-driven work when a managed File is updated.
In detail
Define how an Endpoint should run
Define how an Endpoint should run
An Endpoint is now created with a full, predictable execution-options profile when one has not been supplied. Its request and response remain visible by default; legacy result mode and library skipping are disabled; and the default execution memory is 32 MB. These settings make the initial behavior of a newly defined Endpoint explicit rather than leaving it dependent on an incomplete options object.Endpoint metadata can also identify the particular Component schema element that it represents, alongside the schema identity and version. This is useful when an application exposes more than one callable element from the same Component definition: the Endpoint can retain the exact element-level connection needed by surrounding template and automation work.
Prepare a CSV for the destination system
Prepare a CSV for the destination system
CSV download was already part of the Database workflow; 0.6.0 adds choices for the exported representation. The export dialog lets an operator choose a delimiter and include hidden columns when needed. When the selected Database contains Boolean values, the download can express them as check and cross marks,
1 and 0, or true and false.The available controls follow the definition being exported. Nullable columns can use empty cells for NULL values, while Databases with JSON or JSONB columns can emit those values as Base64. A spreadsheet-friendly human review and a downstream import often need different representations; these choices let the same query result serve both without hand-editing every file after download.React when a managed File changes
React when a managed File changes
Managed-file updates can now publish a File Updated event. An automation can use that event as the start of a follow-on process: for example, validate a newly revised input file, refresh data derived from it or notify the people responsible for the next operational step. The event is raised for an update, so it represents the current managed-file record rather than a generic file-system signal.
Also in this release
- Dashboard routes open the selected dashboard canvas directly.
- The Web IDE keeps changed items visible separately from the full Component tree.