ATS Level Actions
ATS level actions are located at the top right of the ATS header. These actions are performed against any selected applications, or on the job level as a whole.
All applications within a column can be quick selected by using the Select All ( ) button in the header of the column.
Standard actions
There are a number of standard actions available, these are as follows:
Reject Candidate(s)
Rejects the selected cards and performs the rejected stage transition.
Add Candidate
Search for a new candidate to create an application for against this job. Additional fields can be included via field sets on a record type by record type basis by utilising the record type customisation metadata as follows:
| Field Label | Field Value |
|---|---|
| SObject | seven20__Application__c |
| Customisation Name | Add Candidate To Job |
| Customisation Value | seven20__Application__c field set API name |
It is possible to configure which Contact field is displayed underneath the candidate name when searching for candidates to add. Use the Candidate_Search_Context_Field configuration metadata setting and input the API name of the desired Contact field into the Value field of the metadata record.
Add to Other Job
Creates applications for the currently selected candidates against another job. Supports lookup customisation.
Add to Hotlist
Adds the currently selected candidates to a hotlist. The hotlist lookup in this screen can also be used to create a new hotlist.
Submit Multiple Candidates
Submit multiple candidates with the option of sending an email to a hiring manager, or other email addresses. Email templates related to the seven20__Job__c object may be used. Related templates can be grouped using the email template folders configuration, by placing them in the folder assigned to Mass Submit to Job. The action will redirect to a separate screen. By default, a maximum of 6 candidates can be sent at once, however a Seven20 Configuration setting with developer name ATS_Multiple_Submit_Candidate_Count can be used to increase or decrease this amount.
Do not increase the Submit Multiple Candidates limit without strongly considering the effects. This limit exists due to email size limits, which can not be predicted. If the limit is increased, it is possible to send emails that are too large to be delivered to some mailboxes.
Mass Email Candidates
Send an email to the selected candidates. Email templates related to the seven20__Application__c object may be used. Candidates can also be quick selected, by stage, via the first screen of this action. The columns visible in the selection screen can be configured by a field set on the application (seven20__Application__c) object and by using a Seven20 Configuration setting with developer name Mass_Email_Candidate_Fieldset.
Deactivate the configuration setting metadata ATS_Show_Mass_Candidate_Email_Button to hide this action.
Close Job
Sets the Job_Closed__c field to true on the Job (seven20__Job__c) record. If the Mass Reject Applications on Job Close Trigger Action is active, all applications that are not already rejected or placed, will be rejected. It is possible to adjust which fields appear on the Close Job modal by configuring field sets for each job record type via record type customisation metadata records with the values:
| Field Label | Field Value |
|---|---|
| SObject | seven20__Job__c |
| Customisation Name | Job - Close Job Fields |
| Customisation Value | seven20__Job__c field set API name |
None of the above standard ATS actions are currently configurable actions.
Custom actions
Custom flow modal actions can be created. These will be displayed to the left of the standard actions. These should use the following settings:
| Detail | Value |
|---|---|
| Process | ATS - Mass |
| Templated Flow | seven20_ATS_Mass_Template |
The following input variables are required:
| Variable Name | Type | Description |
|---|---|---|
| jobId | Id | Id of the ATS's job record |
| applicationIds | Text collection | Collection variable containing all the selected application Ids |
Don't forget to follow the standard flow modal action configuration steps