The Idea:
Creating a new System Configuration Model in Looker (or a structural update to the existing Project Descriptor Model) would allow System Administrators to fully report on their system setup and configuration in Clarity, regardless of whether those elements are actively attached to a program or screen.

The Problem:
Currently, the Project Descriptor Model is incredibly helpful for reviewing active system setups. However, it is structurally limited because many of the views only pull in data when elements are actively in use (e.g., connected to programs or screens).

Because of these underlying data joins, users cannot report on everything that is actually configured in the system. This creates a significant blind spot for System Administrators, especially during new customer onboarding, system migrations, or routine system audits.

Concrete Examples & Limitations:

Example 1: Program Templates
Currently, the Program Templates view in the Project Descriptor Model uses a join that only pulls in templates linked to programs. If a System Administrator wants to view all templates that exist in Clarity to determine which are in use and which are orphaned or obsolete, they are unable to do so. It is not possible in Looker to report on Program Templates that are not linked to a program.

Current Workaround: Admins must manually review every single template in the Clarity UI, or customers with BYOBI access can pull the information using SQL (or seeing if Bitfocus could provide this information through a support request).

Example 2: Picklists and Multi-Select Fields
Admins would like to have a comprehensive view of all picklist values for all picklist and multi-select fields to validate their setup. This is particularly helpful for new customers as they are reviewing the initial configuration of all of their fields. However, the current Picklist view in the Project Descriptor Model is joined to the "Questions" view, meaning it only contains fields currently connected to a screen. It is impossible to report on picklist values for fields that are not yet on a screen in Looker.

Current Workaround: Admins would need manually review every single picklist and multi-select field that is not on a screen in the Clarity UI to review all picklist values, or customers with BYOBI access could pull the information using SQL (or seeing if Bitfocus could provide this information through a support request).

Impact:
Implementing a System Configuration Model would improve the user experience for System Administrators by enabling them to:

Audit System Health: Easily identify unused, obsolete, or duplicate configurations (like unlinked templates or incorrect picklist values) to keep their Clarity environment clean.

Streamline Onboarding: Allow new customers to validate their full system setup and field configurations in bulk via Looker before going live.

Reduce Technical Burden: Eliminate the need for customers to have to use SQL to query this data (or rely on Bitfocus support to provide it).

Thank you for considering this enhancement to make configuration management in Clarity more transparent and accessible!