Stages / Columns
The ATS kanban is broken down into different columns based upon the stages which have been defined against the job's record type. These stages are defined based on what the active picklist values of the seven20__Stage__c are for the record type. Additionally, a lot of the stage specific configuration is handle by the application stage customisation functionality.
Ensure that a record type mapping has been created for any custom record types, otherwise the stages and columns cannot be determined and the ATS will not load.
By default, new applications will appear in whatever stage has been assigned as the default field value for that record type.
Defining new stage columns
There are predefined values for the seven20__Stage__c field. If these values are not appropriate, custom stages can be defined by creating a new picklists value for the seven20__Stage__c field. The order of the value determines its column order within the kanban, with the first value being the left most column and the last value being the right most column.
When creating new values, don't forget to add these to the relevant record type picklist values.
When a stage is deactivated or reactivated, the value of seven20__Stage__c will remain unchanged for all existing applications. Candidates cannot be added to an ATS if they already have an application against a deactivated stage.