The current Compare App Versions feature does not provide a detailed comparison of the Tulip Table Queries and Aggregations referenced an app.
This is a gap because query and aggregation configuration can directly affect the data presented to an operator and the values used in app logic. For example, a change to a query filter, sort order, record limit, app-input mapping, or the aggregation linked to a query can change which production records are included and how their data is summarised. Likewise, changing an aggregation type and source field can change a calculated value that may be displayed or used to drive an app decision.
For GxP-relevant applications, this is a change-control and data-integrity risk. During review and approval, teams need objective evidence of what changed between versions and whether that change impacts data. Without a version diff for queries and aggregations, a reviewer cannot reliably assess the changes from the current version-comparison feature.
Requested enhancement
Please extend Compare App Versions to show added, removed, modified, and renamed Tulip Table Queries and Aggregations associated with the compared app versions.
For each changed Query, please show a version comparison of:
- Query name and referenced table
- Filters, including app-input
- Sort configuration
- Record limit
For each changed Aggregation, please show a version comparison of:
- Aggregation name
- Parent Query used by the aggregation
- Aggregation type
- Source field (where applicable)
If Query and Aggregation versioning already exists for import/export or restore behavior, please expose the version/snapshot identity and configuration history in the App Version comparison workflow.
Ideally, the comparison should also identify where the changed query or aggregation is used in the app—for example, as an Interactive Table data source, a variable data source, or within app logic.
This would make version comparison more complete, improve change-impact assessment, and provide stronger review evidence for regulated GxP workflows.