Compliance
Within Seven20, there are several objects which are used for tracking compliance details required for a job, and the compliance details which a candidate has provided. These objects are:
- Compliance (seven20__Compliance__c) - An instance of compliance, e.g. a driving license, owned by a contact or an account
- Compliance Relationship (seven20__Compliance_Relationship__c) - A join object between a compliance and an application or placement
These compliance records are created via the Compliance Manager component.
Compliance records against the Application are automatically copied to the Placement when the Application is converted to a Placement. This is done by populating the seven20__Placement__c field on the seven20__Compliance_Relationship__c record.
Directly managing compliance for contacts is not supported. Compliance records should be managed via the Compliance Manager on the relevant application or placement.
Required compliance
Additionally, Seven20 also has objects for defining compliance requirements for a job:
- Required Compliance (seven20__Required_Compliance__c) - A compliance which is required for a job
- Required Compliance Template (seven20__Required_Compliance_Template__c) - A template of required compliance records, used to quickly set up required compliance for a job
Required compliance is managed through a quick action on the Job (seven20__Job__c) object, called Configure Required Compliance. Using this quick action will open a modal where the user can select a template of required compliance records to add to the job. The user can also add, edit and remove required compliance records directly from the modal.
There are two picklists which allow the selection of required compliance. This is done by firstly selecting the Type with the left hand picklist, and then selecting the Sub-Type with the right. Selecting a Sub-Type will add the required compliance to the table below.
Additionally, in the modal footer, there is a picklist which will allow the user to select a template of required compliance records to add to the job. This will add the required compliance records to the table above. Any required compliance record added via a template cannot be removed at this stage, but can be removed when reusing the quick action.
The records can be saved by clicking the Save button. It can also be saved as a Template by clicking the Save as Template button. This will open a modal where the user can enter a name for the template. Saving it as a template does not prevent the user from also saving it against the record.
Ensure the type and sub-type fields have matching values between the compliance and required compliance records.
Duplicate required compliances can be added, however they may not behave as expected.