Admin: ATS v2: Configure Reject Origin For Reject Flow

To use the Reject Origin in a Reject Flow you must configure it.

Three values for the Reject Origin picklist are available on the Applicationv2 object:

1. Go to Object Manager > Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) v2 > Fields & Relationships > Rejection Origin.
   • Ensure the picklist has the values you need:
     • Client A Company is the organization where the contact works. This can also be called the Client.
     • Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider.
     • Internal
2. Go to Setup > Custom Metadata Types > Rejection Origin Mapping.
   • Create a record for each association of Reject Reason and Reject Source. The record should be configured as follows:
     • Rejection Reason: Should contain the API API, or Application Programming Interface, is used by customers to create custom career portals or to take advantage of Data Mirror/DataMart. Bullhorn prefers to use REST API. name value of the Rejection_Reason__c picklist field from ApplicationV2 object.
     • Rejection Origin: Should contain the API name value of the Rejection_Origin__c picklist field from ApplicationV2 object.
3. To enable popup on hover for the ATS List View One of the three user Interfaces in ATS v2 (the others being Kanban View and Table View) (chevron view), a new fieldset ApplicationRejectPopupFieldSet must be created on the ApplicationV2 custom object in the Subscriber’s Org.
   • This fieldset should contain all the fields needing to be displayed at a glance without clicking into the application record (EX: Rejection Origin).
4. Give users access to field Rejection_Origin__c when saving a value to Rejection_Reason_c.
   • This permission has been included in the managed package Permission Sets referencing the Rejection_Reason__c.