api

 In part 1 I covered some ground regarding integrating Bullhorn and Drupal without getting into too much detail. Hopefully part 2 will answer some questions how to do it.

I have a few gripes with Bullhorn outside of the performance issue I mentioned earlier:

 If you've had encounters with the recruiting industry from a developer's point of view then the name Bullhorn should be no news to you. There are other players on the market, Monster being the most known overall in the states. I used to work for a company in Europe almost a decade ago that had recruiting offices in 9 countries so I've been there before and seen some oddities along the way - HR-XML for example.

In order to integrate Bullhorn data there are a few things to keep in mind:

Domain Access 6.x-2.2 was released yesterday. This is the last 6.x release, further development will go into 7.x branch.

Things to be aware of from a developer perspective:

  • Change to hook_domainwarnings() - http://drupal.org/node/692772. Won't break existing modules but will prevent new functionality from working.
  • New hook_domain_warnings_alter() for cases where hook_domainwarnings() is possibly overridden by Domain Settings - http://drupal.org/node/721148
  • Now with basic Drush support
  • Generate domains on the fly with Devel