Objects are the records a solution keeps — tasks, customers, requests or whatever your problem involves. The Objects tab lets you see each object, browse and add its records, and adjust its fields.
Overview
The Objects tab becomes available once the Solution agent has created at least one object. It lists the types of records that the solution stores, such as tasks, customers, or requests, with each object's Object name, Description, number of Fields, and when it was Last updated. You can search, filter, sort and save views.
The list follows the solution: when the agent adds a new object while you're watching, it appears without a reload. There's no button to create an object here — ask the agent instead, so the new object becomes part of the solution.
Opening an Object
Click an object to open it in place, beside the chat. A Records / Schema switch at the top chooses what you see; it opens on Records. Use the back arrow to return to the list.
Records
Records shows the object's data as a table, with a column for each field. You can search, hide and reorder columns, and more records load as you scroll.
Click a record to open it in a side panel. The pencil icon opens the edit form.
Each record's menu offers Edit, Share and Delete, depending on your permissions on that record.
An object with no records shows "No records — You haven't created any records yet."
Adding Records
Click Add Record at the top of the Records view and pick a method:
Method | Description |
|---|---|
Start from scratch | Fill a form field-by-field to create one record. |
Fill via JSON | Paste a JSON object or array of records. |
Upload file | Import records from a CSV or Excel file. The import runs in the background and a notification shows its progress. Offered when you have import permission. |
Generate via prompt | Auto-generate records from a prompt — handy for sample data while you test. Offered when your environment supports it. |
Add Record appears only if you have Edit permission on the object, and is disabled while the object has no fields.
Required fields and the object's primary key are enforced when you create or edit a record — you can't save until they're filled in correctly.
Schema
Schema shows the object's fields in the platform's standard field editor. With Edit permission on the object you can add, change and remove fields; without it, every field is read-only. Saving the schema switches you back to Records so you can see the effect.
Tip: For changes that should show up across the solution — such as a new field that should appear on a form — ask the Solution agent rather than editing the schema yourself, so it can update the screens and workflows that use the object at the same time. Editing a field directly here changes only the object — forms, workflows and other screens that use it don't update automatically.