Data and action components

These components handle data display, search results, object creation, saving, and script execution in Caseflow templates.

ObjectSearch

Query and render objects in table, cards, or list format with row actions, editing, and create support.

Key capabilities

Declarative query config with class, display columns, constraints, and sorting
Row context menu — edit, delete, documents, history
Editable mode with modal editing
Inline cell editing on the result table — see Inline cell editing
Create mode with defaults
Optional per-row document lookup via documentSearchConfig
“Open related” navigation that resolves a dotted attribute path to a related object — configured per saved search in the Search configurator
queryKey for targeted refresh
itemTemplateName for card/list rendering

Props

Prop	Type	Required	Default	Notes
`config`	`ObjectSearchConfig` or JSON string	Yes	—	Must include class and display columns.
`display`	`table` \| `cards` \| `list`	No	`table`	`cards`/`list` can use `itemTemplateName`.
`itemTemplateName`	`string`	No	—	Per-row template for cards/list rendering. It gets the row’s display column values as `{{columns.<label>}}` — see Item templates.
`editable`	`boolean`	No	`false`	Enables edit action and edit modal flow.
`editTemplateName`	`string`	No	class default Update template	Edit modal template override.
`allowCreate`	`boolean`	No	`false`	Enables add/create action.
`createTemplateName`	`string`	No	class default Create template	Create modal template override.
`createDefaults`	`Record<string,string>` or JSON string	No	—	Applied to new object before first render.
`allowDelete`	`boolean`	No	`false`	Enables delete action with privilege checks.
`documentSearchConfig`	`DocumentSearchDto` or JSON string	No	—	Enables per-row documents modal action.
`queryKey`	`string`	No	`object-search-<className>`	Stable key for targeted refresh actions.
`openCreatedObject`	`string` \| `boolean`	No	`false`	Open newly created object in new tab.
`selectInto`	`string`	No	—	Click to select into a transient field of the view, for example `_SelectedObjectId`. See Click to select.
`onSelect`	`string`	No	—	Action chain after a `selectInto` selection, run on the view’s object, with `${row.*}` variables.

ObjectSearchConfig shape

{
  "className": "Task",
  "displayColumns": [
    { "dottedName": "Name" },
    { "dottedName": "Status", "label": "Current status" }
  ],
  "constraints": [
    { "dottedName": "CaseRelation", "operator": "=", "value": "{{stock.objectid}}" }
  ],
  "sorting": [
    { "dottedName": "Name", "direction": "asc" }
  ]
}

Examples

Editable list with create and targeted refresh:

<ObjectSearch
  queryKey="case-tasks"
  config='{
    "className":"Task",
    "displayColumns":[{"dottedName":"Name"},{"dottedName":"Status"}],
    "constraints":[{"dottedName":"CaseRelation","operator":"=","value":"{{stock.objectid}}"}]
  }'
  editable="true"
  allowCreate="true"
  allowDelete="true"
  createDefaults='{"CaseRelation":"{{stock.objectid}}"}'
/>

Row-specific document lookup using ${row.*} variables:

<ObjectSearch
  queryKey="objects-with-docs"
  config='{
    "className":"Task",
    "displayColumns":[{"dottedName":"Name"}]
  }'
  documentSearchConfig='{
    "documentTypeIds":[116],
    "filters":[
      {"keywordTypeId":115,"operator":"Equal","value":"${row.stock.objectid}"}
    ],
    "maxResults":50
  }'
/>

Item templates

An item template renders one search row. Its scope is the row’s own object, so {{Name}} is that object’s own Name attribute. The configured display column values are available under columns, keyed by the column’s label, or by its dottedName when it has no label. That is how a card shows values from a related object:

<ObjectSearch
  config='{
    "className":"Offer",
    "displayColumns":[
      {"dottedName":"OfferId","label":"Offer ID"},
      {"dottedName":"VehicleRelation.Make","label":"Make"},
      {"dottedName":"VehicleRelation.Model","label":"Model"},
      {"dottedName":"PresentedAt","label":"Presented"}
    ],
    "constraints":[{"dottedName":"LeadRelation","operator":"=","value":"{{stock.objectid}}"}]
  }'
  display="list"
  itemTemplateName="OfferCard"
/>

The OfferCard template:

<div class="p-4">
  <p class="font-semibold">{{columns.Make}} {{columns.Model}}</p>
  <p class="text-sm text-muted-foreground">{{columns.Offer ID}}</p>
  <p class="text-sm">Presented <DateDisplay value="{{columns.Presented}}" /></p>
