Account: Ignore Unchanged Fields Not Respected for to Many Association Fields

Previously, Bullhorn ATS fields with a multi-select edit type weren’t respected by VMS Sync’s Ignore Unchanged Fields account setting. This caused user edits to fields marked as “do not touch.” VMS Sync no longer edits these ATS field types when Ignore Unchanged Fields is enabled.

 

Controlling which ATS fields VMS Sync can edit ensures manually-entered ATS data is preserved, preventing manual rework.

Credentials: Healthtrust Position Failure When VMS Raw Data is Enabled

Previously, enabling VMS Raw Data on Healthtrust credentials caused positions to generate an ATS Save Fail report. Healthtrust field handling has been updated, and positions now process as expected with this Credential setting enabled.

 

VMS Raw Data displays additional fields on the Position JSON that users can reference in rules to populate ATS Job fields. Timely position delivery helps submit candidates to positions as quickly as possible.

Positions: Blank Vector Agency Interview Type

Previously, some Vector positions parsed a blank Agency Interview Type value when a value was present in the VMS. We have updated how these values are parsed to account for field label differences in the VMS. This ensures VMS Sync successfully parses an Agency Interview Type value for all Vector Positions with a value in the VMS.

 

The Agency Interview Type indicates how the hiring manager will conduct the Candidate interview (virtual, phone, email, etc.). Accurate field parsing reduces product swivel and manual edits.

Positions: Magnit Position Failure with Attachments Enabled

Previously, some positions were failing to process when Credential Feature Position Attachments was enabled. VMS Sync now successfully parses all Magnit Positions (with and without attachments) with the Position Attachments Credential Feature enabled.

VMS attachments commonly contain additional job details not found on the VMS Position posting. Both Position and attachment delivery are important to reduce req delay and improve ATS Job accuracy.

Positions: Magnit Position Type

Previously, some Positions parsed a blank Position Type value when a valid Type value was present in the VMS. We have updated how Magnit Type values are parsed to account for back-end data formatting differences in the VMS. This ensures VMS Sync successfully parses a Position Type value for all Magnit Positions with a valid Type value in the VMS.

Position Type is commonly used to set ATS Employment Type, which can determine the fields and values available on an ATS Job. Accurate Position Type parsing is important for data accuracy and manual edit reduction.

Positions: Magnit Supervisor Parsing

Previously, VMS Sync was parsing Manager as a long string of text for some positions, resulting in delivery failure. VMS Sync now correctly splits Magnit’s Manager value into Supervisor First Name and Supervisor Last Name components. VMS Sync also now parses Manager from Magnit’s Duties field when Manager is blank in the VMS.

Magnit uses Manager to indicate the main point of contact for a Position. Many Customers use Supervisor First and Last Name to look up and assign ATS Company Contact to Jobs.

Positions: Staffbot Status Update

Positions removed from Staffbot weren’t generating a Closed VMS Status. VMS Sync now automatically changes the Status of any Position removed from Staffbot to Closed. This ensures inactive positions are categorized appropriately in the ATS and users are notified of the change appropriately.

Status updates are a core function of VMS Sync, as candidates can only be submitted to positions in a submittable state (usually Open and with a non-zero Opening Count).

 Submittals: CKEditor Error

A red security warning message would briefly display in the Comment field of the Submit to VMS form. We have updated our CKEditor version and added styling to hide this message.

 Submittals: Healthtrust Match Candidate Owner Auto-population

An issue was resolved with Healthtrust Submittals. Previously, Candidate Owner and Match Candidate Owner were not auto-populating on the Submit to VMS form. Healthtrust submissions made from the ATS also displayed the Match Candidate Owner as the VMS Sync API user. VMS Sync now pre-populates the Match Candidate Owner based on the following logic:

• Match Candidate Owner = User making the submission
• If the submitting user isn’t a valid Healthtrust user, Match Candidate Owner = Candidate Owner
• If Candidate Owner isn’t a valid Healthtrust user, Match Candidate Owner = blank

When Match Candidate Owner is submitted to Healthtrust as blank, VMS Sync populates Match Candidate Owner with the value of the Healthtrust Candidate Owner on the Healthtrust submission. If no Candidate Owner exists for the Candidate in Healthtrust, VMS Sync populates the VMS Sync API user.

VMS Sync pre-populates Healthtrust Candidate Owner based on the following logic:

• New Healthtrust Candidates – Candidate Owner = User making the submission
• Healthtrust Candidates – Candidate Owner = blank

When Candidate Owner is submitted to Healthtrust as blank, VMS Sync won’t pre-populate a value. Candidate Owner will remain blank. This ensures VMS Sync doesn’t override any values left intentionally blank by Healthtrust users.

Pre-population increases the speed of the Candidate submission process and reduces the end-user swivel between records and products.