On Wednesday, July 19th, 2023, we released Matador Jobs 3.8.10 to all our users. This release is a small update with a few minor enhancements that couldn’t wait for Matador 3.9.0 and some bug fixes that were worth bringing along for the ride. Let’s dive in–a pun to express how I’d rather be finding a pool to avoid this sweltering Phoenix summer (today is the 20th day of 110ºf or 43.3ºc or greater here!)

Bullhorn’s API Authentication Updates

Last week, Bullhorn released an update that improved their API Authentication routines to prefer the use of Datacenter-specific authentication servers. While geographically distributed datacenters have been in use since the first days of Matador, back then and until now, a Matador site would still initially log in at the one centralized authentication server and then after login be redirected to the datacenter where your data was stored. This Bullhorn update now asks that API systems perform initial login on new geographically-distributed authentication servers as well, and moving forward, and for backward-compatibility, if an API system tries to log in at a different datacenter, the API system will be redirected before login.

This is a great change that will result in more performant routines, especially for non-US based users, but Matador needed an update to its code adapt to this Bullhorn change. Note that older versions of Matador will still use the single centralized authentication server (until it stops working, if ever) but will be redirected by Bullhorn’s backward-compatibility, which means older versions will now be slower than before. This version of Matador, and any moving forward, will only use the centralized server on the first-ever login for the site, thereafter re-authenticating from the datacenter specific authentication servers and taking advantage of the Bullhorn API authentication process update and its performance benefits.

The only potential issue we see moving forward is that your connection will break in the rare case that your data is moved from one datacenter to another. If this happens you will need to reset your Bullhorn Connection in Matador after the change, but this is extremely uncommon to have your company data migrated to other client clusters.

As a bonus, since we were working in the same section of our code, we were also able to remove the “Datacenter” step of the Bullhorn Connection Assistant as its former functionality is now automated, streamlining the user connection to Bullhorn even more.

Search by ID in Matador Search

It is common request: “Can Matador search take me directly to a job if I search the ID?” The answer has been no in the past. We provided a way for users to separately have a “Search by ID” field added to search forms, but we felt the added complexity on search would cause issues.

We have found a reliably efficient way of extending this desired behavior and, since it is fully backward-compatible and requires no changes to use, are deploying it early with this hotfix release. Provided your ID numbers are non-zero integers (some future integrations use alphanumeric IDs and thus won’t qualify for this) and a non-zero integer number is provided in the search field without any other text characters, Matador will switch to searching on the external ID, and if found, return the job matching that ID.

You can still use the separate Search By ID search field, and future non-Bullhorn integrations may require it if the job IDs from those systems are not integers.

Minor Bug Fixes

This release also fixes the following minor bugs discovered since 3.8.9.

  • Do not set the salary_string and salary_formatted values for a job when the fallback/default salary value is used and is not set or set to zero.
  • When a fallback/default salary value is used and is a non-zero, set the salary_string value.
  • Fixed issue where a Google reCAPTCHA script installed by another theme or plugin but not used by Matador’s Google reCAPTCHA solution would cause Matador’s form to not pass validation.
  • Identified and fixed issue in Matador’s new sync routine (currently in beta) that could be encountered when a sync step is not found as a class method or callable and thus resulting in an infinite loop.
  • Identified and fixed two issues in Matador’s new sync routine (currently in beta) where a class property that was to be read via late static binding was being read as an instance property, causing issues in some implementations. Notably, locally created jobs were being removed during a remote sync.

Update Now!

Matador Jobs 3.8.10 is released for automatic* update to all subscribers as of Wednesday, July 19, 2023. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: if your current installed version is 3.8.0 to 3.8.4, you need to manually install this update.