Bullhorn for Salesforce Job Board Integration

Note: To take advantage of the features mentioned in this documentation, your Org needs to be using (Undefined variable: bh4SFVersions.Latest Package Version) or newer. See Release Notes for more details about which features were introduced in each release. If you would like to upgrade to the current release, contact Bullhorn for Salesforce Support.

Overview

With a Job BoardClosed A website where open jobs are advertised integration, users are able to post JobsClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. externally so candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. can submit applications from the JobClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. Board pages or your website. When an ApplicationClosed First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) is submitted, CandidateClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Contact and Application records are created in your Org. This article familiarizes you with job board integrations and how they function.

The Job Board integration is not part of the core Bullhorn for Salesforce package but is offered as a separate development option during the implementation process. For details around the cost of configuring the Bullhorn for Salesforce Job Board integration and customization options, please reach out to the Bullhorn for Salesforce Support Team or Sales Department.

The Job Board implementation can include:

Option 1: Force.com Pages and an XML Feed

Configuration Overview

  • Within Setup, create a Domain Name.
  • Create a Site.
  • Assign Permissions to the Guest Site Profile. This will be the anonymous user applying for jobs from the z board.
  • Enable Visualforce pages.
  • Assign CRED permissions on the Job, Contact, and Account objects.
  • Enable field visibility for all fields on the Job object.
  • Update relevant Custom Labels and Static Resources with new Job Board information.
  • Style Customizations.
  • Changes to the logo’s URL, favicon, and rights reserved in Job TemplateClosed In BH4SF, this mainly refers to email templates page.
  • Create a Custom Setting for the Job Board.
  • Map Job fields to the XML feed in Custom Settings > Talent Rover Properties > Jobs Feeds.

Requirements for Job Posting

Any Job record created in your Org can be posted externally once the below conditions are met:

  • The Post Externally checkbox is selected.
  • The name of the Job Board is selected in the Job Board picklist.
  • The Job Status is not equal to Closed.

Job Field Mapping

Data from the Job record is sent to the XML feed based on the mapping configured in the Jobs Feed Custom Setting. The Job post will be created using the values captured by the XML feed.

In this example, the Job’s TR1__External_Job_Title__c field is mapped to the <title> tag in the XML feed.

Below is the standard field mapping to the XML feed. This can be customized using the Jobs Feed Custom Setting.

TR1__Element_Name__c (XML Feed Tag) TR1__Field_Name__c
description TR1__ClientClosed A Company is the organization where the contact works. This can also be called the Client._description__c
date TR1__Open_Date__c
lastmodifieddate LastModifiedDate
country TR1__County__c
referencenumber TR1__Job_Number__c
companyClosed A Company is the organization where the contact works. This can also be called the Client. TR1__Job_Board__c
category TR1__Primary_Background__c
experience TR1__Experience_RequirementsClosed Object. Its records store details about a Job position to be filled__c
url id
city TR1__Regional_Area__c
state TR1__State_Area__c
title TR1__External_Job_Title__c
education TR1__Education_Requirements__c
description TR1__Client_description__c

Job Board Pages

Once the Job Board Site has been created, two registration pages and a search page are available. These can be customized and embedded in your own website with custom development.

This is the Job Search page which shows every Job that is posted externally.

You can see the full Job post by clicking on the Job Title. Clicking the Apply button at the bottom of the Job Post page launches the Registration page. The Job object has package fields that are designed to be used for external posting, so you can have an internal and external title, as well as internal and external Job descriptions. Ensure that you map the correct field to the XML feed.

On the Job Register page, the Candidate is asked to enter personal information such as their name, email address, and address.

Once the mandatory fields are populated, clicking Continue navigates the Candidate to the second registration page. This page lets the Candidate upload a resume and finish applying for the Job.

Candidate Records and Applications

When a Candidate applies with a resume, we check if there is already a Candidate record in the Org with the same personal information. If none is found, a new record is created that includes the parsed resume.

If the Candidate applies without a resume and there isn’t an existing Contact record in the database, we create a Contact record with the data entered in the Registration form.

In both cases, an Application record is also created for that Candidate related to the relevant Job.

Option 2: XML Feed Only

If you don’t want to redirect from your own JobBoard or website to a force.com site, you can use HTTP REST services. With the HTTP REST services, you can create your own HTML registration form and that can pass the XML feed information as a JSON body to Bullhorn for Salesforce endpoint.

We provide an XML feed that contains all the necessary information to post jobs externally and to receive applications. The third party website administrator has to 'consume' the XML feed. Our XML feed allows Job posts and HTTP REST services to receive Applications from a third party website.

No specific knowledge of the Salesforce platform is required because our services follow Service-Oriented Architecture (SOA) standards. The third party developer is required to know how to parse XML and how to post a JSON payload on the HTTP Rest service. These are basics of SOA and developers doing EAI integrations would be familiar with these concepts.

Sample XML feed: http://trideas.force.com/jobboard/jobsfeed?jobboard=talentrover