# Changelog of Workday Jobs Scraper — Company Job Boards (`adderleydata/workday-jobs-scraper`) Actor

- **URL**: https://apify.com/adderleydata/workday-jobs-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/adderleydata/workday-jobs-scraper.md

## Changelog

### 0.1 — first public version

- Any number of Workday career sites per run, by the link to the company's careers page on myworkdayjobs.com: with or without a language code, a posting link, or the career site's API address. The tenant is taken from the host and the site name is matched without regard to case, so two links to one career site are read once.
- The list is read 20 postings per request, Workday's largest page, up to the total its first page reports; a page past the end, which Workday answers with its first page again, ends the search. Each posting saved is read once more for the facts the list does not carry.
- A search that reaches Workday's cap of 2,000 postings is split by one of the career site's own filters, usually job category, and each part is read.
- Output in the Adderley Data `job.v1` schema: every location the posting lists, the primary first, with the posting's ISO country code and, where the label's order is clear, city and region; work arrangement from the company's remote-type label, with Flex and a flexible-office label read as hybrid; employment type from Workday's time type; the posting's start date as `postedAt`, at 00:00 UTC; its end date as `expiresAt` where the career site publishes one; the employing organisation as `company.name`.
- Pay is read from the posting's text where it states a range; Workday's public records have no pay field. No range, no salary.
- Filters: search keywords, one search per keyword with Workday's own search; locations and job categories through the career site's own filter values, so a posting listed as several locations is found when one of them matches; days since posting, from 1 to 30, from the age the list states. A relative age is never written into a row as a date.
- Incremental mode: `changeType` of NEW, UPDATED, REAPPEARED or EXPIRED, decided from the list's title, location, remote type and requisition id before any posting's own record is read; unchanged postings skipped, not charged and not read again. An edit to the posting's text alone is not reported.
- A search that returns fewer postings than it reported, because the career site changed while it was being read, is read once more from the start; postings already saved are skipped.
- Optional full descriptions from the same request as the posting's facts, with email addresses, phone numbers and personal profile addresses redacted by default, and link addresses and images dropped from the HTML.
- A career site Workday does not know, or a tenant on the wrong wd host, fails that site's request once with a message saying so. The other career sites in the run are kept, and nothing is declared expired. A posting taken down between the list and its own record is saved with the list's facts, and the log says why.
- No recruiter names, emails or phone numbers in any field: Workday's public records have none, application-form references are never read, and `job.v1` has nowhere to put one.