I generate an AppDoc PDF regularly to keep a project memory file in sync with my app’s schema, and I noticed that Security Filters (defined under Data > table settings > Security tab) are completely absent from the export. I checked every table in my app and the string “Security Filter” does not appear anywhere in the generated document, even though I have Security Filters actively configured on several tables.
This creates a real problem for documentation and auditing. AppDoc otherwise does a thorough job exporting column definitions, Valid_If, Editable_If, Show_If, Required_If, views, and actions, so it’s surprising that Security Filters, which are one of the most important access-control mechanisms in an app, are left out entirely. Anyone relying on AppDoc as a source of truth for how their app’s data access is configured will get an incomplete and potentially misleading picture, since the exported schema will look like there are no row-level restrictions at all when in fact there are.
Requested fix: include each table’s Security Filter expression in the AppDoc export, ideally right alongside the other table-level settings (similar to how “Are updates allowed?” is currently shown).
Workaround: none. I currently have to keep a separate manual note of each table’s Security Filter outside of AppDoc, which defeats the purpose of using AppDoc as a single source of truth.
Thanks for the update, and to the engineering team for the fix. I generated a fresh AppDoc PDF and can confirm Security Filters are now showing up correctly. The expression is exported in full, and it appears right alongside the other table settings like “Are updates allowed?” and “Expression for update mode,” which is exactly what I was hoping for.
In my current app only one table has an active Security Filter configured, so my test was limited to that single case, but it came through cleanly and completely. Really appreciate the quick turnaround on this one, it makes AppDoc a much more trustworthy source of truth for documenting access control.