</div>

Keys are used exactly as written. {{columns.Offer ID}} and, for an unlabelled column, {{columns.VehicleRelation.Model}} both work in text and in props.
In a condition ({{#if …}}), give the column a label made of letters, digits and dots only: no spaces, parentheses, quotes or operator characters such as !, =, <, >, & or |. For example {{#if columns.Make}} works, but a column labelled Offer ID or Amount (DKK) can’t be tested in a condition.
Values are the search result as text: dates arrive as ISO text (for example 2026-10-01T00:00:00) and numbers are not localized, so wrap a date in <DateDisplay value="{{columns.Presented}}" /> as above.
Values are those from when the search ran. After an edit inside the card, {{columns.X}} keeps the old value until the search refreshes, so use {{AttributeName}} for the row’s own attributes that the card edits.
A null value is empty in columns. The table, cards and list displays show it as —.
Templates that don’t use columns render exactly as before.
If the search doesn’t return a configured column, ObjectSearch shows a warning naming it (for example “Column ‘Make’ (VehicleRelation.Make) was not returned by the search”) instead of leaving it silently empty.

Click to select

Use selectInto for master/detail views: one click selects a row or card, a double click opens it. Without selectInto, the existing click behavior is unchanged.

Interaction	With `selectInto="_X"`
Click, Enter, or Space	Writes the object id to the transient field `_X` of the view and highlights the item. Nothing opens.
Double click, Ctrl/Cmd+Enter, or the item’s open button	Opens the object in one new tab.
Click or double click on a card nested in another card	Handled by the clicked card only; the cards around it neither select nor open.
Click on a button, link, or field inside an item	Left to that control.

An ObjectSearch inside an item template with the same selectInto hands its selection to the outermost ObjectSearch that declares the field, so a click on a card at any depth of a recursive tree selects into the view. The item template can read {{selection.isSelected}} ("true" or empty) to style the selected card. Fields that start with _ are transient: selecting never marks the object as changed and never touches unsaved edits. onSelect runs after a selection in the view’s context, so setValue writes to the view. A newer selection cancels the actions of an older one that has not run yet. Pair it with a reactive DocumentSearch to show the selected object’s documents:

<ObjectSearch
  config='{"className":"Part","displayColumns":[{"dottedName":"Name"},{"dottedName":"Code"}]}'
  display="table"
  selectInto="_SelectedObjectId"
  onSelect='setValue:{"attributeName":"_SelectedObjectName","value":"${row.Name}"}'
/>
{{#if _SelectedObjectId}}
  <DocumentSearch
    reactive="true"
    config='{"documentTypeIds":[116],"filters":[{"keywordTypeId":115,"operator":"Equal","value":"${_SelectedObjectId}"}]}'
  />
{{else}}
  <p>Select an object to see its documents.</p>
{{/if}}

DocumentSearch

Query and render documents from a document search configuration with optional upload support.

Props

Prop	Type	Required	Default	Notes
`config`	`DocumentSearchDto` or JSON string	Yes	—	Main query contract for documents.
`display`	`table` \| `cards` \| `list`	No	`table`	Rendering style.
`viewable`	`boolean`	No	`true`	Enables open/view behavior.
`queryKey`	`string`	No	auto-generated	Use stable key for `refreshDocuments:<key>`.
`showHeader`	`boolean`	No	`true`	Result count and refresh controls.
`title`	`string`	No	component default	Header title.
`allowUpload`	`boolean`	No	`false`	Enables upload entry point.
`createDefaults`	`DocumentUploadDefaults` or JSON string	No	—	Prefills upload type and keywords.
`className`	`string`	No	—	Styling hook.
`reactive`	`boolean`	No	`false`	Re-run whenever a `${...}` filter value changes, without `refreshDocuments`. Results found for an earlier value are never shown for a new one: the search shows its loading or error state instead.
`preview`	`none` \| `modal`	No	`none`	`modal` puts an eye button on every result. It opens the document in a pop-up over the view, the same pop-up as RelatedDocument’s `preview="modal"`. See Preview a document without leaving the view.
`previewWithKeywords`	`boolean`	No	`false`	With `preview="modal"`: the document’s keyword panel beside it in the pop-up.

Filter values can read the object store with ${...}; the search does not run while a referenced value is empty. Without reactive, such a search runs again only on refreshDocuments:<queryKey> and keeps showing its previous results while it reloads.

Preview a document without leaving the view

With preview="modal", every result gets an eye button. It opens the document in a pop-up over the view, where you can page through it. The pop-up closes with its close button, Escape, or a click outside it, and leaves the view as it was: the same scroll position and selection, and any unsaved edits untouched. Previewing never changes the record. The eye button is its own click target: it does not open the document in a new tab or select the row. Add previewWithKeywords="true" to show the document’s keyword panel beside it, in a split you can resize and collapse. Keyword edits there are saved to the document with the user’s own rights; they never change the Caseflow record. On screens narrower than 1024 px the pop-up fills the screen. preview takes only none and modal here. An inline preview exists only on RelatedDocument. The template editor warns about preview="inline", about preview="true", and about previewWithKeywords without preview="modal"; those settings have no effect.

<DocumentSearch
  config='{"documentTypeIds":[127],"filters":[{"keywordTypeId":235,"value":"${_SelectedObjectId}","operator":"Equal"}]}'
  reactive="true"
  preview="modal"
  previewWithKeywords="true" />

Common enum values for configs

Enum	Values
`FilterOperator`	`Equal`, `NotEqual`, `LessThan`, `LessThanEqual`, `GreaterThan`, `GreaterThanEqual`, `Contains`, `StartsWith`, `EndsWith`, `IsNull`, `IsNotNull`
`SortDirection`	`Ascending`, `Descending`
`StandardColumn`	`DocumentId`, `DocumentName`, `DocumentTypeId`, `DocumentTypeName`, `DocumentTypeGroupId`, `DocumentTypeGroupName`, `DocumentDate`, `StoredDate`, `CreatedByUserId`, `CreatedByUsername`, `FileExtension`, `FileTypeName`, `MimeType`, `CurrentRevisionNumber`
`DateFilterPreset`	`Today`, `Yesterday`, `ThisWeek`, `LastWeek`, `CurrentMonth`, `LastMonth`, `ThisYear`, `LastYear`

Examples

Baseline document search:

<DocumentSearch
  queryKey="case-documents"
  config='{
    "documentTypeIds":[116],
    "filters":[
      {"keywordTypeId":115,"operator":"Equal","value":"{{stock.objectid}}"}
    ],
    "maxResults":50
  }'
/>

Upload flow with defaults:

<DocumentSearch
  queryKey="case-documents"
  config='{
    "documentTypeIds":[116],
    "filters":[
      {"keywordTypeId":115,"operator":"Equal","value":"{{stock.objectid}}"}
    ]
  }'
  allowUpload="true"
  createDefaults='{
    "documentTypeId":"116",
    "keywords":[
      {"keywordTypeId":"115","value":"{{stock.objectid}}"},
      {"keywordTypeId":"320","value":"{{CaseNumber}}"}
    ]
  }'
/>

DocumentChat

An AI question-and-answer chat over the documents a DocumentSearch config matches, inside the object’s view. Answers carry document and page references; a click opens the cited page in Caseflow’s preview pop-up (the same as preview="modal") without leaving the view. Where an answer refers to a Caseflow object, a click opens the object in a new tab. The user can ask follow-up questions in the same conversation, end an answer while it is being written with Stop, and start over with New conversation.

Prerequisites

AI chat is available to the user. It is off unless it is switched on for your environment, and where features are controlled per user group, one of the user’s groups needs AI document search chat under Admin settings → Access → User Group Access. The panel checks this first and otherwise shows AI chat is not available to you here.
An AI search agent under Admin settings → AI Assistant → Agents with keyword types (its keyword boundary), offered to the user groups that use the view, and with Caseflow templates ticked under Offered in. Untick AI chat there if the agent should only be used from templates. See AI agents and shared settings.
The documents are indexed for AI search.

Props

Prop	Type	Required	Default	Notes
`config`	`DocumentSearchDto` or JSON string	Yes	—	The documents to ask about, in the DocumentSearch config format. It must pin the agent’s boundary keyword with an `Equal` filter. A new `${...}` value starts a new conversation.
`agent`	`string`	Yes	—	The search agent’s name, as shown under AI Assistant → Agents. See Agent by name.
`title`	`string`	No	`Ask AI about the documents`	Panel heading.
`scopeLabel`	`string`	No	—	Name of the scope in the scope line, for example `{{_SelectedObjectName}}`.
`placeholder`	`string`	No	—	Placeholder of the question field.
`height`	`string`	No	`420px`	Height of the conversation area.
`previewWithKeywords`	`boolean`	No	`false`	The cited page opens with the document’s keyword panel beside it. The panel is the same editable panel as on DocumentSearch: keyword edits there are saved to the document with the user’s own rights.
`className`	`string`	No	—	Styling hook.

Agent by name

Like classes and attributes in a template, the agent is referred to by its name, never by its id. Ids differ between environments; the name is what the template keeps when it is promoted.

The name is matched against the search agents the user may use that are offered in Caseflow templates. Matching is exact, ignores case, and ignores leading and trailing spaces.
The chat never falls back to another agent.

Renaming an agent means updating the templates that name it, just as renaming a class does. Until then, those chats show that no agent with the name is available. Agent names are not required to be unique. If two agents the user may use have the same name, the chat refuses to start until an administrator renames one of them.

States

Instead of the question field, the panel shows a state when the chat cannot start:

State	When
No AI agent named ”…” is available to you. It may not be offered in Caseflow templates.	No search agent with that name exists (for example, after a rename), the agent is not offered in Caseflow templates, or the user’s groups may not use it.
More than one AI agent is named ”…”	Two or more agents the user may use share the name.
Could not load the AI agents	The agent list failed to load. Retry loads it again.
No AI agent is set for this chat	`agent` is empty.
AI chat is not available to you here	AI chat is not available to the user: it is switched off for your environment, or features are controlled per user group and none of the user’s groups has AI document search chat. Also shown when no agent applies to the user at all.
Select an object to ask about its documents	A `${...}` value in the config is empty.
Could not check the documents	The scope check failed. Retry runs it again.
These documents cannot be used for AI chat	The config does not pin the agent’s boundary keyword.
This agent’s document scope matches no document types…	The agent’s document-type restriction resolves to no document types, for example a restriction to document type groups that are empty. An administrator needs to fix the agent.
This chat would not be limited to these documents, so it cannot start.	The conversation would not be limited to the documents the config matches. This is the case for an agent without keyword types, even one that restricts document types: it would answer from every document of those types that the user may read.
There are no documents to ask about here	The config matches no documents.
Too many documents to ask about	The config matches more documents than the conversation limit.
None of the documents are indexed for AI yet	None of the matching documents are indexed.

When some, but not all, documents are indexed, the scope line says how many the AI cannot read.

What the server enforces

The conversation uses exactly the agent the template names. The server checks the config against that agent alone and refuses it when the config does not satisfy the agent’s boundary.
The agent must be offered to one of the user’s groups.
When the conversation is created, the server fixes its scope to the documents the config matches. Every answer, including follow-ups, is retrieved from that set only; a question cannot widen it. To ask about another object, the panel starts a new conversation.
The user’s own document rights still apply.
An agent offered in Caseflow templates cannot be saved without keyword types.

Before it creates a conversation, the component also refuses a scope that would not be limited to the config’s documents; see This chat would not be limited to these documents, so it cannot start. under States. The chat itself never writes. It does not change documents, keywords, or the object, and it does not mark the object as changed. The citation pop-up’s keyword panel (previewWithKeywords) saves keyword edits with the user’s own rights, as on DocumentSearch. Conversations appear in the user’s AI chat history. The panel shows no approval cards for keyword changes the agent proposes. For an agent offered in Caseflow templates, set propose_keyword_updates to Off under the agent’s Tool overrides. In the template editor’s preview nothing is saved: asking a question starts no conversation and shows Not available in preview, the question stays in the field, and the citation pop-up’s keyword panel is read-only.

Example

The documents of the object selected in an ObjectSearch with selectInto="_SelectedObjectId":

{{#if _SelectedObjectId}}
  <DocumentChat
    agent="Case documents"
    title="Ask about the documents"
    scopeLabel="{{_SelectedObjectName}}"
    config='{"documentTypeIds":[116],"filters":[{"keywordTypeId":115,"operator":"Equal","value":"${_SelectedObjectId}"}]}'
  />
{{/if}}

Here the search agent Case documents has keyword type 115 as its boundary.

CreateObjectButton

Open a create modal for a class and optionally run post-create actions.

Props

Prop	Type	Required	Default	Notes
`className`	`string`	Yes	—	Class to create.
`templateName`	`string`	No	class default Create template	Create template override.
`defaults`	`Record<string,string>` or JSON string	No	—	Initial create values.
`label`	`string`	No	component default	Button text.
`variant`	`primary` \| `secondary` \| `outline` \| `ghost`	No	`primary`	Button styling.
`onCreated`	`string`	No	—	Action chain after successful create.
`openCreatedObject`	`string` \| `boolean`	No	`false`	Open created object in new tab.
`buttonClassName`	`string`	No	—	Styling hook.

Example

Create with refresh and local update:

<CreateObjectButton
  className="Task"
  defaults='{"CaseRelation":"{{stock.objectid}}","Status":"Open"}'
  onCreated='refresh:case-tasks | setValue:{"attributeName":"HasTasks","value":"true"}'
  label="Add task"
/>

SaveButton

Save dirty objects within a controlled scope with before/after hooks for validation and automation.

Props

Prop	Type	Required	Default	Notes
`scope`	`primary` \| `all`	No	`primary`	Save scope when `objectKey` is not supplied.
`objectKey`	`string`	No	—	Target a specific object in store.
`label`	`string`	No	component default	Button text.
`variant`	`primary` \| `secondary` \| `outline` \| `ghost`	No	`primary`	Button styling.
`requireDirty`	`boolean`	No	`true`	Set `false` to allow hook-only save triggers.
`onBeforeSave`	`string`	No	—	Executes before save API call.
`onAfterSave`	`string`	No	—	Executes after successful save API call.
`className`	`string`	No	—	Styling hook.

Save hook runtime variables

${changedFields} — array with utilities like .includes("Field"), .length, .join(", ")
${oldValues.AttributeName}
${newValues.AttributeName}

Examples

Save-time validation gate:

<SaveButton
  scope="primary"
  onBeforeSave='throwError:{"message":"Notes are required when closing"} when ${newValues.Status} == "Closed" and ${newValues.Notes} == ""'
/>

Normalize values before save and refresh after save:

<SaveButton
  scope="primary"
  onBeforeSave='setValue:{"attributeName":"SubmittedBy","value":"{{user.username}}"}'
  onAfterSave='refresh:case-tasks | refreshDocuments:case-documents'
  label="Save changes"
/>

ScriptButton

Run a script directly from the UI with input mapping and result-driven follow-up actions.

Props

Prop	Type	Required	Default	Notes
`script`	`string`	Yes	—	Script slug.
`inputs`	`object` or JSON string	No	`{}`	Supports `{{...}}` and `${...}` variable forms.
`label`	`string`	No	component default	Button text.
`variant`	`primary` \| `secondary` \| `outline` \| `ghost`	No	`primary`	Button styling.
`onSuccess`	`string`	No	—	Action chain with `${scriptResult...}` support.
`onError`	`string`	No	—	Action chain with `${scriptError}` support.
`disabled`	`boolean`	No	`false`	Disable button execution.
`className`	`string`	No	—	Styling hook.

Example

Script output projected to field:

<ScriptButton
  script="generate-document"
  inputs='{"object_id":"{{stock.objectid}}","template":"${_TemplateName}"}'
  onSuccess='setValue:{"attributeName":"GeneratedDocumentId","value":"${scriptResult.data.document_id}"} | refreshDocuments:case-documents'
  onError='throwError:{"message":"Document generation failed"}'
  label="Generate document"
/>

WorkflowTasks

List the workflow tasks offered on the current object, so people can complete them without leaving the case. Inside a RelatedObject, it lists the related object’s tasks. A task is listed only when the workflow author switched on Also show on the document or object for it; every other task stays on the Tasks page only. Tasks are grouped by workflow, with the step each one is on. Who sees a task, and the inputs it asks for, are the same as on the Tasks page; see tasks on the document or Caseflow object. After a task completes, the object’s values are reloaded. Unsaved changes are kept, and the person is asked to save and reload. The element shows nothing while the object is being created, while its tasks load, or when they cannot be loaded. With no tasks, the button is hidden, while the inline list says No tasks right now., so a tab that holds only the list is never blank.

Props

Prop	Type	Required	Default	Notes
`display`	`button` \| `inline`	No	`button`	`button` shows an icon with the task count that opens a side panel; `inline` shows the grouped list in place.
`label`	`string`	No	`Tasks`	Caption of the button and the panel, or the list’s heading.
`className`	`string`	No	—	Styling hook.

Examples

In a header:

<div class="flex items-center justify-between">
  <h2 class="text-lg font-semibold">{{Name}}</h2>
  <WorkflowTasks />
</div>

On a tab of its own:

<Tabs defaultValue="details">
  <Tab value="details" label="Details">
    <EditableField attributeName="Title" />
  </Tab>
  <Tab value="actions" label="Actions">
    <WorkflowTasks display="inline" label="Actions" />
  </Tab>
</Tabs>

Internal support components

These components are used internally by the Caseflow runtime. They are not available as template tags but are important for understanding the system.

ObjectModal

Modal shell for template-driven create/edit operations. Used by ObjectSearch and CreateObjectButton.

Create mode initializes a new in-memory object state and can apply defaults
Edit mode binds to an existing object key
Resolves and renders the chosen template (Create or Update)
Handles save mutation and callback orchestration (onCreated, onSaved)
Can open created object in a new tab
Invalidates related query keys after save so dependent UI refreshes
If closed before first save, unsaved temporary state is cleaned up
If no template exists, a clear fallback message is shown

DocumentsModal

Modal wrapper around DocumentSearch with resolved config. Used by ObjectSearch row actions for “view related documents”.

Receives already-resolved configuration from parent (including row-variable substitutions)
Shows loading state while configuration is being prepared
Renders DocumentSearch in table mode with header enabled

DocumentPreview

File preview renderer with revision/rendition selection and live refresh. Used by RelatedDocument preview modes.

Fetches revisions and renditions for a document
Picks latest revision and default rendition for preview
Subscribes to document revision events and refreshes automatically
Returns structured loading, empty, and error states

ItemTemplateRenderer

Renders one search result item using a named Caseflow template for cards/list displays. Used by ObjectSearch when display="cards" or display="list".

Creates an isolated object provider per item (no row-to-row state bleed)
Fetches the named template for the row’s class in update context
Builds item scope with regular attributes, stock attributes, user context, and alias scopes
Adds the row’s display column values as columns.* — see Item templates

ObjectHistoryDialog

Shows object audit details in a dialog with two data views. Used by ObjectSearch row action “View history”.

Attribute Changes tab — flattened transaction/attribute change rows
Event Log tab — event timeline with translated event types
Loads history only when dialog is open
Formats UTC timestamps for readable presentation

Complete component inventory

Component	Template tag	Primary purpose
`EditableField`	Yes	Edit one attribute with type-aware editor
`RelatedObject`	Yes	Resolve and render a related object
`RelatedDocument`	Yes	Render document attribute with preview
`RelationPicker`	Yes	Select or create relation targets
`ObjectSearch`	Yes	Execute object searches with row actions
`DocumentSearch`	Yes	Execute document searches with optional upload
`DocumentChat`	Yes	Ask AI about the documents a document search matches
`CreateObjectButton`	Yes	Launch create-object modal
`SaveButton`	Yes	Save current or all objects
`ScriptButton`	Yes	Run a script on-demand
`WorkflowTasks`	Yes	List the workflow tasks offered on the object
`ObjectModal`	No	Modal shell for create/edit operations
`DocumentsModal`	No	Modal wrapper for document search
`DocumentPreview`	No	File preview with revision support
`ItemTemplateRenderer`	No	Render one search result via template
`ObjectHistoryDialog`	No	Object audit and history dialog

Where to read next

Lists, saved searches, and search operators

Configure Caseflow saved searches and folders, result tables, typed column filters, bulk actions, inline editing, and search operators.

​ObjectSearch

​Key capabilities

​Props

​ObjectSearchConfig shape

​Examples

​Item templates

​Click to select

​DocumentSearch

​Props

​Preview a document without leaving the view

​Common enum values for configs

​Examples

​DocumentChat

​Prerequisites

​Props

​Agent by name

​States

​What the server enforces

​Example

​CreateObjectButton

​Props

​Example

​SaveButton

​Props

​Save hook runtime variables

​Examples

​ScriptButton

​Props

​Example

​WorkflowTasks

​Props

​Examples

​Internal support components

​Complete component inventory

​Where to read next

Lists, saved searches, and search operators

ObjectSearch

Key capabilities

Props

ObjectSearchConfig shape

Examples

Item templates

Click to select

DocumentSearch

Props

Preview a document without leaving the view

Common enum values for configs

Examples

DocumentChat

Prerequisites

Props

Agent by name

States

What the server enforces

Example

CreateObjectButton

Props

Example

SaveButton

Props

Save hook runtime variables

Examples

ScriptButton

Props

Example

WorkflowTasks

Props

Examples

Internal support components

Complete component inventory

Where to read next