Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Your custom views, with your custom global questions, simplified.

Custom views can be used by both Corporate Report Writers and Report Writers.

1.0 Jobs, Applications and Assessment

One View, Many Uses

This single, simplified custom view combines all the key fields that used to exist across multiple views.

  • Requisition and Job data, process history and job status history

  • Applications, assessment history, application status history and interview bookings

  • Role and task permissions

  • Pre-calculated and placeholder metrics

  • All of your reportable job, application and global assessment form

  • Includes new and updated fields

It has been designed to cater for the vast majority of your Recruit reporting needs.

Find What You Need

Folders

Fields

Folders in all views are ordered in a top-down approach. In view 1.0, you’ll find:

  • essential job data and job details first

  • application and assessment details

  • your metrics and custom questions.

Field names and descriptions have been reviewed and updated so that you know exactly what they represent.

  • Hover over a field to see its description, or refer to the data dictionary available on the default dashboard.

Key Field Changes

This view combines fields that were found in different views in Analytics Classic, including (but not limited to) process step and assessment step data.

Process Step Data

Assessment History Data

  • Workflow process and process step data for each requisition/job (not application)

  • Was found in view 02 in Analytics Classic

  • Now found in the Job Details folder of view 1.0

These fields include Process or Process Step in their names.

  • Assessment process and process step data for each application (not job)

  • Was found in view 04 in Analytics Classic

  • Now found in the Assessment Details folder of view 1.0

These fields include Assessment or Assessment Step in their names, not Process.

This is a different naming convention to Analytics Classic. If rebuilding old reports, check whether your process step fields came from:

  • view 02, and is therefore Process Step data, which means you use the Process/Process Step fields

  • view 04, and is therefore Assessment History data, which means you use the Assessment/Assessment Step fields.

View Demo

Explore the view and its fields using the VIEW DEMO 1.0 Jobs, Applications and Assessment report. This available in your default Reports folder > Templates.

Folder and Field Details

View 1.0 folders and their new or notable fields.

 Jobs and Requisitions
  • Core requisition/job fields

  • Time to fill placeholders

  • Link to Job Card

 Job Details
  • Additional requisition/job details

  • Current Job or Requisition

  • Job Template, Requisition Process and Assessment Process names

  • Process details (view 02 in Analytics Classic)

  • Process Step Is Current

  • Job status history (view 09 in Analytics Classic)

  • Job roles (view 15 in Analytics Classic)

 Applications
  • Core application fields

  • Application Is Submitted, Application Is Withdrawn

  • Application Last Assessed Date

  • Link to Candidate Card

 Application Details
  • Additional application fields

  • Application Notes - Reinstatement Requested/Withdrawn Application

  • Application Reinstatement Requested

  • Late Application Expires

 Assessment Details
  • Assessment Step Details (view 04 in Analytics Classic)

  • Assessment Step Duration (Days)

  • Reference Request Status

  • Interview Bookings/Scheduler (view 03 in Analytics Classic)

 Metrics
  • Application counts - submitted, incomplete and withdrawn

  • Placeholder counts - diversity/candidate groups, shortlisted, interview, accepted offer

  • Job count

  • Job, application, process, assessment and various user ID fields

 Dates - Other Formats
  • System dates in year, month and date drill-down format

  • Application submitted

  • Job created, open, close, archive

 Custom GQs and Group Questions
  • Job, Application and Global Assessment Form GQs

  • Any custom group questions

A full data dictionary will be available on the Welcome and Instruction dashboards > Views subtab.


Other Custom Views

You’ll also get 2.0 Candidates and Job Alerts and 3.0 Users for data and custom global questions in those specific contexts.


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 will be done in 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.

rstem 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

System views can only be used by Corporate Report Writers.

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.

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.

  • No labels