comply_01

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
comply_01 [2019/01/22 12:49] – [Using Compliance Domains in Validation Functions] Michael Scottcomply_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). 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 ===== ===== Default Domains =====
  
-You can optionally set up //Default// domains for each department. 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.+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.
  
  
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.  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 ===== ===== Using Compliance Domains in Validation Functions =====
Line 52: Line 57:
  
 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 in the function, 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 ===== ===== Using Compliance Domains in Shift Matching =====
  • comply_01.1548161371.txt.gz
  • Last modified: 2019/01/22 12:49
  • by Michael Scott