We are enabling this for all Workday push customers via a phased roll out. To organize the required permission changes, we will be in touch with you. If you have any questions or queries, please reach out to your customer success manager

Overview

Beamery has performed a comprehensive upgrade of its Workday Push Integrations pipelines to Workday SOAP API version v44.1. This upgrade improves platform performance, stability, and data integrity, and introduces several key improvements that were not available with the older API version (v31.2).

Key Updates

• Performance and Stability: The previous pipeline sent all candidate fields and all associated applications in a single, large Put_Candidate request, leading to timeouts and performance degradation. The upgrade decouples pipelines and optimizes data payloads.
• Data Integrity: The upgrade ensures better data integrity and resolves limitations from the older API. For example, the v31.2 API could not push middle names for USA candidates — v44.1 resolves this.

What’s Changing

1. Workday Candidate Push API Upgrade
   The Workday Candidates Push pipeline now uses Workday API version v44.1 Put_Candidate (also uses Get_Candidates and Get_References).
    

   Field/Area	Before	After
   Candidate Field Updates (Name, Location, Phone)	All fields sent regardless of modification.	Only modified fields (name, location, phone) are sent, preventing unnecessary overwrites.
   Merged Candidates	Updates sent but API returned false positives without actually updating.	Updates are no longer sent for candidates merged in Workday but not in Beamery. These are now handled as rejections.
   Phone Device Type	Not mandatory; "Mobile" used as default.	Mandatory in v44.1. Mapping checks config first, then matches the closest available type, with "Mobile" as final fallback.
   Twitter/X URL	Sent in both Website data and Social Network Username fields.	Sent as Website data only. Social Network Username no longer works as intended in the current API.
   Middle Name	Not sent for US candidates (v31.2 limitation) or unsupported countries.	Now sent for US candidates. Still not sent for unsupported countries (Canada, UK, India, etc.).
   Existing Employee (Worker_Reference)	Could overwrite restricted candidate fields, causing unreported failures.	v44.1 enforces restrictions. Name, location, email, phone, website, and social media are NOT pushed for records with a Worker_Reference. Tags and prospect resume data ARE still pushed.
   Prospect Data (Summary, Skills, Experience)	Pushed to all existing and new applications.	Pushed only to new applications and the Prospect profile (not pre-existing applications). If no Prospect profile exists, one will be activated.

2. Workday Application Push — Decoupled Pipeline
   A separate pipeline for Workday Application Push has been implemented, also using v44.1 Put_Candidate.
   Key change: Application resume data (Summary, Skills, Experience) is now sent only for new applications. Existing applications no longer receive updated resume data through this process.
3. Workday Attachment Push — Decoupled Pipeline
   The Workday Attachment Push is now a decoupled pipeline using v44.1 Put_Candidate_Attachment. There is no change in functionality or behavior — this aligns with the previous implementation where attachments used a separate API request.

Permissions Change

• The upgrade from SOAP API v31.2 to v44.1 requires a permission change for Resume_Data content.
• Affected fields: 
  • Prospect_Data.Prospect
  • Resume_Data.Summary
  • Resume_Data.Skill_Data
  • Resume_Data.Experience_Data
• Required permission:
  • "PUT Candidate Data: Attachments"

Without this permission, the system returns: "You don’t have security access to add or make changes to a prospect’s attachments."
If you already have attachment push enabled, this permission is already set and no action is required.

Important Notes

• If your Workday tenant requires "Source" as mandatory when Prospect profiles are activated, you will need to create a new Source "Beamery" using the Maintain Recruiting Sources task in Workday.
• LinkedIn and Facebook URLs continue to be transmitted within the Social Network URLs field.
• Workday no longer supports Get or Put operations for merged candidates in recent API versions.

Frequently Asked Questions

• Why have you decoupled Candidates & Applications on the push?
  • The combination of pushing both on a single API request led to longer processing times and frequent request timeouts. Separating them reduces the risk of long processing times and push failures.
• What does this decoupling mean for the separate Application push?
  • Applications are now their own entity within the Beamery Data Model, matching the Workday data model. Previously, Skills, Experience, and Summary updates were pushed to both new and old applications. Now they are pushed only to new applications.
• What happens when there is no Prospect profile in Workday?
  • Skills, Experience, and Summary are pushed to the Prospect profile via Candidate Push. If no Prospect profile exists, one will be activated and populated. Any new applications created from the Prospect profile will inherit the latest updates.
• Why is the PUT Candidate Data: Attachments permission required even without attachments?
  • Workday made permissions more granular from v43.1 (2024R2 release). Skills, Experience, and Summary are part of "Resume Data" in the Workday data model, and this permission is required to update that data. Even without attachment push enabled, the permission is still needed. This was verified in collaboration with Workday.