Workflow product

Portal Preflight

Use Portal Preflight before retrying failed uploads.

Step 1

Identify the likely rejection reason

Start with file type, extension, metadata, checksum, file size, supported-format, filename, and packet-manifest checks before changing the file or launching a server job.

Step 2

Preflight PDF packets

Check size drivers, page count, page size, text-layer and scan signals, password protection, hidden content, attachments, metadata, and compression options before uploading a final PDF copy.

Step 3

Preflight image uploads

Check dimensions, aspect ratio, safe-area behavior, file-size targets, metadata privacy, format, and compression before uploading images to a strict destination.

Step 4

Preflight data and archives

Validate CSV structure, product-style headers, archive paths, duplicate names, nested archives, and upload chunk sizes before files are parsed, extracted, or imported by another system.

Workflow notes and help

Review PDFs, images, archives, CSV files, and Office documents before uploading them to file-size-limited portals or handoff systems.

Ready or needs review
  • Ready to retry: The file type, size, page count, dimensions, naming pattern, and packet manifest match the limits you entered or reviewed.
  • Needs PDF review: The PDF is encrypted, scanned, oversized, has unusual page sizes, hidden-content signals, attachments, or metadata that should be inspected before upload.
  • Needs image review: The image is the wrong format, too large, incorrectly sized, outside the needed aspect ratio, or still contains metadata/privacy signals.
  • Needs packet review: The ZIP, filename set, CSV headers, duplicate names, chunk size, or manifest details need attention before a handoff.