 What’s New in FlightPath Data 1.1.88

FlightPath Data 1.1.88 is the largest release since the product launched. It deepens AI-assisted authoring, adds an agentic operational layer, expands CsvPath Language significantly, and rounds out a number of operational features that make FlightPath a more complete edge data governance platform.

AI-Assisted Authoring

FlightPath’s sidebar AI assistant can now help developers and BizOps team members with four core authoring tasks:

▶ Generate validations from requirements: describe a data contract in plain language and get a working CsvPath script as a starting point
▶ Explain validation scripts: Get a complete plain-English rule-by-rule walkthrough of what an existing script does
▶ Create test data: Generate sample files that exercise your validation logic before real data arrives
▶ Refactor scripts: Clean up, reorganize, or modernize existing CsvPath code without rewriting from scratch

The assistant works from a sidebar throughout the authoring environment without interrupting your flow. Learn more about FlightPath AI →

Agentic Workflows

Three new operational capabilities reduce manual intervention in day-to-day data operations:

▶ Arrival activations: Automatically trigger runs when data files arrive — no scheduling, no polling, no manual handoff
▶ Async job control: Full visibility into running jobs: status, metrics, and results accessible at any point, with clean access to results when a run completes
▶ No-code webhooks: Fire automatically based on run outcome criteria, keeping downstream consumers, monitoring tools, and notification systems informed without anyone in the middle

Learn more about FlightPath Agentic Workflows →

Config Variable Interpolation

FlightPath’s environment variable support is significantly expanded in 1.1.88. Projects can use OS-level or project-specific environment variables interchangeably. Config values written in ALL CAPS are automatically resolved against the environment. New in this release: config values can contain {} replacement tokens that pull from OS or project environment variables — and those resolved values can themselves can point to further environment variables, enabling flexible, layered secret management that keeps credentials cleanly separated from runtime configuration.

Default File Registration Path Templates

Path templates — which control how registered files are stored below their named-file location — can now be set as a default directly in the named-file definition. Previously, the same template had to be passed explicitly on every registration. Setting a default eliminates that repetition and ensures consistent storage structure across all registrations for a given named file, whether you’re mirroring an up- or downstream system’s layout or building a more browse-friendly local structure.

Post-Run Transfers

Post-run transfers now support all files generated during a run — not just the primary output — and work across all configured storage backends. This removes a significant limitation for teams publishing results to S3, Azure Blob, GCP, or SFTP destinations.

Parquet Output

FlightPath now supports generating Parquet files to a data schema defined using the parquet() function. Like line() — FlightPath’s structural schema function — multiple parquet() functions can be active simultaneously, each generating its own Parquet file. This makes it possible to decompose a flat CSV into separate relational entities in a single pass: a hospital visit record with doctor, patient, and diagnosis fields on every line can produce three properly structured Parquet files, with foreign keys, without any intermediate transformation step.

New and Expanded Functions

1.1.88 adds 10 new analytical and transformation functions, including support for JSON Query and SQL — two capabilities that significantly expand what’s expressible in CsvPath Language without leaving the validation framework. See the full functions reference →

Grid View for Run Metadata

The JSON grid view returns for system metadata files. The code editor introduced in 1.1.87 is excellent for editing JSON and JSONL directly, but less suited to exploring run metadata. The grid view gives operations teams a cleaner, more scannable way to inspect what happened in a run without switching to an external tool.

Default Markdown Documentation Files

Named files and named-paths groups now automatically generate a Markdown documentation file on creation. These files are the only operational files in FlightPath that are user-editable, and they live alongside the assets they describe. It’s a small feature with a clear signal: documentation of data operations belongs in FlightPath, not in a separate wiki or nowhere at all.