OA Workflow Auto-Submit

Problem It Solves

OA form submission often stalls on login, workflow entry, dropdowns, person pickers, and final validation. This skill targets Weaver OA workflows by chaining browser automation, workflow ID matching, and form operations into a repeatable process.

How It Works

• Two execution modes: prefer bua + browser hybrid mode; fall back to built-in browser mode when bua is unavailable or disconnected.
• Workflow matching: read references/workflow_ids.md before execution and resolve the workflowid using exact match, keyword match, and default generic flow rules; ambiguous matches prompt for confirmation.
• Key steps: log in to OA → open the form via the AddRequest.jsp direct link → confirm required fields → fill and submit → validate requestid and page title → save a screenshot and report key details.
• Interaction handling: use snapshot for interactive elements and JS evaluate for field labels, hidden menus, and dropdown options that standard snapshots may miss.

Boundaries

Best suited for OA environments with a configured address, user permissions, and a debuggable browser. It stores sensitive credentials in long-term memory, requires explicit confirmation of required fields before submission, and depends on the specific OA DOM structure for person search, retraction, and hidden menus. New workflows require workflow IDs and SOP files.