Skip to content

Help sobject_editor

Alex Miarsky edited this page Nov 10, 2026 · 2 revisions

Creating and editing sObjects

The object editor uses the active TACTIC EditWdg definition.

On a configured page, Edit record opens the selected object's native form. The page displays stored record values; its layout controls their presentation. If a displayed value is missing from the form, add its actual column to that Search Type's edit definition. Use TextAreaWdg for long or Markdown text. Edit the source text, choose Save changes, then refresh the selected details to see its rendered content. Closing without saving leaves the record unchanged.

Keywords use the same tag editor as the results table. Click the field to add or remove individual tags. Save applies the tags to the form draft; submit the object form to write them to TACTIC. Cancel leaves the field unchanged.

Main controls

Each field keeps the server title, order, column, required and read-only state, option labels and stored values. Text, multiline, boolean, select, user, project, process, pipeline, status, date, password, parent, preview, and thumbnail widgets share one responsive Material form.

Status and process colors and task assignees follow the selected object's workflow configuration.

Usage notes

  • Opening a newly created object keeps the current dock arrangement; its Search tab retains its own layout afterward.
  • Fields stack in one ordered column in a narrow window.
  • Widening either the Create or Edit window flows the existing field cards into two or three columns instead of stretching every control across the window.
  • Each card still aligns its label beside the control when its own width allows it.
  • The form and multiline fields show theme-aware scrollbars whenever their content exceeds the available height.
  • Select lists hide unnamed blank entries; a named empty or default option remains available.
  • Password editing never reveals the current value; leave it empty to keep the existing password.
  • Unsupported custom server widgets remain visible and read-only instead of writing an incorrect fallback value.

Shared object form example

Open Create for Assets, enter a name and description, and save. Multiple keeps an individual preview for each object; Robot {n:03} generates Robot 001, Robot 002, etc. Review every preview before Create. Handler keeps its configured batch adapters. Browser Multiple currently supports ordinary database fields; custom actions, uploads and instance creation explain why individual forms are required. Cancel does not write. A failed response keeps the draft; an unknown write result blocks resubmission until you close, refresh and check the records.

Presentation examples

Examples use test data and show the panel content. The surrounding window or dock keeps its normal behavior.

Batch creation panel

Clone this wiki locally