Apps and Data Flow Notebooks

Open Conversation → Apps for App notebooks, or Data Flows → Notebooks for data notebooks. An administrator authors notebooks in the selected tenant and project. A notebook combines explanations, configuration, retained examples, SQL and tests. Saving creates a draft revision.

Test a notebook

1. Select your tenant/project and notebook. Save any pending edits.
2. Choose Run tests, Run samples, Run section, or the Run button on one stage. Required dependencies run first.
3. Expand the run history. Inspect the actual queued, running, succeeded or error state. A failed prerequisite blocks downstream work.
4. Open Computed output to inspect typed rows and page through them. A complete sample is required for verification.
5. Inspect each comparison and its differences. Missing references, ambiguous keys or incomplete coverage cannot pass.

SQL data stages use a bounded retained table named sample. Configured transforms use the same data transformations as the existing Flow designer. These sample runs do not read customer sources or write customer destinations. Document extraction uses a saved template and an authorized retained parsed document; label examples first and review extraction output.

An edit makes prior results stale. Model, parser, comparison and execution changes can also invalidate evidence. Run affected checks again before requesting activation.

When a data stage uses an extraction table, the run waits for you to accept the extraction result in Documents Automation → Monitoring. It then uses the table's declared grain, keys, types and currency fields. Correcting that result invalidates downstream evidence; run the checks again.

For a Channel test cell, configure the test destination, case revision and assigned reviewer, then choose Send test notification. Expand the run history to see the queued and provider-accepted states, and use the notification history to check the receipt and reviewer action. Only configured test destinations are allowed.

Review proposed edits

Expand Proposed notebook edits. If prompt generation is available, describe the change and choose Propose edit. Select a pending proposal, inspect its before/after diff, then choose Accept reviewed diff or Reject diff. Acceptance creates a new draft revision and requires new tests. A proposal cannot approve or activate itself.

If prompt generation is unavailable, you can still review pending proposals or edit a draft directly. Generated edits are restricted to declared resources and approved sample/reference files; unavailable connectors or fields must be resolved before continuing.

Activate or restore a tested version

1. Run the declared tests for the saved revision. Document extraction also requires a current passed golden pilot.
2. Expand Tested versions and activation and choose Request version review.
3. The notebook owner reviews the exact revision and chooses Approve exact version.
4. Choose Activate approved version. Changes since testing or approval block activation.
5. Use Run active version on retained samples to inspect the approved version independently of later draft edits.

Critical failures cannot be overridden. An owner can override a verified standard test only by recording a reason and residual risk. An unverified result cannot be overridden.

To restore a previous tested version, enter a reason and choose Restore this version. Restoration preserves case and ledger history. A critically paused version cannot be restored; correct the issue, rerun tests and approve a new version.

An active version remains tied to its tested source. A critical mismatch pauses future runs. If test-channel monitoring is configured, a failure alert is queued. Remote acceptance of an email or chat message does not prove delivery to its recipient.

Pilot and availability

Use 20 representative historical documents with separate calibration and unseen holdout examples. Agree on matching keys, currency, record grain, tolerances and required accuracy before the pilot. The provided synthetic examples check software behavior; they do not certify customer accuracy or delivery.

Customer PO writes, arbitrary live notebook execution and automatic financial business actions are not enabled by saving or activating a notebook. Existing Flow designer links/history remain available. A migrated sample comparison does not activate the legacy schedule or duplicate it.

For document setup, labeling and result review, see Documents Automation.