VNDLY (platform)
Workday VNDLY is a cloud-native VMS aligned to the Workday suite. composerID treats VNDLY as a destination system of record — publishing Intent Records and maintaining the audit spine — with tenant mapping validated in a customer sandbox because API documentation is customer/partner-scoped.
The public API facts composerID's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.
| Authentication | Customer/partner-provisioned credentials within the Workday ecosystem. Confirm auth flow (OAuth 2.0 / ISU-style integration user) per tenant. |
|---|---|
| API style | Customer-scoped APIs; public endpoint documentation not confirmed. Workday-suite alignment drives object and required-field conventions. |
| Base URL | Provisioned per customer tenant. No public base URL. |
| Objects | Requisition, Worker, Assignment, Timesheet, Supplier (per Workday-ecosystem conventions) |
| Events / webhooks | Not publicly documented; plan poll-based reconciliation and confirm event options per tenant. |
| Rate limits | Not publicly documented; defined per tenant/integration agreement. |
“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary — especially around custom fields, approval flows and object extensions.
Deterministic mapping
Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).
Tenant discovery
composerID can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.
Enrichment loop
If the target platform requires a field the Intent record doesn't yet have, composerID emits an enrichment_request back to the intake layer.
An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.
| Object | Canonical fields | Platform target | Required status | Notes |
|---|---|---|---|---|
| Requisition (Contingent) Create worker request |
role_title, location, start_date, cost_center, worker_type | Customer API (Workday ecosystem) | Tenant required | Workday alignment drives required fields |
| Worker / Assignment Assignment lifecycle |
worker_id, dates, rate, status | Customer API | Tenant required | Back-sync into intent timeline |
Idempotency & drift — publish + reconcileExpand
Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, composerID supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.
Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). composerID is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.
How scanning works
High-level flow
What gets produced
Portable artefacts
Important — where this platform is tenant-definedExpand
Workday VNDLY documentation is customer/partner-scoped. composerID starts with minimum viable mapping and relies on tenant discovery (required fields, custom fields, code lists) to generate a working MappingProfile.
Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.