Differences

This shows you the differences between two versions of the page.

--- comply_01 [2018/08/09 16:20] – [Definition] Defaults Michael Scott
+++ comply_01 [2024/11/25 11:16] (current) – Shelley Hunter
@@ Line 1: / Line 1: @@
-====== Compliance Domains ======
+====== Compliance Domains - Advanced ======
 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 23: / Line 23: @@
 ===== Default Domains =====
-You can optionally set up //Default// domains for each department. They must have 'Default' at the begin of the name. There should **NOT** be more than one default domain per department. Default domains will reduce or remove the need to set explicit domains for vacancies and candidates. A typical departmental default domain might link to a global domain to handle global questions required by everyone, and conditionally to various role based domains to police the requirements of each job role.
+You should set up //Default// domains for each department you want to have compliance scoring for, even if you only used a linked Domain of universal questions. The name must start with the word 'Default'. There should **NOT** be more than one default domain per department. Default domains will reduce or remove the need to set explicit domains for vacancies and candidates. A typical departmental default domain might link to a common global domain to handle global questions required by everyone, and conditionally to various role based domains to police the requirements of each job role.
 ===== Viewing Compliance Status of Candidates =====
-In a candidate record go the the **Compliance Domains** view and tick one or more domains. You will only be able to tick global ones and those departmental ones for which the candidate is registered.
+A candidate's compliance status is based on the Default Compliance Domains for the department(s) for which the candidate is registered, **UNLESS** domains have been selected explicitly for the candidate on the **Compliance Domains** view. You will only be able to tick global ones and those for departments for which the candidate is registered.
-On the **Compliance** view, you will see the colour-coded status of all the relevant questions.
+On the **Compliance** view, you will see the colour-coded status and scores of all the relevant questions.
-On the **Temp Desk Compliance** view you will see the compliance status of all Current candidates in the Pool for whom compliance domains have been selected, with percentage scores.
+If you enable the General Setting **//Show Person Compliance Score Button//**, a button will appear on the top panel showing the calculated percentage score. Pressing it will navigate to the **Compliance** view.
+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.  To set this up you should set a client code against the domain and add this to the Compliance Domain Code field on the Temp Details view of the Client record.  If the code in the compliance domain is filled, the domain will only be used by companies which match that code.  This applies to both default departmental domains and linked domains.
+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 =====
-For this to work you need to specify a Compliance Domain for the **Vacancy** (see the Miscellaneous view). You can also specify Compliance Domains for **Temp Shift Templates**.
+Validation functions use the Default Compliance Domain for the vacancy's department, or the domain explicitly set in the Vacancy Miscellaneous view. You can also specify explicit Compliance Domains for individual Temp Shift Templates.
-In the Placement Pre-Validation function put:
+In the **Placement Pre-Validation** function put:
 <code>return ComplianceValidforPlacement( persid, vacid );</code>
-This will check the Compliance Domain for the Vacancy. It will use the Vacancy start date to check any expiring date questions.
+This will check the Compliance Domain for the Vacancy (explicit or default). <color #ed1c24>Note: It will use the Vacancy start date or today's date, whichever is later, to check any expiring date questions.</color>
-In the Tempshift Pre-Validation function put:
+In the **Tempshift Pre-Validation** function put:
 <code>return ComplianceValidforTempShift( persid, planid );</code>
-This will use the Compliance Domain for the Temp Shift Template, if any, otherwise that for the Vacancy. The Shift Date will be used for expiry checks.
+This will use the explicit Compliance Domain for the Temp Shift Template, if any, otherwise that for the Vacancy (explicit or default). The Shift Date will be used for expiry checks.
+You may, of course, have additional non-questionnaire based checks to make in the function, which should be done first.
-You may, of course, have additional non-questionnaire based checks to make, which should be done first.
+In the **Person State Change Validation** function you might put:
+<code>
+declare rv long varchar;
+if newstatus='C' then  // Trivial example of changing to Current only. Real life conditions will be more complex.
+  set rv = ComplianceValidPerson(persid,0); // 0 means exclude warnings i.e. failures only
+  if rv is not null then
+    update person set status = oldstatus where personid = persid; // Revert to previous state
+    return rv
+  end if;
+  set rv = ComplianceValidPerson(persid,1); // 1 means include warnings. Report them but don't revert state
+end if;
+return(rv)
+</code>
 ===== Using Compliance Domains in Shift Matching =====