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 3 Current »

In this section


The following table gives detailed descriptions of the views and the recommended use for each view.

View                                                                                

Recommended Use

1.    eRecruit Job, Requisition and Application Data

This view is your primary source for building information about Jobs and Requisitions in an Application context. Data about the source and history of an Application in the context of a candidate and/or job. Recommended for reporting on applications/applicants in the context of candidate or job history. It also includes sourcing calculations.


We recommend this view as your Default View. It contains a number of precalculated fields.

2.    eRecruit Process Step Data

This view will typically be used to create time-to-fill and/or bottleneck reports. It includes Job Data, Task Data, Global Questions within the Job Context and Process Step Data.


It has a number of pre-calculated fields to assist you in measuring your process effectiveness. Appendix 2 lists these in greater detail.

3.    eRecruit Activity Data

Data about interviews and the applications and/or job they are related to. The only calculated field is the interview duration. Also available here are the Global Questions from all contexts.


4.    eRecruit Application Assessment History Data

This view is somewhat similar to the Process Step view but at a more granular level. It holds one row per APM step execution (= 1 row per step per Applicant) along with relevant Job, App, Global Assessment Form and user Global Questions.


The only pre-calculated fields are the step execution duration in seconds and days.

5.    eRecruit Application Status History Data

This view contains one row for each time the status of an Application changed. It will be useful for reporting on an end-to-end Application process.

6.    eRecruit Back-end User Activity Data

This is a simple view listing all back-end Users (recruiters, vendors) as well as the Global Questions on the User context, and all User activity. You would typically use it to reporting on Users’ Account Expiry Date, or report on the org chart by a Global Question (number of recruiters by gender by year for example.) The activity part of the view allows you to report on which job or candidate a given User worked on.

Be very careful when touching User activity fields (everything in the user activity folder) as it can potentially return a lot of data (every task ever undertaken, and their target). Make sure you use filters in your reports and make them mandatory.


7.    eRecruit Email Data

This view is very similar to the SMS view and shows all emails sent to applicants.


Amount of data
Because of the potential size of the email body and the important number of emails in the system, the table storing emails can get pretty big. For some of our bigger clients, it is several gigabytes in size. Make sure you always use date filters or you will get all that data to be pumped through the network causing delays.

8.    eRecruit Job Permission Data

This view offers a summary of all job permissions. It should be used for reviewing Audiences, Users and Jobs and their respective permissions.


9.    eRecruit Job Status Data

This view provides a list of Job Status changes. In each row, it shows the old and new statuses, status change date, and general info about thus User that instigated the change and the job itself, along with Global Questions.


10.  eRecruit Job-Ad Data

This view provides access to Job-Board data, along with the job it targets and the User who lodged the Job Ad.


11.  eRecruit Job-Alert Data

Including Job Alerts, Audience and Candidate information. It will allow you to report on number of Job Alerts set up within a period.


12.  eRecruit Module and Function Permission Data

This can be used to see what System Modules and/or Functions User/User Groups have access to.


13.  eRecruit Process Template Copy Data

This view shows how many times a process template has been copied and can be used to outline orphan templates that clutter the system. Although a job itself is not a process per se, they are included in this view.

14.  eRecruit SMS Data

This shows all text messages sent to applicants and is generally used by NGA.NET Support.


15.  eRecruit User Role Data

This very simple view shows which Users were assigned a role (chair, delegate etc) on a given job.

16.  eRecruit User Role Permission Data

Similar to the User role view, this shows what Users are allowed to be assigned a given role.


17.  eRecruit Talent Search Data

Create a report based on the number and type of searches Users have conducted and the number of records returned.


18.  eRecruit Config Change Data

This view documents changes in configuration and the users responsible for them. (Not currently functional)

19.  eRecruit Merge Document Data

This shows which Global Questions are used on merge documents. Useful for reporting on Merge Document use and Global Question usage.


20.  eRecruit Refresh Data

This view shows how long each component of the refresh process takes to run. It comes with a bunch of standard reports showing the cost of refresh over time.


21.  eRecruit Form Configuration Data

This allows you to see which questions are configured against a given form. It could also be used to report on form templates which use regular (non-global questions). This view comes with a standard report located in the system summaries folder.


Top

  • No labels