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/07 16:31] – First draft 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 5: | Line 5: | ||
They can also be easily fitted into the validation mechanism so that relevant errors and warnings appear without the need for fiddly custom programming in the validation functions. | They can also be easily fitted into the validation mechanism so that relevant errors and warnings appear without the need for fiddly custom programming in the validation functions. | ||
- | A validation domain can be either global or linked to a department. There can be multiple domains per department to cope with different skill sets and compliance criteria. A compliance domain can also link to others, | + | A validation domain can be either global or linked to a department. There can be multiple domains per department to cope with different skill sets and compliance criteria. A compliance domain can also link to others, |
===== Definition ===== | ===== Definition ===== | ||
Line 19: | Line 19: | ||
Numeric, scored and graded questions will additionally support a minimum value. This should be left at 1 for all non-numeric questions. | Numeric, scored and graded questions will additionally support a minimum value. This should be left at 1 for all non-numeric questions. | ||
+ | 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 ===== | ||
+ | |||
+ | A candidate' | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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 ===== | ||
+ | |||
+ | Validation functions use the Default Compliance Domain for the vacancy' | ||
+ | |||
+ | In the **Placement Pre-Validation** function put: | ||
+ | < | ||
+ | |||
+ | This will check the Compliance Domain for the Vacancy (explicit or default). <color # | ||
+ | |||
+ | In the **Tempshift Pre-Validation** function put: | ||
+ | < | ||
+ | |||
+ | 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. | ||
+ | |||
+ | In the **Person State Change Validation** function you might put: | ||
+ | < | ||
+ | declare rv long varchar; | ||
+ | if newstatus=' | ||
+ | set rv = ComplianceValidPerson(persid, | ||
+ | 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, | ||
+ | end if; | ||
+ | return(rv) | ||
+ | </ | ||
+ | |||
+ | ===== Using Compliance Domains in Shift Matching ===== | ||
+ | |||
+ | To add the compliance score percentage to the Temp Shift Match Wizard, in the **Vacancy Shift Matcher Numeric Custom Column** function, put: | ||
+ | < | ||
+ | To sort the highest scores at the top, in the **Vacancy Shift Matcher Custom Sort Order** function, put: | ||
+ | < | ||
+ | **Note:** This score will relate to the **Vacancy** Compliance Domain and Start Date, **NOT** those for individual shifts. | ||