Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| comply_01 [2020/07/23 14:09] – Viola Scott | comply_01 [2024/11/25 11:16] (current) – Shelley Hunter | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Compliance Domains ====== | + | ====== Compliance Domains |
| Compliance domains provide a structured mechanism for monitoring the compliance status and suitability of candidates based on their Questionnaire responses (both global and departmental). | Compliance domains provide a structured mechanism for monitoring the compliance status and suitability of candidates based on their Questionnaire responses (both global and departmental). | ||
| Line 36: | Line 36: | ||
| On the **Compliance** view of the **Temp Desk** you will see the compliance status of all Current candidates in the Pool for whom compliance data can be determined, with percentage scores. | On the **Compliance** view of the **Temp Desk** you will see the compliance status of all Current candidates in the Pool for whom compliance data can be determined, with percentage scores. | ||
| + | ===== Client Compliance Domain Code ===== | ||
| + | |||
| + | When different clients have different compliance requirements it is possible to link a domain to the client. | ||
| + | |||
| + | You must be using the compliance pre-validation functions for this to come into play, otherwise it cannot know which client you are trying to match. | ||
| ===== Using Compliance Domains in Validation Functions ===== | ===== Using Compliance Domains in Validation Functions ===== | ||