Repository navigation
Home
Accelerator Version: v0.6.0 Published By: MFGx Platform Compatibility: Fuuz Industrial Intelligence Platform 2026.8.0+ Guide Last Updated: 2026-08-15
This guide describes the Plex Keyring Schema accelerator as it exists at the version stated above. It is provided for informational and enablement purposes to customers and partners and does not modify, supplement, or take precedence over any signed order form, statement of work, or master services agreement. Where this guide and a signed agreement conflict, the signed agreement governs.
The complete Plex read surface, as Fuuz data models. 182 models covering every readable collection endpoint in the Plex developer portal, generated from Plex's own API dictionary rather than hand-written — so coverage is a property of the generator, not of how much time someone had.
This is the schema layer of the Plex keyring: somewhere to land every readable Plex object, with foreign keys resolved into real, enforced relations so applications traverse rather than join.
| Data models | 182 |
| Fields | 4,560 (2,356 of them Plex's own) |
| Relations | 465 forward, 283 reverse collections |
| Endpoints covered | 119 collection GETs + 63 sub-resources |
| Dictionary | Plex developer portal, 2026-08-05 |
Models only. Connections, extraction flows and the endpoint switchboard are separate concerns and are not installed by this package.
Derived from Plex's published documentation, and pinned to it. The models were generated from the API descriptions on developers.plex.com as of the dictionary date above — 283 read contracts, 359 response schemas, harvested and turned into models by a generator rather than written by hand. Nothing Plex changes propagates here on its own. See How This Was Built and The Vendor Dependency.
Install this once per Plex PCN, into its own Fuuz tenant.
The primary key of every row is Plex's own key. Two facilities both have a PART-1000, so two PCNs sharing one tenant would collapse onto the same row — silently, with nothing in the data to show it happened. One tenant per PCN makes that impossible by construction rather than by convention.
| If you are… | Read |
|---|---|
| Evaluating whether this fits your environment | Overview → Discovery Q&A |
| Implementing it for a client | Capability Map → Included vs Custom |
| Installing it | Walkthroughs |
| Planning an upgrade | Versioning & Compatibility |
| Deciding who supports it | Support & Maintenance |
Customer & Partner Guide v0.6.0