API cards and API tables provide a more flexible and customizable way to present information on your homepage, dashboards, or other overview pages.
API cards
API cards are used to display concise information about specific spaces, applications, or objects. They also serve as quick links to the mentioned e.g., space, other resources, or trigger additional details if necessary.
API cards can show a wide variety of information, including but not limited to:
- Space: Space name, number of objects in the space, short description, space owner, etc.
- Application: App name, number of objects in multiple spaces, a brief description, etc.
- Object: Object name, related space or app, and other metadata.
- Dashboard: Dashboard name, description.
Display options
- Card view: Individual cards are presented as separate units.
- List view: Cards can also be displayed in a condensed list or table view for easy scanning of multiple items.
Optional interactivity
While API cards can display information, they may also include optional interactive elements:
- Clickable Links: The card can link to spaces, applications, objects, or dashboards.
- Pop-up Details: Cards can include buttons that trigger a pop-up with more detailed information.
- Custom Links: Other links or actions can be configured based on specific needs.
API tables
API tables provide a tabular view of objects and metadata, offering a more structured and detailed format for presenting information. These tables can be added to homepages, app overview pages, or parent object pages, and they can be fully customized to display a wide range of object-specific information.
API tables support flexible column configurations to display the necessary information.
Column widths and your rows-per-page choice are saved per user. Drag a column edge or change the rows per page, and the layout persists across page reloads and navigation.
A table can open at a default page size set by whoever configured it, but your own rows-per-page choice always takes precedence over that default.
To reset column widths to their defaults, use the Reset button in the table header. The button appears only on tables headed by a section title or a panel header.
Manage columns
Every API table that lists Dawiso objects has a Manage columns control in the table header; tables backed by an external data source do not offer it. You can show, hide, reorder, and search the table’s columns.
You can also display additional columns: attributes and user relations, such as Steward or Owner, of the object types the table can show.
Click Restore default columns at the bottom to remove customizations.
The offer adapts to the table’s content:
- Only attributes and user relations that occur in the table’s rows are offered.
- Only columns from spaces you can read are offered.
- Existing columns are listed first; addable columns follow, sorted alphabetically by label.
- Same-named attributes, for example Created on both Table and View, carry the owning object type in brackets — icon first, then name — in both the popover row and the column header; unique names stay plain.
Column values and settings behave as follows:
- Long plain-text values shorten to an excerpt with a … more control; rich-text values keep their formatting and images in a fixed-height cell with no control to expand a cut-off value — the full content stays on the object’s detail page.
- Your column selection is remembered per table and per context (space, application, or hierarchy); a remembered column the current context cannot show is dropped automatically.
- Hiding a column clears its filter. Unchecking an added column removes it from the table and clears its filter and sort — check it again to re-add it.
Added columns are excluded from bulk editing, and added user relation columns cannot be sorted.
Customizable columns
The columns in your API table can be customized by configuring the API table in packages. While that is for more advanced users, here is a non-exhaustive list of possible columns
| Category | Example column |
|---|---|
| 1. Basic information | Object name: The primary identifier or title of the object., ID or Unique identifier: A unique ID associated with the object (if applicable)., Path or URL: The object’s location or URL within the system., Space name: The name of the space where the object resides. |
| 2. Ownership | Assigned users: Any users assigned to manage or monitor the object., Data owner or steward: The entity or person who owns the rights to the data or object. |
| 3. Status and workflow | Workflow status: The current status of the object in its workflow (e.g., “In Progress,” “Completed”)., Approval status: Whether the object has been approved, rejected, or is awaiting review. |
| 4. Temporal data | Create date: When the object was created and who created it., Last updated: When the object was last modified and by whom. |
| 5. Descriptive attributes | Description: A brief summary or explanation of the object., Tags or categories: Any tags, labels, or categories associated with the object for easier organization., Object type: The specific type or classification of the object (e.g., document, image, workflow). |
| 6. Metrics and performance | Fullness score: A metric indicating how complete or populated the object is., Usage statistics: Data on how often the object has been accessed or modified., Activity history: A log of recent actions or changes made to the object. |
| 7. Custom fields and metadata | Custom metadata fields: Any other user-defined or system-generated metadata associated with the object. |
Filtering columns
Every column can be filtered from its header. On a column that shows related objects, the filter is a searchable multiselect: pick the related objects you want instead of typing a name. It only offers objects that are genuine matches for that relation, so no selection returns zero rows.
The list of objects loads only when you open the filter, and it loads more as you scroll to the bottom. You can search the list by name. Selecting several objects in one column returns rows that match any of them; filtering on two different relation columns returns rows that match both. Columns that show assigned users, such as Assigned users, keep the previous text-based filter.
Select all selects only the objects already loaded in the list, not every possible match. Scroll to load the rest of the list first if you need to select everything.
Actions
Through the configuration of api-table properties using packages, the following features can be added.
| Action | Description |
|---|---|
| Action buttons | Custom buttons can be added to tables, enabling users to trigger specific actions, such as running SQL-based tasks. |
| Mass-editing and bulk actions | Bulk actions can be performed on multiple objects simultaneously. Users with the appropriate permissions can mass-edit fields such as workflow status or ownership, streamlining the process of managing large datasets. |
| Numeric range filter | Aggregated statistic columns support filtering by numeric range (object karma, number of favorites, views in last month, all-time views, and number of relations). Click the filter icon and enter a from value, a to value, or both. Leaving one field empty applies an open-ended bound, and entering the same value in both fields filters for an exact match. |
| Tabs with quick filters | Quick filter tabs can be integrated into the table to provide immediate access to specific subsets of data. For example, filters might include recently updated, owned by me, or in progress, allowing users to focus on relevant data quickly. |