Syncing vs Indexing in Daxtra

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

Information sent to DaxtraClosed A BH4SF partner. One of the Search and Match / Resume Parsing services providers integrated with BH4SF is both synced and indexed within Daxtra. This article covers both topics and their differences.

Syncing vs Indexing

Syncing records to Daxtra (to the SMWS database) or sending updates to Daxtra refers to the process of sending data related to the Daxtra CandidateClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Profile.

Creating a new Contact, parsing a new resume, updating a resume, or updating Contact fields selected to be used as an Advanced Filter will trigger an update of the Candidate Profile stored on the Daxtra database. For this data to be converted into searchable information, Daxtra needs to indexClosed A collection of files that can be searched by client data entity types. When records can be found in training login, but not the live system, it may require a bootstrap of the index. the data we send.

When a new Contact is created through parsing, the request for syncing and indexing uses a low priority queue; it is sent immediately and then stored in that queue and processed based on the server load. If there is no mass sync of records going on, the new data will be synced and indexed in an hour.

Admin Note:

Daxtra runs Update Indexes every hour and Full Indexes once a week.

  • Partial indexes (or Update Indexes) are run once every hour from Monday to Friday.
  • Full indexes are performed once a week on weekends according to a schedule (Daxtra can provide details on this schedule)

There is also an option to have the Full Index set up to run every night, but that is only recommended for small databases (ieClosed Internet Explorer is an out of date browser provided by Microsoft. Use Chrome!, small number of CandidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider.).

Update Indexes include all records since the last Full Index. If there have been a lot of records created or updated since the last Full Index the Update Indexes take longer to complete.

It’s important to understand the relation between updating records and indexing (especially when it comes to mass updates) as making high demands on the indexing process will result in performance issues for the server that hosts the SMWS database. Depending on the scenario, disabling indexing temporarily or for the duration of a mass update might be required (this needs to be done on the Daxtra side).