The pages
Six pages across the top of the app for administrators, plus the Operation page reached from the catalog. Everyone else sees two: Upload and History. There is no sidebar. Every page opens with one sentence saying what it is for, every tab has a short caption, and every field has a tooltip.
| Page | Who | What |
|---|---|---|
| Overview | everyone | The dashboard: records moved each way per day, records per web service, slow operations, and one line saying how many things wait on a person. Pick a window: 30 days, 90 days, past year, all. |
| Operations | data engineers | The business objects this app moves, one web service at a time. Search for one, switch it on or off, choose how it sends when there is a choice, set its retention, and open its extract or submit to configure it. |
| Operation | data engineers | One operation, opened from the catalog. Configure it, run an extract now, manage validation rules, and see how to feed a submit. The operation is in the page URL, so a refresh keeps it open. |
| Upload | everyone | A file of records into Workday: pick the business object, download its template, upload the file. The batch is checked at once and opens in History. |
| History | everyone | Two views. To do lists what asks for a person, each row with what to do in front. Everything is the timeline of submits, extracts and files, newest first. Clicking a row opens its Detail page. |
| Detail | everyone | One submit, extract or dropped file. A submit shows its records with their outcome and Workday ID or, when some failed, the two ways to fix them. The XML tab keeps the exact request and answer per record. |
| Reconcile | accountants, data engineers | Confirm that submitted records exist in the extract and carry the expected status, and that every line came back with the values sent. |
| Admin | administrators | Tenant-wide settings, entitlements, the Workday setup checklist with a test per operation, the connection test, the heartbeat and the inbox. |
Overview
Overview answers one question: is data moving? It shows records moved each way per day, records per web service, the slowest operations, and a single line counting what is waiting on a person. It shows no error lists; failures are rows with something to do on History, never a chart.
Operations
Operations is the catalog. Three tabs:
- Business objects. Pick a web service, search, and switch business objects on and off in an editable table. Each row carries the On switch, Auto tuning, Retention days and a read-only Set up column that says whether every part has passed its Workday authorization test. Business objects are all or nothing: switching one on creates its tables, pairs its submit with its extract and starts every part; if any part cannot start, nothing starts and the page says why. Switching it off stops every part and keeps the configuration.
- Web services. Which web services the catalog lists. The four financial services are on by default; switch on the ones your tenant uses. A web service with a business object on cannot be switched off.
- Config. One business object's Submit, Extract and Setup sub-tabs. Submit and Extract configure the operations; Setup is the Workday checklist with a Test setup button.
The catalog describes business objects in plain words, such as Submit: files hold for approval and Extract: daily 01:00. Workday operation names appear only on the Operation page.
Operation
One operation, with the same panel the Config tab shows and its own URL, so links from History and Detail land here and a refresh keeps it open. For an extract: configure the table prefix, key, load type, incremental window and schedule; run it now for an ad hoc window; see the highwater mark and the tuning levels the next run starts at. For a submit: the Feed tab with the exact table names, inbox folder and template; validation rules; the source key and load method; and the Spec tab showing which repeating elements became line tables and which became JSON attributes.
Upload
The one page most people need. Pick a business object that is on, download its template (one sheet per table, root first), fill it, upload it. The batch is checked at once and opens in History with every record's outcome. Administrators find the same form on the submit's Feed tab.
History
Two views of the same timeline.
- To do lists what asks for a person, with the action in front of each row: Fix the records and submit again, Submit, Submit again, Run the extract again, Fix the file and upload again. A held submit is submitted from here; a submit with rejected records opens for correction; a rejected file says why it was refused.
- Everything is the full timeline of submits, extracts and files, newest first. Every row names its business object and its step: Upload (the file and this app's checks), Submit (the calls to Workday) or Extract, with how it stands, such as Submit: rejected by Workday.
Filters above the grid narrow it to one business object, one step or one state; the rows are what everyone works from.
Detail
One submit, extract or dropped file.
A submit lists its records with their outcome and Workday ID. When some failed, it offers the two ways to the same correction: edit the cells in the grid, or download the records as a workbook with the error beside each row, correct it, and upload it in the same tab. Errors carry one of four categories: checked here, Workday rejected, Workday warning, connection. The XML tab keeps the exact request and answer per record, redacted of credentials, and names the Snowflake task that ran the batch.
An extract run shows each operation it ran with the records written per table, the phases that took the time, and any error, with a button to run it again.
A dropped file shows how it was routed, what the checks said, and the submit it became.
Reconcile
For every submit paired with an extract: each succeeded record matched to the record the extract read back by Workday ID, classified as confirmed, not yet extracted, missing or status drift. The Lines tab lists only the lines that were not found or differ, column by column. The same views are there for SQL. See Reconciliation.
Admin
Tenant-wide settings in groups (Compute and schedule, Extracts, Submits, Retention, Appearance), the connection to Workday with its test, entitlements per user, the Workday setup guide for download, the heartbeat switch, and the inbox with Scan inbox now.