Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Status: 📝 Planned (Phase 2 & 3 expansion)
Spec: PF-23 Phase 2 & 3 Expansion
Parent Spec: PF-23 Data Manager - Object Browser

​
Overview

PF-23 (Data Manager) provides a unified Object Browser (list, detail, fields tab, favorites, categories). The Phase 2 & 3 expansion wires the object detail view to PF-25 (Raw Data Editor), PF-26 (Object Permissions), PF-31 (Page layout management), and PF-28 (Object relationship visualization) via tabs and layout integration.

​
Integration Points (from expansion spec)

Consumer (PF-23)ProviderIntegration TypeDescription
Data Manager object detailPF-25Embed / Link”Raw Data” tab shows PF-25 raw data UI for the selected object
Data Manager object detailPF-26Embed / Link”Permissions” tab shows PF-26 permissions UI for the selected object
Data Manager list/detail viewsPF-31Platform LayerLayout controls and persistence per PF-31
Data Manager object detailPF-28Embed / Link”Relationships” tab or section consumes PF-28 when available (read-only)

​
Context Passed to Child Features

  • Organization: organization_id from the current object detail context (PF-23 object metadata or selected object’s org).
  • User: Current user from useCurrentUser(); permission checks delegated to PF-25 and PF-26 when entering their tabs.
  • Object context: Selected object’s api_name, object_type (core/custom), and any identifier needed by PF-25/PF-26 (e.g. table name, object metadata id).

​
Entry Points

  • Location: src/platform/data-manager/ (object detail tabs).
  • Raw Data tab: Renders PF-25 entry point (e.g. component or route) with object context; tab visible when PF-25 is implemented and user has PF-25 view permission.
  • Permissions tab: Renders PF-26 entry point with object context; tab visible when PF-26 is implemented and user has PF-26 view permission.
  • Layout (Phase 3): Layout controls and persistence per PF-31; consumed in Data Manager list/detail pages.
  • Relationships (Phase 3): Relationship view/tab consumes PF-28 API or component when PF-28 is available.

​
Permission Alignment

  • PF-23 does not define new permission keys for these tabs. Tab visibility and content access are gated by:
    • PF-25: Use permission keys defined in PF-25 (e.g. raw data view/edit) when rendering or entering the Raw Data tab.
    • PF-26: Use permission keys defined in PF-26 (e.g. object permissions view/manage) when rendering or entering the Permissions tab.
  • Object detail always enforces PF-23’s own access (org member can view object metadata); child tabs enforce their own permissions on enter/render.

​
Platform Layer Usage

  • Data Manager: @/platform/data-manager — object list, object detail, tabs container.
  • PF-25: Consumed via embed or link from Data Manager; no new platform layer export required for PF-23.
  • PF-26: Consumed via embed or link from Data Manager; no new platform layer export required for PF-23.
  • PF-31: Layout storage and API per PF-31; Data Manager is a consumer of layout configuration.
  • PF-28: Relationship metadata and UI per PF-28; Data Manager exposes a “Relationships” tab that uses PF-28 when available.

​
Event / API Contracts

​
Rollback

  • Phase 2: Non-breaking; feature flags or tab visibility can hide Raw Data and Permissions tabs.
  • Phase 3: Non-breaking; layout and relationship features can be toggled or disabled per PF-31/PF-28.
Last Updated: 2026-02-27