Understanding Check Results

File Statuses

Every file checked receives one of four statuses:

Pass rate is calculated as: Passed / (Total - Skipped) x 100.

Viewing Results

In the Check History tab, click a completed check run to expand it. Each file is listed with:

• Status dot (green/red/amber/grey).
• File name (clickable link to open in Forma for Forma checks; plain text for local uploads).
• File path in the CDE (or just the filename for local uploads).
• Rule set name badge (in per-folder mode).
• Source badge -- a purple "Local Upload" badge appears on results from local file checks.
• Action buttons -- open in Forma, download, re-check (hidden for local upload results since files are not stored).

Searching and Filtering

Use the search bar above the results list to filter files by name. Type any part of the file name and the list filters in real time.

Run-Level Cards (Register & Numeric Range)

Above the per-file table, the detail page shows summary cards for any run-level rules that produced data. These are pinned at the top so you can see the overall picture before drilling into individual files.

Register Completeness Card

When the run includes one or more Register Cross-Reference rules, a completeness card appears for each rule with:

• A large completeness ring showing the percentage in the centre, colour-coded green / amber / red by threshold.
• Found / Total — entries in the register that have a matching file.
• Missing — entries in the register with no corresponding file.
• Unexpected — files in the folders whose value isn't in the register.

This is the fastest way to see whether a run satisfies your MIDP/TIDP at the current stage. The detailed missing/unexpected lists are still available by expanding the corresponding [Register Check] row in the file list below.

Numeric Range KPI Tiles

When the run includes one or more Numeric Range rules that produced violations, a small KPI tile appears for each rule showing the count of out-of-range values. Use these to spot misnamed sheet numbers, revision counters, or floor levels at a glance.

Both card types only render when there is data — runs that don't use those rule types are unaffected.

Violation Details

Click a file row to expand its details. Each violation shows:

Run-Level Results (Register Cross-Reference)

Register Cross-Reference rules don't belong to any single file — they evaluate the whole run at once. Their results appear in the file list with a purple [Register Check] badge instead of a filename, and report two kinds of violations:

• Missing files — list entries (e.g. document numbers from your MIDP) that have no matching file in the checked folders. The "Actual" field shows (not found).
• Unexpected files — files in the checked folders whose value isn't in the register list. These are flagged as warnings rather than errors so you can decide whether they're legitimate additions or mistakes.

Run-level entries don't have a Forma file link, file path, download button, or PDF preview — there's no single underlying file. They group all violations from one rule into one entry, so you'll see one row per Register Cross-Reference rule even when it produced dozens of violations.

Extracted Content

For files with zone extraction, the details also show:

• Rule set name (if per-folder mode was used).
• Template name and match type ("size match" or "fallback").
• Zone values with pass/fail/not-checked indicators:
  • Green checkmark -- zone value matched the expected metadata.
  • Red X -- mismatch found (shown in the violations above).
  • Grey dash and "(not checked)" -- zone was extracted but no rule referenced it.

Violation Status Workflow

Every violation can be tracked through a four-stage lifecycle:

Open  -->  Acknowledged  -->  Waived  -->  Resolved
                          \-->  Resolved

Change the status using the dropdown on each violation row. Status changes are saved immediately. For triaging large runs, use the Bulk action row in the table toolbar to flip every violation in the current filter to Open / Acknowledged / Waived / Resolved at once — see Managing Violations.

Linked Forma Issues

When a violation has been pushed to Forma as an issue (see Pushing Findings to Forma Issues), the row gains a few extra surfaces:

• A Forma Issues column in the table shows the live status badge — #801 (open), #802 (closed), etc. Click the badge to open the issue in Forma.
• Expanding the row reveals an ACC Issues card listing every linked issue with status, ID, and a direct link.
• The status colour reflects the latest known state: blue for open / draft, green for closed / answered / completed, red for in-dispute / rejected, grey + strikethrough for deleted.

The Sync Forma button at the top of the table re-fetches every linked issue from Forma in one shot — useful when a webhook event was missed.

Two-Way Status Sync

When the Forma webhook is registered (it is by default after the first push), status changes flow both ways:

• Closing or completing the issue in Forma → the linked violation is auto-marked Resolved in Foreman.
• Reopening the issue in Forma → the linked violation flips back to Open, and a snackbar notifies you the next time you load the run detail page.

Auto-changes are stamped as system updates so they're distinguishable from human edits. Waived is never overwritten — it's a deliberate human decision.

Pushing Approved Files to the Cloud

Once you're happy with the result of a check, you can publish the file to a Forma, SharePoint, or Box destination folder without leaving the run-detail page. From the action bar:

• Push all files at the top of the table opens the dialog with every eligible file in the run pre-selected. The split-button caret next to it lets you pick Forma, SharePoint, or Box as the destination cloud.
• Tick checkboxes next to specific files to enable the Files to Cloud button in the sticky selection bar at the bottom — only the selected files are sent to the dialog.

Each push uploads the file to the destination folder you pick, fills in custom attributes from PDF zone values and filename segments, stamps Foreman QA Status, and creates either a new item or a new version (auto-detected by name). For runs that include local-uploaded PDFs, this is the one-click promote — no second upload, no re-keyed metadata.

See Pushing Files to the Cloud for the full mapping reference, type-aware writes, same-cloud carryover, the duplicate-name preflight, and the auto-push-on-pass option. Save your row configuration as a preset and compose multi-source values via Combine values… for richer mappings.

Deleting Check History

Click the delete button on a check run row to permanently remove the run and all its results. This action cannot be undone.

Next Steps

• Managing Violations -- bulk-update statuses, multi-select rule filter, and triage workflows
• Re-checking failed files -- re-run only the failed/warning files after a fix
• Exporting Results & PDF Reports -- download results as CSV, Excel, or branded PDF (now includes Forma issue columns)
• Pushing Files to the Cloud -- publish reviewed files with metadata pre-filled (Forma / SharePoint / Box)
• Attribute mapping presets & auto-memory -- save and reuse the push mapping
• Pushing Findings to Forma Issues -- create issues from violations in one action
• QA Dashboard & Trends -- view aggregate metrics