---
title: "Validation of Candidate Eligibility in JSM Tabs"
slug: "validation-of-candidate-eligibility-in-jsm-tabs"
updated: 2025-12-31T12:13:31Z
published: 2025-12-31T12:13:31Z
canonical: "zenoplesupport.aqore.com/validation-of-candidate-eligibility-in-jsm-tabs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validation of Candidate Eligibility in JSM Tabs

## Validation of Candidate Eligibility in JSM Tabs

This feature introduces enhanced validation checks in the Job & Assignment Management (JSM) module to ensure that only eligible candidates are displayed in specific JSM tabs. The system will now verify multiple conditions, URLOverride, DNA Status, Allow Crossover, Entity Share, and Customer Exclude, before showing data in the JSM tabs.

### Functionality

- **Validation Checks Applied to All Four JSM Tabs**(Worked Before, Job Candidate, Shortlist, Available):
  - **URLOverride**: Excludes candidates if override conditions prevent eligibility.
  - **DNA Status**: DNA-status employees are filtered out and do not appear.
  - **Terminated Status**: Terminated employees are excluded.
  - **Allow Crossover**: Verifies crossover permissions; ineligible candidates are excluded.
  - **Entity Share**: Applies entity sharing rules to ensure proper visibility.
  - **Customer Exclude**: Excludes customers per existing logic (already functional in Job Candidate, Shortlist, Available; now extended to Worked Before tab).

### Business Logic

- **JSM Tab Filtering Only**: Validation applies **exclusively to JSM tabs** to prevent office staff from seeing ineligible candidates in scheduling workflows. Global search and self-application remain unaffected to preserve candidate self-service.
- **Candidate Behavior**: Even if a DNA-status or ineligible candidate is successfully added as a Job Candidate (e.g., via manual office staff action), they **will not appear**in JSM candidate lists or in any other JSM tabs. However, they remain visible in these areas without impacting business logic:
  - Person Application > Hiring Info > Job Candidate
  - JCM
  - TJM > Candidate
  - DHM > Talent
  - CMS > Job & Assignment > Job Candidate
- **Self-Application Preservation**: Eligibility validations are **not enforced in global search** to avoid preventing DNA-status candidates from applying to jobs independently. This supports candidate self-service workflows.
- **Manual Addition Handling**: Office staff manual additions of ineligible candidates are addressed through **training and documentation** rather than system restrictions, ensuring users understand eligibility criteria.

This targeted approach maintains clean JSM candidate lists for office staff while supporting flexible candidate self-management and application processes.