📚 CV Uploads, Parsing & Previews
Which documents appear in the “Change Preview CV” dropdown on a Contact’s Experience tab?
The dropdown shows documents stored in the Contact’s CV folder. This folder is automatically created when a Contact is created and is intended to hold CVs parsed by services such as Daxtra or Textkernel. Only suitable document types appear in the preview selector; supporting parser artefacts (such as .txt or .xml) are not shown.
Can non‑CV files appear in the CV Preview selector?
They can, but only if users manually upload non‑CV files into the CV folder. Best practice is to store only CVs in this folder to ensure a clean CV Preview experience.
Why doesn’t a manually uploaded CV always generate a preview?
CV previews are generated when a CV is parsed. Manually uploaded CVs do not automatically produce a preview unless processed through parsing.
Are duplicate checks performed when uploading CVs via Textkernel?
No. Textkernel behaves the same as Daxtra On Demand — duplicate checking is not performed during upload.
How does the “Existing Contact” field get updated after CV upload?
The field is updated when a CV is parsed on the Contact record or when using Bulk CV Parsing (Textkernel only).
🔍 Searching & Filtering Data
Do users need to use asterisks (*) in Boolean Search?
Yes — unlike structured keyword search, Boolean Search does not automatically apply wildcards. Adding an asterisk (*) expands results by acting as a wildcard.
When should quotation marks be used in Boolean Search?
Quotation marks should be used when searching for multi‑word phrases (for example, "software developer"), ensuring the exact phrase is matched.
Does deactivating a Tag remove it from Search results?
No. Deactivating a Tag does not trigger re‑indexing, and inactive Tags may still appear in Search results.
📊 Managing Vacancies
Can customers identify Vacancies created using the Clone function?
Currently, Vacancy records do not have a field indicating cloning. Audit history records the action as “Create”, not “Clone”.
Can you remove a Vacancy from a Project?
Yes. Within the Vacancy, then in the Owner Information section, where you add the project, once it's added, you can click the "x" to remove the project from the Project field. Then save the vacancy record and it will then delist from the project.
Are there risks in changing Vacancy type (e.g. Contract to Permanent) mid‑process?
Yes. Changing vacancy type can introduce risks, particularly around existing shortlists and financial data. These scenarios require careful testing to avoid inconsistencies.
⚙️ System Behaviour Explained
Why does sending an email automatically create a Connection record?
This is expected behaviour. Emails create a Connection based on the entity specified in the Regarding field (e.g. Vacancy, Candidate, or Shortlist).
🔐 Data Protection & GDPR
Can customers download data for an individual DSAR request?
Yes. An automation called Subject Access Request allows data export directly from Mercury. It can be run by users with the appropriate role and supports document templates.
👤 Managing Contacts & Records
Does merging Candidate and Client Contacts cause issues?
Timelines and related entities should merge correctly. However, users should verify contact flags (Candidate/Client) and ensure email addresses are retained to avoid visibility issues after the merge.
🔄 Workflows & Process Tracking
How can customers track progression without custom development?
Customers commonly use Shortlist sub‑statuses, which are configurable and can be updated from shortlist views to track candidate progression without consultancy work.
🔌 Integrations & Data Syncing
Can candidates exported before an integration update be re‑synced?
Yes. Re‑using the relevant integration (for example, re‑exporting via the recruiter workflow) allows updated data to be pulled in.