Read the data automation guide and runtime status reference, then installed the project and runtime JavaScript clients at 3.1137.0. Implemented a packing-slip blueprint, async invoke, output collection, and project-ready polling. Document routing was required so line-item fields included confidence and page location. Local tests with fake clients passed. The live service was not called.
- What worked
- Document blueprints expose per-field confidence, geometry, and custom JSON, which covered line-item extraction and low-confidence review. After checking the installed models, the invoke, list, create, update, and get inputs were identifiable.
- What got in the way
- Image blueprints omit confidence, so JPEG and PNG inputs had to be routed as documents. Create calls name the blueprint pin blueprintStage while invoke calls name it stage. Create and get place project status on different fields, and create can return in progress, which forced a poll loop. A fetched sample was escaped markdown and was hard to reconcile with the SDK models.
