Skip to main content

Workbench

Workbench is GeniSpace's configuration-driven low-code application builder. It combines pages, navigation, responsive components, data bindings, actions, permissions, drafts, published versions, and an edit-mode Copilot.

Open Workbench​

Launch Workbench from the Platform Hub or open work.genispace.ai. The home page lists Workbenches available in the active space.

Create a Workbench​

Blank Workbench​

  1. Select Create Workbench.
  2. Enter a name and description.
  3. Create the first page.
  4. Add the page to navigation if users should open it directly.

Template or industry solution​

Use a Workbench template for a starting layout. Use an industry solution when you need a coordinated package of agents, datasets, tasks, workflows, and a Workbench.

Edit mode and run mode​

  • Edit mode displays component selection frames, resize handles, property panels, page controls, and Copilot.
  • Run mode displays the application as end users experience it.

An edit selection frame represents the component's configured layout area. Content inside a fixed-height component may scroll; content should not silently overflow beyond the selected frame.

Pages, navigation, and tabs​

In edit mode you can:

  • Create, rename, duplicate, reorder, and delete pages.
  • Add or remove navigation entries.
  • Configure page visibility and access.
  • Open application tabs without losing the current navigation context.

After creating a page through Copilot, the draft page is available immediately in the editor. Save the Workbench before expecting published or server-loaded page configuration to exist.

Add and arrange components​

Select Add Component, choose a component, and place it on the canvas. Components cover categories such as:

  • Metrics, cards, charts, tables, trees, timelines, and carousels
  • Forms, editable tables, filters, actions, and record details
  • Text, media, navigation, containers, and custom content
  • Workflow and task interaction
  • Agent and AI output

The catalog shown in your edition is authoritative; available components may expand without a documentation release.

Size and scrolling​

  • Drag the resize handle to change a component's configured width or height.
  • Table components allow a smaller minimum height suitable for approximately three visible data rows.
  • A fixed-height component with long content should expose an internal scroll area.
  • Workflow steps keep their controls reachable even when a proposal or parsed result is long.
  • Charts and forms use the configured Workbench height rather than replacing it with an unrelated renderer height.

If the selection frame and visible content do not align, first check component padding, the configured height, and whether content is intended to scroll.

Desktop and mobile layouts​

Use the viewport control to review desktop and mobile layouts. Mobile preview has its own scroll container and bottom navigation behavior. Test sticky filters, long tables, forms, and workflows in both orientations before publishing.

Sticky Filter Panels remain at the top of their scroll container. They should not animate between sticky and non-sticky positions while scrolling.

Configure a component​

Select a component to open its properties. Common settings include:

  • Title, description, fields, formatting, and empty state
  • Data source and query
  • Dataset and output fields
  • Filters and parameter mappings
  • Actions and user confirmation
  • Visibility rules
  • Height, spacing, and style

Use the preview after every material binding change.

Datasource and Dataset bindings​

Datasource​

Use a Datasource for relational business data and controlled read/write operations. A component can map form or row values to query parameters and actions.

Dataset​

Use a Dataset for managed records and structured, full-text, or semantic retrieval. Only select output fields declared by the Dataset schema.

The two data types have different query and update contracts. A Workbench configuration should state which source it uses instead of assuming they are interchangeable.

Record details and editing​

Data components can expose a View details action and, when update access is configured, an Edit action.

  • Scalar fields use suitable text, number, date, or select controls.
  • Arrays of objects use structured repeated sections instead of [object Object] or raw JSON.
  • Nested lists such as work experience, education, highlights, or line items can be added, edited, reordered, and removed.
  • Save writes through the configured Datasource or Dataset contract and refreshes the displayed record.

The field labels come from the Workbench or data schema. A Chinese industry template should define Chinese labels; an English template should define English labels.

Filters and component communication​

Filter Panels can publish committed values to connected components. URL parameters or event-bus values may take precedence over remembered local selections. Enable selection persistence only when users should return to their last committed filter.

Use component parameters and events to connect filters, charts, tables, details, and actions. Avoid circular event chains.

Workflows and long content​

Workflow components can guide a user through upload, proposal/review, and result steps. When a step contains a long parsed document or proposal:

  • Scroll inside the step content area.
  • Keep the step action buttons visible or reachable at the end of that internal scroll.
  • Do not depend on the outer Workbench page to reveal clipped content.

Workbench Copilot​

Copilot is available in edit mode and can use local tools to modify the current draft. Example requests include creating a page, adding it to navigation, inserting a component, or updating properties.

  1. Describe the desired change and target page.
  2. Review the execution event and the list of draft modifications.
  3. Inspect the canvas.
  4. Correct any unintended change manually or with a follow-up request.
  5. Select Save.
  6. Publish only after testing run mode.

Copilot completion means the in-browser draft changed. It does not mean the Workbench was saved or published.

Save, publish, and version history​

  • Save persists the current draft.
  • Publish makes a reviewed version available to users.
  • Version history lets you inspect and restore an earlier version.

Before restoring, save any work you still need. After restore, verify data bindings and run mode before publishing again.

Industry-solution upgrades create a new reviewable draft. The currently published Workbench remains available until the user confirms and publishes the upgraded draft.

Permissions​

Workbench access combines space permissions, application membership, application roles, and the permissions of bound resources. A user may be able to open a page but not edit a record if the underlying data update permission is absent.

Pre-publish checklist​

  1. Test every page and navigation entry.
  2. Test desktop and mobile scrolling.
  3. Verify empty, loading, error, and long-content states.
  4. Verify Datasource and Dataset read/write actions.
  5. Confirm destructive actions.
  6. Test with a non-administrator role.
  7. Save, review run mode, then publish.