usertasks
All documentationStart free beta
Documentation hub

Feature guide

Objects and data

Model reusable business entities over custom tables and external reference operations.

On this page

Complete feature description

Understanding objects and data in UserTasks

Objects provide a business-oriented data contract over UserTasks custom tables and external Integration References. Instead of making every form, page, or workflow understand a vendor-specific API, an object defines stable fields and maps common operations—list, get, insert, update, and delete—to one or more sources.

Custom tables are tenant-scoped operational stores with typed columns, imports, APIs, realtime updates, and workflow events. External object sources can call references so records remain in the system of record while UserTasks presents a consistent model to designers.

Because objects are reusable, the same customer, vendor, case, or asset definition can drive page tables, form lookups, workflow actions, reports, and composite application experiences.

When to use this feature

  • Multiple product areas need the same business entity.
  • External data should be presented without copying it into UserTasks.
  • You need CRUD-style behavior over custom operational data.
  • A source-specific API should be hidden behind stable business field names.

What you can build

  • Vendor and customer registries
  • Case and request records
  • Reference-data catalogs
  • External CRM or ERP views
  • Composite objects spanning internal and external sources
  • Event-driven operational datasets

Production design notes

  • Keep object keys stable after consumers bind to them.
  • Make source mappings explicit and test list/get and mutation operations independently.
  • Use data-change workflows carefully to avoid update loops.
  • Apply object and source permissions according to the most sensitive underlying field.

Core concepts

Custom tables

Tenant-scoped typed data stores support UI editing, imports, APIs, workflows, and realtime events.

Object definitions

Name business fields and map list, get, insert, update, and delete operations to data sources.

Object sources

A source may be a custom table or integration reference with field and parameter mappings.

Reusable access

Objects can drive forms, pages, workflows, reports, APIs, and composite application experiences.

Actions and capabilities

What designers and operators can do in this product area.

Objects and data actions

The main operations available in Objects and data.

Objects and data actions

Create table

Define columns and types, then manage rows from the data workspace.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “Create table”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Objects and data actions

List and retrieve

Query collections or individual records through object-backed references.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “List and retrieve”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Objects and data actions

Insert, update, and delete

Map object operations to custom-table mutations or external integration references.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “Insert, update, and delete”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Objects and data actions

Trigger on data change

Start workflows when rows are created, updated, or deleted and filter on changed fields.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “Trigger on data change”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Objects and data actions

Expose through OData

Use the tenant OData endpoint to query eligible operational data with standard options.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “Expose through OData”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Objects and data actions

Import and report

Load CSV/Excel data and use tables or object fields as report sources.

Example: Model a Vendor object once, then reuse it in an intake form and approval page.
Configuration inputs
  • Permission to view and edit the relevant objects and data assets.
  • The target table or object definition and its typed fields, source, and operation mappings.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Data from the main navigation.
  2. 2.Create or open the relevant asset and choose “Import and report”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The reusable business entity is available to forms, pages, workflows, reports, and APIs.
  • Failures remain visible with enough context to correct configuration or retry safely.

Potential use cases

Patterns you can adapt to your own operating model.

Vendor registry

Maintain vendor records and drive approvals when risk information changes.

Custom table
Object definition
Page editor
Data change workflow
Approval task

Virtual customer object

Present an external CRM record as a reusable object without copying all data.

REST integration
List/get references
Object field mappings
Page binding
Workflow update action