| Table of Contents | ||||
|---|---|---|---|---|
|
You can:
define the placeholder fields in your Acendre Analytics custom view 1.0 Jobs, Applications and Assessment
add the metrics and calculated fields that you are likely to use in multiple reports
add calculated filters and filter groups for filters you repeatedly configure or use
split the answers from a multi-select question to a seperate value per selected answer (per job or application).
Doing this these will give you a consistent approach to your reporting and ensure a single source of truth for how these metrics and fields are defined.
| Info |
|---|
Complete the Requirements Template available on the Analytics Solutions page. |
, or make it much easier to report on the data you are after.
You’ll need to provide clear definitions for all placeholder and additional fields
, metrics and calculated filters, including:
Time to Fill Start
Female candidates: any candidate that answered custom global question APP: Gender = Female (application context)
and End Dates
Gender and diversity group counts
Candidates by assessment stage counts
Any other requirements
| Info |
|---|
Complete the Requirements Template available on the Analytics Solutions page. |
| Note |
|---|
Did you know: there are a whole range of advanced fields in the system views. If you need to use any of these regularly, you might consider having them added to your custom view 1.0 If, for example, you need to see each time a candidate starts a step after being rolled back, you’ll need the Assessment Step - Execution Started field from the SYS 1.3 view. |
Placeholder Fields
The following placeholders are built into your view 1.0 to capture the fields metrics that you’ll most likely need in your reports. For detailed instructions and tips for exploring your data to define them, see Defining Your Placeholder Fields.
Field Category | Field Type | Field Name | Description | Example Definition |
|---|---|---|---|---|
Jobs and Requisitions | NUMERIC | Placeholder - Time to Fill (Days) | Time to Fill (Days) - Placeholder (Job Open to Job Archived).
| Based on Time to Fill Start and End Date definitions. |
DATE | Placeholder - Time to Fill Start Date | Time to Fill Start Date - Placeholder (Job Open Date)
| When Requisition Process Step Name = “Requisition Approved” is started. | |
DATE | Placeholder - Time to Fill End Date | Time to Fill End Date - Placeholder (Job Archive Date)
| When the first candidate arrives at the ‘Offer’ assessment step. | |
Metrics | NUMERIC | Placeholder - Application Count - Diversity and Other Groups | Requires custom definitions and individual fields required for each diversity or other candidate group. | Female candidates: any candidate that answered custom global question APP: Gender = Female (application context) |
NUMERIC | Placeholder - Application Count - Shortlisted | Requires custom definition. Placeholder definition counts all applications that had an application status at any point of Shortlist or reached a step named Shortlist. | When a candidate reaches the ‘Shortlist’ assessment step. | |
NUMERIC | Placeholder - Application Count - Interview | Requires custom definition. Placeholder definition counts all applications that had an application status at any point of Interview or reached a step named Interview. | When a candidate is given the ‘Interview’ application status. | |
NUMERIC | Placeholder - Application Count - Accepted Offer | Requires custom definition. Placeholder definition counts all applications that had an application status at any point of Accept, Accepted Offer or Offer Accepted. | When a candidate has a value for the ‘Date Accepted Offer’ global question. |
Additional Metrics and Fields
Other potential metrics and calculated fields may include:
Field Category | Field Type | Example Fields - dependent on your reporting needs |
|---|
Example Definition(s) - dependent on your process and configuration | ||
|---|---|---|
Other application Groups | NUMERIC | Internal, External, |
In Merit |
Pool, Verbal Offer, Declined Offer… |
Assessment Step - Name = ‘Merit Pool’ Application Status = ‘Merit Pool’ Custom GQ (app context) Merit Pool Decision = ‘Approved for merit pool’ | |||
Job counts | NUMERIC | Casual Processes, Internal Processes, Secondments… | Custom GQ (Job context) Vacancy Type = 'Casual' |
Dates | DATE | Job Approved, Selection Process Approved… | Process Step Last Edited for Process Step Name = Selection Process Approval and Process Step Status = Complete |
Combining fields | TEXT (DIMENSION) | Location (Old) and Location (New) | CASE WHEN Custom GQ (Job context) Location (New) IS NOT NULL then Location (New) ELSE Location (Old) END |
Addition of time to dates | DATE | Date Merit Pool Expires (1 year after job opens) | Job Open Date + 1 year |
System Fields | Various | Any field found in a SYS 1.x view that you’d like added to your custom view 1.0 | Assessment Step - Execution Started |
Calculated Filters
Calculated filters allow you to quickly include/exclude certain results, like excluding test jobs, isolating or excluding your graduate programs, or eliminating any jobs archived more than a year ago.
Filter Type | Filter Description | Example Filter(s) | |
|---|---|---|---|
 | Set Filter | Set filters automatically limit the results of the report - no further selections are required. Suggested uses might be exclude test jobs or any process that isn’t recruitment, or to only show special processes. You will need to provide the logic that identifies each of these (eg Job Type = graduate, Job Name starts with xxTest). | Omits Test Jobs e.g. Job Reference starts with ZZ_Test |
Option Filter | Option filters allow you to make a choice but with the logic pre-configured. Suggested uses might be to exclude graduate programs OR only show graduate programs; only show internal jobs OR only show external jobs. You will need to provide the logic that differentiates your desired options. | Only show graduate jobs or exclude graduate jobs (Job Reference starts with /does not start with GRD) | |
Filter Group | Filter groups allow you to combine a group of filters that you commonly use together, including their AND/OR relationships and other settings. It allows you to quickly add the whole filter group to your report without any further configuration BUT it also means you cannot modify any of those filter settings, like the name, whether the values are cached, or how the filters are organised. | Job Reference, Job Name, Group, Level and Open Date. | |
Multi Select Extractions / Field Combinations
About Multi Select Extractions | Original Multi Select Format | Extracted/Split Multi Select Format | ||||
|---|---|---|---|---|---|---|
We now have a solution that enables us to separate multiselect answers into different rows. This is made possible by isolating each specific answers from within the combined multi-select block - e.g. so that a candidate’s answer of “alpha,bravo,charlie” as it appears against the multi select question can be separate into three rows of “alpha”, “bravo” and “charlie”. This then allows easier searching and filtering of multi-select responses. | Adelaide,Brisbane,Canberra,Darwin,Hobart,Melbourne,Perth,Sydney | Adelaide | ||||
Brisbane | ||||||
Canberra | ||||||
Darwin | ||||||
Hobart | ||||||
Melbourne | ||||||
Perth | ||||||
Sydney | ||||||
| ||||||
About Field Combinations | Original Fields | Combined Field | ||||
|---|---|---|---|---|---|---|
Different fields for a particular item (ie a job or application) can be combined into a single field to make filtering easier and condense them into a single column. | APP: ATSI = Yes | Diversity (Combined): ATSI Disability Current Employee | ||||
APP: Disability = Yes | ||||||
APP: Current Employee = Yes | ||||||
| ||||||
