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:06] – [Definition] 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 20: | Line 20: | ||
In **Linked Domains**, add any already defined domains which will be checked whenever this one is checked. IQX will check the full hierarchy of linked domains. For a Linked Domain to be conditional rather than mandatory, you must specify both a question and a choice to trigger it. If a domain appears more than once in a hierarchy tree it will only be checked once, so you don't need to worry about ' | In **Linked Domains**, add any already defined domains which will be checked whenever this one is checked. IQX will check the full hierarchy of linked domains. For a Linked Domain to be conditional rather than mandatory, you must specify both a question and a choice to trigger it. If a domain appears more than once in a hierarchy tree it will only be checked once, so you don't need to worry about ' | ||
+ | |||
+ | ===== Default Domains ===== | ||
+ | |||
+ | 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 ' | ||
+ | |||
===== Viewing Compliance Status of Candidates ===== | ===== Viewing Compliance Status of Candidates ===== | ||
- | In a candidate | + | 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 |
- | 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 |
+ | |||
+ | 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. | ||
- | 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. | ||
===== 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 ===== |