Skip to main content

Package Setup

Firstly, it is necessary to install the Join package into the client's org - contact the Seven20 Product team to obtain the link for the latest package version. Seven20's Join package is dependent on the following core product packages:

  • Seven20 - Utilities
  • Seven20 - Core
  • Seven20 - Parse and Match
  • Seven20 - Integration Utilities

Credential Setup​

  • Sign into the client's Join account
  • Navigate to https://join.com/user/api and generate an API token
  • Once generated, copy the token
  • In Seven20, navigate to Setup -> Custom Code -> Custom Metadata Types
  • Click 'Manage Records' against Seven20 Configuration Setting
  • Find the record called Join Key (Join_Key), click Edit, paste the API token from Join into the Value field and click Save

Retrieving Join Options​

There are three custom objects used when posting job adverts to Join for which the relevant data need to be retrieved from Join for each client:

  • Join Category (seven20__Join_Category__c)
  • Join Employment Type (seven20__Join_Employment_Type__c)
  • Join Seniority (seven20__Join_Seniority__c)

This data is then used in the associated lookup fields on individual Job records in order to ensure that the values are valid and the job adverts send successfully. The data is retrieved by executing the below from the developer console - replace countryCode with the 2-letter ISO country code based on the client's language requirements:

JoinRequestOptionsRetriever.retrieveOptions(countryCode);
info

If a language other than English is required, please contact the Seven20 Product team to confirm support.

Retrieving Applications​

Applications for job adverts in Join are retrieved into Seven20 via a scheduled job. The job is configured to run on the hour every hour. To schedule the Job run the below command in execute anonymous:

JoinGetApplicationScheduler.scheduleJob();

Configuration Options​

Various configuration options are available to change the behaviour of the integration; these are controlled by Seven20 Configuration Metadata records:

Configuration NameDetails
Integration Job owner fieldDictates who will be the owner of new candidates and applications. Must be a user lookup field on Job. The default value is OwnerId.
Integration Override File OwnerIf active the owner of any inserted files will be the same as the ‘Integration job owner field’ otherwise it will be the guest site user.
Integration maintain candidate sourceBeing active will maintain a candidate source field in the case of updates. If set to inactive the integration will overwrite the source. Default is active.
Integration Parse CandidatesSetting the record to active and entering a valid Parser Status into the value field will cause created or updated Contact records to be parsed; ensure that the value entered exactly matches the Parser Status picklist value.
Join Applications Straight To ATSIf active, applications received from Join will be created as seven20__Application__c records; if inactive, seven20__Job_Board_Application__c records. Default is inactive.
Job Board Reference FieldDefines what field should be mapped as the reference when posting Jobs, must be populated with the API Name of a field on the Job object. The default value is seven20__Job_Board_Reference__c