Lookups & Reference Data
Where do the shared code lists behind every module’s statuses and types live?
Lookups are the platform’s categorized reference data — the code lists behind statuses, types, and categories in every module. Each value carries a stable internal key and localized display text, so screens and reports stay consistent while labels translate.
Referenced across3 other parts of continON
How it works
Reference data is one governed taxonomy rather than a list per screen. Lookups are organized into categories, can nest hierarchically, and separate the stable internal key a record stores from the display text a user sees. Renaming a label never breaks a stored record, and the same value reads correctly in every language the organization registered.
Every application resolves its lists through the same shared service, across dozens of consumer areas — so a value maintained here updates each dropdown, status, and category that uses it. There is no reconciling one module’s type list against another’s.
Adjacent to reference data sits navigation configuration: the order and placement of screens and submodules in each application’s menu is administered data too. A process published in the Builders can even place itself into that menu — configuration reaching all the way to where users find their work.
What the table carries
| # | Maintained | Resolved against it |
|---|---|---|
| 01 | Stable keys, localized labels | Records store an unchanging internal key; users see translated, org-specific display text. |
| 02 | Hierarchical categories | Lookups organize into categories and nested structures, matching how real classification works. |
| 03 | One service behind every list | All modules resolve statuses, types, and categories through the same shared reference-data service. |
| 04 | Menu and submodule configuration | Which screens appear, and in what order, is administered data — per application, without code changes. |
See lookups & reference data running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.