Skip to Content
Raydo

Browser and Desktop Submission Audit Starter

Review a test form and connect browser and desktop evidence to its submission receipt.

The browser_desktop_submission_audit template sets up Open → Fill → Upload → Review → Submit → Browser proof → Desktop evidence → Delivery. It uses both a browser execution target and a desktop computer-use target. Connect the actual accounts, form controls, attachment source, and desktop app before using this sequence.

InputHow the draft uses it
portalUrl, accountNameRequired text for the open-node context. Confirm the actual browser profile and logged-in account.
submissionTitle, submissionBody, uploadFileRefsRequired text mapped into the fill and upload nodes. Check the actual field selectors and the upload adapter's file contract.
desktopAppName, desktopEvidenceZoneThe app name is required. The optional zone describes where to look for proof after submission.
reviewApproved, reviewSummaryRequired Boolean branch input and optional review notes. The submit node carries a separate approval requirement.
{
  "portalUrl": "https://example.com/staging-form",
  "accountName": "Test account",
  "submissionTitle": "Test submission record",
  "submissionBody": "Check the draft fields and attachment in staging.",
  "uploadFileRefs": "/path/to/test-attachment.png",
  "desktopAppName": "Test app",
  "desktopEvidenceZone": "Test app's receipt panel",
  "reviewSummary": "Check attachment, destination, and expected receipt",
  "reviewApproved": false
}
  1. Use a staging form and sample files. Verify the browser connection and permissions. The upload node is before review, and the draft maps uploadFileRefs as a string. If the route expects an artifact ID, such as the Raydo browser extension's upload route, bind a ready supported artifact and map its artifactId and the actual upload control before testing.
  2. Check the edit route with false. For the submit route, use a designated test target and check the approval on the actual submit node.
  3. Compare the submission receipt with the browser proof and the desktop evidence. To keep them as a project deliverable, package them into an artifact and map it to the supported project delivery target. If the run failed during evidence collection, check the external receipt before retrying submission.

See Browser submission workflows and Browser configuration.

Browser and Desktop Submission Audit Starter