Overview
Support workflows where files arrive before the source application has its final object identifier.
Problem
Many forms need attachments before the parent business object is committed.
Solution
Upload into governed File-Vault state and later bind the file to the authoritative source app, object type, and object id.
How it works
A trusted application uploads the file, creates its business record, then calls files.bind so File-Vault records the final relationship and governed destination context.
Who is this for
Application Engineer
Product Team
Expected outcomes
- No temporary filesystem implementation in the source app
- Durable source-object attachment after record creation
Key metrics
Security impact
- File reference, source application, source object type and id, folder/routing metadata, and audit state · PII: depends on the uploaded file and source object metadata
Compliance
- Trusted app provenance, operation grants, resource authorization, audit, and controlled file routing
Availability & next steps
Enterprise