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
Last revisionBoth sides next revision
comply_01 [2018/08/09 16:47] – [Default Domains] Michael Scottcomply_01 [2020/07/23 14:09] – Viola Scott
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 44: Line 44:
 <code>return ComplianceValidforPlacement( persid, vacid );</code> <code>return ComplianceValidforPlacement( persid, vacid );</code>
  
-This will check the Compliance Domain for the Vacancy (explicit or default). 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:
Line 52: Line 52:
  
 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.txt
  • Last modified: 2020/12/03 15:10
  • by Shelley Hunter