Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
comply_01 [2018/08/09 16:32] – [Viewing Compliance Status of Candidates] Michael Scott | comply_01 [2020/12/03 15:10] (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 23: | Line 23: | ||
===== Default Domains ===== | ===== Default Domains ===== | ||
- | You can optionally | + | You should |
Line 32: | Line 32: | ||
On the **Compliance** view, you will see the colour-coded status and scores of all the relevant questions. | On the **Compliance** view, you will see the colour-coded status and scores of all the relevant questions. | ||
- | 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. | + | If you enable the General Setting |
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. | ||
+ | |||
===== Using Compliance Domains in Validation Functions ===== | ===== 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 |
- | In the Placement Pre-Validation function put: | + | In the **Placement Pre-Validation** function put: |
< | < | ||
- | 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 |
- | In the Tempshift Pre-Validation function put: | + | In the **Tempshift Pre-Validation** function put: |
< | < | ||
- | 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 |
+ | |||
+ | 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 | + | In the **Person State Change Validation** function you might put: |
+ | < | ||
+ | declare rv long varchar; | ||
+ | if newstatus=' | ||
+ | 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 | ||
+ | return rv | ||
+ | end if; | ||
+ | set rv = ComplianceValidPerson(persid,1); // 1 means include warnings. Report them but don't revert state | ||
+ | end if; | ||
+ | return(rv) | ||
+ | </ | ||
===== Using Compliance Domains in Shift Matching ===== | ===== Using Compliance Domains in Shift Matching ===== |