Nimra AhmedandGitHub
bea9d0835b
* refactored Storybook UI * refactored Storybook UI * removed extra cards from the doc, added card for ui components * added hover behavior to doc page & made it look selected * separate storybook docs and tests * separating storybook tests and docs * fixed spelling errors in docs * Final round of edits for frontend, added backend folder architecture * Created CODE_OF_CONDUCT.md * Add code of conduct to contributing.md * doc changes * fixed broken links
17 lines
787 B
Plaintext
17 lines
787 B
Plaintext
---
|
|
title: Custom Objects
|
|
sidebar_position: 4
|
|
sidebar_custom_props:
|
|
icon: TbAugmentedReality
|
|
---
|
|
|
|
To elevate our platform experience and adhere to our dedication towards versatility, we've successfully integrated custom objects (objects available only in a specific workspace).
|
|
Users across different workspaces can now seamlessly access custom objects using a dynamic GraphQL schema.
|
|
|
|
## How it works
|
|
|
|
Custom objects trace their roots back to metadata tables that dictate the shape, name, and type of the objects. All this information is housed in the metadata schema database, consisting of tables:
|
|
|
|
- **DataSource**: Details where data is stored.
|
|
- **Object**: Describes the object and is linked to a DataSource.
|
|
- **Field**: Outlines an Object's fields and connects to the Object. |