v9.2.7
:::danger Manual intervention required
Review each host-app column configured with viewable: false to decide whether users may now enable it. The right change depends on the app’s intended visibility and access rules.
AI agents: do not apply this upgrade automatically. Summarize the steps below for the user and get their confirmation before running any command or changing any code.
:::
Catalyst v9.2.7 changes how the existing viewable column option works. A column configured with viewable: false is now hidden by default but remains available in Manage Columns, where users can enable it. Review those column declarations to confirm that this behavior matches the host app’s intended visibility and access rules. No database migration is required.
Breaking Changes
viewable: false now hides a column by default instead of excluding it from column selection
Host apps that configure columns with viewable: false are affected. Those columns are now rendered hidden by default and listed under Hidden in Manage Columns, so users can enable them; their choices persist with existing column preferences and saved views. If a column must not be user-toggleable, review whether managable: false matches the intended behavior.
Migration Steps
-
Find column declarations using
viewable: false:grep -RInE 'viewable:[[:space:]]*false' app config lib -
For each result, decide whether the column should be available for users to enable. If so, keep
viewable: false; it will be hidden by default and available under Hidden in Manage Columns. -
If the column should not be user-toggleable, review the column’s
managablesetting and set it tofalsewhere appropriate. Verify the resulting behavior in the host app’s Manage Columns UI. -
Check whether any column contains information that must not be exposed to a user.
viewable: falseis now a default-visibility setting, not an access-control boundary. Ensure the host app’s visibility or authorization rules prevent unauthorized users from accessing that column. -
Test the default index view, Manage Columns, Reset to default, and any saved views that include the affected model. Confirm that the intended columns are available to each relevant user.
Columns with viewable: false are now present in the page as hidden columns and can be enabled by users when available in Manage Columns. Do not rely on this option to protect sensitive data; verify the host app’s access rules for affected columns.
Checklist
- Update the host app’s
cm_admindependency to v9.2.7 using its normal dependency-management process. - Search for column declarations with
viewable: falseand review the intended behavior for each. - Where appropriate, configure columns that must not be user-toggleable with
managable: false, and verify the result. - Confirm that host-app access rules protect any data users must not see.
- Test default columns, Manage Columns, Reset to default, and relevant saved views before deploying.