fm-analyze

To analyze FileMaker business logic, you query the DuckDB catalog to evaluate variable naming, call chains, and field comments. This semantic analysis derives the functional intent and business purpose behind specific scripts and fields.

Understanding obscure FileMaker scripts requires mapping contextual incoming and outgoing script dependencies. By evaluating call chains and touched data entities, you can reveal workflow triggers and derive the underlying business intent.

Yes, you can audit complex legacy FileMaker solutions by performing multi-hop dependency analysis. This approach maps script call chains and touched data entities to identify the specific business logic behind obscure workflows.

Yes, you need read-only access to the fm_catalog.duckdb database to perform multi-hop dependency analysis. This access allows the semantic evaluation of variable names, call chains, and field comments without modifying data.

Semantic code analysis derives business intent from FileMaker objects by evaluating context from variable naming, layout labels, and field comments. It bridges raw code and business purpose to explain why a script or field exists.

A limitation of analyzing FileMaker business logic through a DuckDB catalog is the reliance on existing catalog metadata. If variable names, field comments, or layout labels are missing or poorly defined, deriving accurate functional intent becomes difficult.