System views can only be used by Corporate Report Writers, and don’t contain any custom global questions.
System Views
These views contain extra system details for that specialised report with very specific requirements. They can be used by themselves or joined to your custom view via a subquery in your report.
System views contain system fields only, in a standardised format.
Any customisation of system fields or addition of custom fields is restricted to your custom views.
By keeping these views as system fields only, we are able to make ongoing updates and additions that are available immediately for your use, rather than waiting for individual updates to your specific custom views. If we implement new system fields, or find a new way to calculate something, you get them straight away.
Of particular importance are the SYS 1.x series - they contain even more fields and calculations that might be relevant to your report requirements. If your are unable to get these from your custom view, explore the relevant system view.
A full data dictionary will be available on the Welcome dashboard > System Views subtab.
System views are:
prefixed with SYS
numbered in line with custom views
SYS 1.x series for Jobs, Apps and Assessment
SYS 2.x series for Candidates
SYS 3.x series for Users
SYS 4.x series for special modules and other system data
Working with System Views
You can add fields from system views to a report built on your custom view. You will usually do this via an append subquery.
If joining custom to system views (or vice versa), you need to use:
join fields to match data between views
filters (like a date range) to focus the scope of data being matched data in the sub-query. This is a new, best-practice approach.
Join fields
You’ll need to join your custom view to the system view via a field contained in both. Custom view 1.0 contains a range of unique identifiers for this purpose. Choose one that matches the detail in your report and the data you need from the system view e.g. ApplicationID for additional application data. Hover over each field when building your report or refer to the data dictionary for full definitions.
System view filters
It is also best practice to filter the data matched in your system view in addition to the join to your custom view data. Doing this can significantly help your report’s performance. You can:
match filter fields from your custom view (where possible) e.g. Job Open Date
add filter fields from the system view to help narrow the data it is matching from
You can link a subquery filter to another filter (e.g. in the master) in the advanced filter settings.
System View 1.x Uses
SYS 1.1 Jobs and Apps
Based on to view 01 in Analytics Classic
Job details, audiences, categories and job owners
Candidates, applications and application sourcing
Application and global flags, application notes and vendors
NEW: Job Vendor details - vendors invited to submit an application (as opposed to the vendors that submitted an application in the Application Vendors folder)
SYS 1.2 Job Process
Based on view 02 in Analytics Classic
Job and process details
Requisition, Job Creation and Assessment Process dates and days taken
Process step history, timestamps and duration
Process step activity - users that accessed a step task
Process step permissions - permissions assigned to a step
NEW: Process step status history - the step status history within a step
SYS 1.3 Assessment
Based on view 04 in Analytics Classic
Application and assessment details
Assessment history, timestamps and duration
Assessment step activity - users that accessed a step task
NEW: Assessment step status history - an application’s step status history within an assessment step
NEW: Online Assessment Test Status - each candidate’s online assessment testing status, per online assessment step per job
SYS 1.4 Job Status History
Based on view 09 in Analytics Classic
Job status history and sequence
Days at each job status
Total days at a given job status or across job statuses, including current
Total days at a given job status or across job statuses, excluding current
Job status event triggers and users
SYS 1.5 App Status History
Based on view 05 in Analytics Classic
Application status history and sequence
Days at each application status
Total days at a given application status or across application statuses, including current
Total days at a given application status or across application statuses, excluding current
Application status updated by details
SYS 1.6 Candidate Status Logs
New fields and new view
Candidate Status Log and sequence
Job, application and candidate identifiers
Log number (for ordering)
Details as per candidate status log in Recruit: Created, Name, Change Type Description, Change, Origin
Additional status log components to target specific changes