ATS v2: Customizing Candidate Stages

Note: To take advantage of the features mentioned in this documentation, your Org needs to be using Package Version 7.16 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.

This article applies to ATS v2s using the ATS v2 data model only.

Overview

There are several customizations available for CandidateClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Stages within ATS v2 including adding, removing, and renaming stages. This article walks you through how to add, remove, and rename stages.

This article is intended for System Administrators.

Add a New Stage

  1. Add the new stage name as a picklist value in the TR1__Stage__c picklist field within the Application V2Closed A BH4SF custom object introduced when new data model ATSv2 was added to the core product object.
  2. Enable the new picklist value for all relevant Record Types.
  3. Run the following line of script in the Developer Console by clicking the Setup icon at the top right of screen, and then Developer Console. Go to Debug > Open Execute Anonymous Window and enter the following:
    Copy
    TR1.RecordTypePicklistDescriber.refreshPicklistMetadata();
  4. Go to Application page layout in Application V2 object and create a new section with Stage Name Details. After doing this, add the related fields under this section.
  5. Set up a data entry page for the newly created stage (if required):
  6. Add the appropriate Job stage banner (stage icon) for the newly created stage in Setup > Static Resources.

Remove an Existing Stage

  1. Remove the Stage Name from the TR1__Stage__c picklist values in the Application V2 object.
  2. Go to the Application page layout in the Application V2 object and remove the related section.
  3. Run the following line of script in the Developer Console by clicking the Setup icon at the top right of screen, and then Developer Console. Go to Debug > Open Execute Anonymous Window and enter the following:

Copy
TR1.RecordTypePicklistDescriber.refreshPicklistMetadata();

Rename an Existing Stage

Via Translation Workbench

  1. Go to Setup >Translation Workbench and click Translate:
    • Select the appropriate language.
    • In the Setup Component drop-down, select Picklist Value.
    • In the Object drop-down, select Application V2.
    • Click the plus icon (+) next to a stage to expand the view.
  2. Add a new label for each stage in the Picklist Value Label Translation column.
  3. Save the changes.
  4. Update the relevant Custom Labels by navigating to Setup > Custom Labels to find the related custom label for the stage. Below are all the Custom Labels created for each stage.

Via Database

  1. Go to the Application V2 object and search for the Stage__c field and click on it.
  2. Every stage appears here so click Edit next to the desired stage name.
  3. Add the new value for the stage.
  4. Save the changes.
  5. Update the relevant Custom Labels by navigating to Setup > Custom Labels to find the related custom label for the stage. Below are all the Custom Labels created for each stage.
    •  Custom Label Name Value:
      • ATS_Submittal_Stage Submittal
      • ATSv2_Offer_Stage Offer
      • ATSv2_Send_Out_Stage Send Out
      • ATSv2_Closing_Report_Stage Closing Report
      • ATSv2_Application_Stage Application
      • ATSv2_Internal_Interview_Stage Internal Interview

If you are renaming or translating the Closing Report stage, please complete the process by adding the new Closing Report stage name to the following Custom Labels:

Add Banner

  1. Navigate to Setup > Static Resources.
  2. Create a new static resource with the name ATSv2_ + your new stage name.
  3. Upload the banner image for your new stage under the Static Resource.
  4. If the stage name includes two words (such as Final Decision), then combine both words and add a prefix string in the Static Resource name (ATSv2_FinalDecision).