Business Analytics
Please note that some help pages and screen shots for "Business Analytics" are only available in English.
Business Analytics in the Umantis application is supported using Pentaho (a third-party tool). The help content for Pentaho’s main functionalities was created from the original Pentaho Business Analytics do-cumentation. You can open the documentation in your business analytics solution via Help > Documen-tation... The following link will bring you to the publicly accessible documentation site for Pentaho: https://help.pentaho.com/Documentation/6.1/
Umantis Business Analytics
The Umantis Business Analytics solution offers a variety of ways to analyze, visualize and generate data. With just a few clicks, you can use the displayed data to investigate specific details and trends to help you in your decision-making process. You can either generate your own reports or use pre-defined Best Practice Reports. You can find sample reports in the Best Practice Re-ports/Samples. If you would like to integrate Pentaho into your Umantis solution, please get in touch with your Umantis contact.
Working with Pentaho
If Pentaho business analytics is already integrated in your Umantis solution, you will find it on the follo-wing tab:
- In Umantis Applicant management under: Evaluation > Business Analytics (https://recruitingapp-XXX.umantis.com/BusinessIntelligence)
- In umantis Employee management under: <tbd>
Getting Started
After registration, Business Analytics provides three tabs to get you started:
- Welcome
- From this tab, you can launch an introductory video that will give you an initial overview of the core functions in Business Analytics.
- Samples
- In the Samples tab, you will find examples of commonly used reports.
- Tutorials
- This tab contains tutorials to help make working with Pentaho easier.
BA User Console
The BA User Console is the main area for users to create or modify reports.
In this area, the user can navigate through the sub-areas described below and perform various actions.
Please note that you should save new reports only in your own files folder:
Location: Your solution number/home/your folder
If you do not have permission to save a file in a certain folder, you will receive an error message:
The file cannot be saved. Try again or ask your system administrator for assistance.
Menu Function | Description |
---|---|
This function allows the user to create a new report or a new dashboard. | |
This function allows the user to save their report in a selected folder in the BI area. | |
This function allows the user to make a copy of an existing report and save it in a selected folder in the BI area. | |
This function allows the user to open an existing report. |
The “Save” and “Save As” icons will only be displayed when the user has opened an exis-ting report or created a new one.
Sub-areas | Description |
---|---|
Home |
This is the starting page for the Business Analytics User Console, where user can take various actions such as opening an existing report, creating a new one, viewing sample reports or tutorials, etc. |
Browse file |
Here, the user can manage existing reports, e.g. with copy, rename and delete operations, folder ma-nagement, generating a link to the report for embedding in Iframes, etc. |
Opened |
This area shows the reports that the user currently has opened |
Managing BA Repository |
This area is used to rename or hide/unhide dimensions or measures for Cubes in supported languages. |
New Analysis Report |
This function allows the user to create a new report. |
New Dashboard |
A dashboard is collection of multiple reports. This function allows the user to select existing reports and save them under a single dashboard. |
Samples |
In this area, the user can use the Umantis Best Practice reports pre-defined for immediate use in busi-ness. |
Tutorials |
These are the standard Pentaho video tutorials for creating and managing reports. |
Recents |
Reports recently viewed by the user are listed in this area. |
Favorites |
For quick access to saved reports, the user can bookmark or mark reports as favorites. These reports are highlighted by clicking on the star icon |
Report Analyzer
The Report Analyzer is the main area for creating and editing reports.
It consists of three main sections:
Left Section: All dimensions and measures are listed here. Clicking on the icon hides this area.
Middle Section: This is the layout area in which dimensions and measures used in the report are dis-played. The user can decide to place the dimensions in columns or rows as needed. Measures will be displayed in the Measures area. Finally, Report Options can also be used as needed. This area can be hidden by clicking on the icon.
Right Section: This is the report/chart area, where the report is displayed in tabular or chart form. In the Report menu bar, the user can filter by drag and drop by activating the filter area with a click on the icon. Additional functions like Export or Chart settings can be modi-fied by clicking on the
icon.
User Action | Description |
---|---|
Create and save new analytics report |
To create a new analytics report, the user must click on the |
Open existing analytics report |
Users can access existing saved reports in two ways: 1) Click on the |
Choose Table view or Chart view for reports |
The table view
|
Report management |
To manage reports, users can access the Browse Files function from the main menu. Reports can be organized in folders using actions such as move, copy, delete etc. The folder structure is standardized for all BA users:
In both of the above folders, the user can create new sub-folders as needed.
|
Access sample reports |
There are two possible ways to access sample reports: 1) Go to the home screen and select the Samples tab in the middle. |
Embed a BA report in a Umantis page |
A Business Analytics report can easily be embedded/displayed to any user in the organization by em-bedding it in an Iframe window across the Umantis application. To embed/display a report, proceed as follows: 4) Once the popup window opens, copy the URL from the browser’s address bar and store it for use in the Iframe.
|
Export Reports |
All reports can be exported in PDF, CSV & Excel workbook format. Users can export reports from the BA user console or from a report embedded in an Iframe. |
Filter data in reports |
Filters are used to restrict or limit the data that is presented in a report. An example is a filter that limits application figures in a report to the first quarter of the year. Filters can be used both in the BA user console and in reports embedded in Iframes: |
Report options |
Report options can be accessed in the BA user console only. There are two ways to access them: a) Click on the Settings
The following functions can be used in reports: |
Chart options |
This function allows the user to configure chart labels, axis, legend etc. For more details, see BA Chart Options. |
Managing BA Schema Repository |
Here the user has access to two main functions: 1) Modify measure and dimension names (caption) & description (mouseover text) in supported lan-guages. |
BA Chart Options
The Chart Options dialog box is available if you have a visualization applied to your report. Just click on the Chart Options button in the Properties panel to bring up the chart options for that report. You can click Apply to update your report with the changes you have made up to that point, and then continue working with the Chart Options. After you are done setting options for your chart, click OK, and the report will refresh to reflect the options.
General Tab
The General tab is where you can specify background colors, fonts, or set the domain limit for the maximum number of plot values for your report.
General Tab description
Option | Description |
---|---|
Background |
Fill type specifies the background color of the chart and the fill colors that will be used. Choose None, Solid, or Gradient from the dropdown menu. |
Labels |
Use the dropdown menus to choose a font for your data labels, specify the size and type for the font, and change the font color with the color picker. |
Domain Limit |
Max Number of Plot Values: Use this to set the maximum number of plot values used in your report. |
Axis Tab
Use the Axis tab to control how the x-axis and y-axis appear on your report.
Axis Tab description
Option | Description |
---|---|
Primary Axis |
Auto Range check box: Calculates the Start and Stop value automatically. If you want to specify your own values, uncheck the box and fill in the Start and Stop fields. Start: Use to set the starting value for the axis. |
Scale |
Increase the scale for the primary axis, or leave it set to a default value of None. |
Secondary Axis |
Available for Scatter and Column-Line Combo charts only. Secondary Axis has the same options as Primary Axis. |
Legend Tab
The Legend tab includes features that you can use to customize the look of the legend that goes along with your report.
Legend Tab description
Option | Description |
---|---|
Show Legend |
Uncheck this box to remove the legend from your report. |
Position |
Use the dropdown menu to place the legend at the Top, Right, Bottom, or Left of your re-port. |
Background Color |
Use this to change the background color of the legend. Click on the Background Color box to bring up the color picker. |
Font |
Use the dropdown menus to choose a font for your data labels, specify the font size and type, and change the font color of the legend. |
Other Tab
Use the Other tab to tailor the look of the small charts for your report, if you have the Multi-Chart option selected. You can alter the size of negative values, or specify how you want Analyzer to show empty cells in your report.
Other Tab description
Option | Description |
---|---|
Multi-Charts |
Charts Per Row: Choose from the dropdown menu to specify how many multi-charts appear on each row. Axis Auto Range for Charts: Use this to set the axis range for your multi-charts. You can use the sa-me range for all of the small charts, or set them independently. |
Size By Measure |
Treat Negative Values as: Use the dropdown menu to choose either Smallest Value or Absolu-te. |
Empty Cell Treatment (Line and Area Charts Only) |
Controls how empty cells appear in your Line and Area charts. Choose from Show Gap, Connect with Dotted Line, or Treat as Zero. |
BA Visualizations for Analyzer/Chart Types
After you have created an analytics report, you will most likely want to make the report more visually pleasing and meaningful for your audience. Analyzer has several built-in visualizations that make it easy to present your data in a way that people can intuitively understand. We also give you many different ways to customize your visualizations.
Both the Layout and Property panels in the Analyzer workspace change dynamically based on the visualization that is currently selected. The Layout panel shows you what data is needed for the current visualization, and the Property panel lets you add or change options such as data labels, color pat-terns, or bullet styles.
The optional properties for each visualization type are listed in each section. You can use any or all of these properties for each visualization to make your report more intuitive for your audience. The Chart Options dialog gives you more ways to customize reports.
Column and Bar Charts
Column and bar charts are among the most recognizable visualizations for data. Column charts display their data vertically, while bar charts display the same data horizontally.
Column and bar charts are good for just about every kind of data; however, they tend to work best when you do not have a large number of variables to display. Drilling down into your data is easy: just double-click on a column or bar in the report.
Optional properties for Column and Bar charts
Property | Description | Available In |
---|---|---|
Data Labels |
Use this to label the data features of your report to reflect what they represent. You can also choose no Data Labels, or specify where you want them to appear. | all Column and Bar charts |
Column or Line Data Labels |
Use this to put data labels on your columns or lines, or both. | Column/Line Combo charts |
Trend Type |
Shows a trend type of none or linear. If you choose linear, you can name your trend line and set its width. | Column charts |
Line and Area Charts
Line and area chart visualizations show data on a graph by connecting plotted points with a line. Each point represents a single value in your data. You can drill down in both chart types by double-clicking on a data point.
A line chart shows just the line connecting the dots on the graph, and works well if you have a large amount of data to analyze.
An area chart shows an aggregate of your data and helps you spot trends quickly, by showing totals and how they are moving relative to each other.
Both types of chart are good if you want to identify trends that happen over a period of time, such as for financial growth, real estate sales, or test scores.
Optional properties for Line and Area charts
Property | Description | Available In |
---|---|---|
Data Labels |
Data Labels Use this to label the data features of your report to reflect what they represent. You can also choose no Data Labels, or specify where you want them to appear. | Line and area Charts |
Bullet Style |
Choose the shape that you want to use for your bullets. | Line charts |
Line Width |
Specify the width of lines in your report. | Line Charts |
Trend Type |
Shows a trend type of none or linear. If you choose linear, you can name your trend line and set its width. | Line charts |
Pie and Sunburst Charts
Pie charts are representations of your data as a circle cut into slices. Each slice represents a piece of data, and the size of the slice is proportional to the data that it represents. Double-clicking on a slice lets you drill down into your data.
Pie charts are a great way to show numerical or financial data— in other words, the value of one element relative to the whole group.
Sunburst visualizations organize and display your data in a series of colored rings. Starting with the cen-ter ring, each ring going outward represents more detailed information relating to the inner ring to which it is connected. These outer rings are arranged and colored to indicate their hierarchical relationship with the inner ring. Any fields that contain empty slices can be shown as gaps in the sunburst.
You can drill down into your data by double-clicking on a data slice. The sunburst then rearranges itself to show the more detailed information.
Sunburst visualizations are particularly well-suited for numerical analysis of hierarchical data.
Optional properties for Pie and Sunburst charts
Property | Description | Available In |
---|---|---|
Data Labels |
Use this to label the data features of your report to reflect what they represent. You can also choose no Data Labels, or specify where you want them to appear. | Pie and sunburst charts |
Order By |
Lets you specify how to sort your data in the report. | Sunburst charts |
Empty Slices |
Check this box to show Empty Slices as gaps in the report. | Sunburst charts |
Scatter Chart Visualization
Scatter charts are related to line and area charts, but show the intersection of x and y values at each data point. These values appear on the scatter chart as a series of bubbles on a graph, based on the attri-butes you used when you built your report. You can then use a measure to color-code the bubble, or use a measure to specify the size of the bubble. Drill down by double-clicking on any data point on the chart.
Scatter charts work well to show the categorical relationship between two sets of numerical measures, e.g. between a budgeted amount and the actual amount of money spent.
Optional properties for Scatter Chart visualization
Property | Description | Available In |
---|---|---|
Data Labels |
Use this to label the data features of your report to reflect what they represent. You can also choose no Data Labels, or specify where you want them to appear. | Scatter Chart visualization |
Trend Type |
Shows a trend type of none or linear. If you choose linear, you can name your trend line and set its width. | Scatter Chart visualization |
Heat Grid Visualization
Heat Grids let you visualize data to identify patterns of performance. This visualization type will color-code your results so you can view complex business analytics in an easy-to-understand way. Drill down into your data by double-clicking any square on the grid. Heat Grids are especially well-suited for compa-ring categorical data using color.
Optional properties for Heat Grid visualization
Property | Description | Available In |
---|---|---|
Data Labels |
Use this to label the data features of your report to reflect what they represent. You can also choose no Data Labels, or specify where you want them to appear. | Heat Grid visualization |
Pattern |
Choose from Gradient, 3 Step, or 5 Step patterns. | Heat Grid visualization |
Color |
Choose from different combinations of colors for your report. | Heat Grid visualization |
Reverse Colors |
Reverses the order of colors in the report. | Heat Grid visualization |
Bullet Style |
Choose the shape that you want to use for your bullets. | Heat Grid visualization |
BA Report Filters
Filters are used to restrict or limit data in a report, building the report to show only the information that you want to view.
For example, a typical report shows job applications by branch office. A time filter on Quarter restricts the data so that only job applications for the selected quarter are shown.
If you add a location filter for country, the report would display data pertaining to country-specific job applications for that quarter. If you add a filter on another field to exclude a job application, the report would display data pertaining to country-specific job applications in that quarter which are also not a part of the excluded area.
BA Analytics supports two type of filters:
Normal filters |
Filters are used to restrict or limit data in a report, building the report to show only the information that you want to view. |
Date range filters |
Date range filters allow you to show only data that meets the conditions of the filter in a report. For example, you can create filters to display data between 2010 and 2013, or all data after 2010. After you have applied your filter, the Analyzer report shows only data specified by the date ranges that you se-lected. |
Create Normal Filters
Follow these steps to add a filter to your Analyzer report.
1. Login to the User Console, and click Browse Files to browse to the location of your Analyzer re-port.
2. Open the report. Click the blue plus sign next to No Filters on the toolbar near the top of the report. A workspace for filters appears at the top of the report.
3. From the Data Source pane, click and drag a field or column into the filter workspace. The Filter dialog box appears. Notice that the values associated with the field are listed in the dialog box. You can choose one of these values, or you can enable Match a specific string to filter the report on a specific string of data.
4. Select the value or values that you want from the Add Selected list and click the arrow to move it into the right pane. The value appears with a green check mark next to it in the right pane.
5. After you have selected all values that you need from the list, click OK to exit the dialog box. Your Analyzer report displays data for the chosen values only.
6. Save your report.
The Analyzer report is filtered and saved. You can click Undo or Reset to return to the previous version of the report.
Create Date Range Filters
Date range filters enable you to show only data that meets the conditions of the filter in a report. For example, you can create filters to display data between 2010 and 2013, or all data after 2010. After you have applied your filter, the Analyzer report shows only data specified by the date ranges that you se-lected.
1. Log in to the User Console, then open an existing analytics report that contains a time dimension, or choose Create New > New Analysis.
2. For a new report, select the data source that you want to use and click OK.
3. Create the report with a time dimension, such as year or quarter.
4. Click the icon to Add a Filter, then drag the time dimension that you want to filter on to the Filters board. You can also right-click on the dimension and add it as a filter.
5. Choose one of the available radio buttons to create your filter:
- Use Choose a commonly used time period to specify a time period such as Current Quarter, Same Quarter last year, or Calendar Month. Once you have your time period specified, click OK to apply the filter. These filters are dynamic and change with the current date. The other date filters are sta-tic.
- Select from a list lets you choose values from a list. You can use the single right or left arrows to add or remove one value at a time, or use the double right or left arrows to add or remove all values in the list. Click OK to apply the filter to your report.
- By choosing Select a range, then clicking the Select from date picker link, you can use the date picker calendars to select beginning and ending dates for your report data. Click Apply, then OK, to apply the filter to your report.
- Once you select a date, the data is validated to make sure that your date ranges actually contain that date. Analyzer searches for the nearest time period, up to plus or minus 30 time periods, if no date is found on the first attempt. You will not be able to save the date filter if no dates are found.
When you create a date range filter using the Between (and incl.) operator and parameterize it, as described in Add Query Parameters in Analyzer Reports, you specify one parameter name, but two pa-rameters are created. One parameter controls the start of the range, and another controls the end of the range. The start date parameter is <YourParameterName>_START, and the end date parameter is <Your-ParameterName>_END.
The Choose a commonly used time period option and the Between, After and Before filters are available only if time dimension levels are set up with the AnalyzerDateFormat annotation.
BA Schema Editor
BA Schema Editor is used for managing schemas (dimensions & measures) in different cubes.
Using the editor, users can perform two main functions:
1) Modify measure and dimension names (caption) and descriptions (mouseover help text) in supported languages (currently English and German only).
2) Hide or unhide the dimensions and measures of a cube.
User actions
Modifying a caption or description is very simple:
1. Identify/Select the cube, e.g. Application, Jobs, Applicant.
2. Select by clicking on any dimension/measure name from the dropdown menu at the left.
3. Select the language from the dropdown menu.
4. Modify the caption and/or description as desired.
Hiding the dimension/measure:
Select the value on the left side; then, on the right, just uncheck the Visible checkbox as desired.
Note:
a.) Changing the group name change will affect all dimensions linked under the same group.
b.) The user must click the Modify button in order to save their changes; changes are not saved automa-tically.
c.) Changes will be saved only for the selected user language.
BA Cubes
Cubes are divided into three core areas / entities in the Recruitingapp solution, namely Applications, Ap-plicants and Jobs.
In addition there is a LifeCycle Transition cube that hold active recruiting data for complex analysis. Active data means that it holds data for all jobs and applications that experienced a status change within the last 365 days.
Property | Description |
---|---|
Applicants |
This cube shows the dimensions, member properties and measures solely from the perspective of the Applicants in relation to the Application-related fields from Recruitingapp, e.g. Applicant Name, City etc. |
Application |
This cube shows the dimensions, member properties and measures solely from the perspective of the Applications in relation to the Job-related fields from Recruitingapp, e.g. Application Source, Application Status etc. |
Jobs |
This cube shows the dimensions, member properties and measures solely from the perspective of the Job-related fields from Recruitingapp, e.g. Job Title. |
Lifecycle Transition |
This cube shows the additional dimensions for ‘active’ Job & Application Status each aligned with the Status date in combination with above three Cube attributes e.g. Start Job Status, End Job Status, Start Application Status, End Application Status etc. This Cube is aligned with the Status date of Job/Application (Calendar) and not with Creation date (Calendar).
BA user can easily combine start and end status with dates to find out the duration between two statuses as needed. |
For more details on field mappings, see BA Dimensions.
Jobs Cube
AM Job Fields name | Dimension/Member Property | English Dimension (Caption) | German Dimension (Caption) | Explanation |
---|---|---|---|---|
Job: Basic field descriptions |
||||
Job title |
D | Job title | Stellentitel | Job title for this job |
Job ID |
D | Job ID | Stellen-ID | Contains a job ID that uniquely identifies the job (system-generated) |
Job number |
M | Job number | Stellennummer | Contains Job number which can be different from Job ID |
Created by |
M | Creator | Erstellt von | Person who created this job |
Awarded on |
M | Last change date of job status | Letztes Änderungsdatum des Stellenstatus | System-generated Date field, based on user activity for the last assigned status of the job |
Priority Marking |
D | Priority Marking | Prioritätsmarkierung | Flags whether its a priority job or not |
Job status |
D | Job status | Stellenstatus | Shows job status |
Current job status |
D | Current job status | Aktueller Stellenstatus | Shows current job status |
Vacancy: Staffing request-related |
||||
Type of request |
D | Type of request | Art des Besetzungsantrages | Example: replacement, new job |
Questions about the request |
D | Job requisition | Fragen zum Besetzungsantrag | Criteria/Reason for the new staffing request |
Name of hiring manager for this job opening |
M | Requester | Antragsteller | Person who made the request |
Replacement for |
M | Replacement for | Ersatz für | Person to be replaced within the company |
Preferred starting date |
M | Preferred start date | Gewünschter Eintrittstermin | Date when the new person will start in the job |
Approval required by |
M | Approver | Zustimmung erforderlich von | Person who will give approval |
Vacancy justification |
M | Job justification | Begründung des Besetzungsantrags | Reason for this new request/job |
Vacancy: Description fields |
||||
Entry level |
D | Entry level | Einstieg als | |
Department |
D | Department | Unternehmensbereich | |
Business language |
D | Business language | Geschäftssprache | |
Form of employment |
D | Employment Category | Beschäftigungsgrad | |
Employment duration |
D | Employment period | Befristung | |
Salary |
M | Salary | Gehaltsbudget | Prospective salary for this job |
Job user-defined 9 |
M | Job user-defined 9 | Stelle benutzerdefiniert 9 | (Free Text field) |
User-defined list Jobs 1 |
D | Work location | Arbeitsort | This field is used generally to store the work location, but it is a user-defined list |
User-defined list Jobs 2 |
D | User-defined list jobs 2 | Benutzerdefinierte Liste Stellen 2 | |
User-defined list Jobs 3 |
D | User-defined list jobs 3 | Benutzerdefinierte Liste Stellen 3 | |
Job user-defined list 11 |
D | Job user-defined list 11 | Stelle Benutzerdefiniert Liste 11 | |
Job user-defined list 12 |
D | Job user-defined list 12 | Stelle Benutzerdefiniert Liste 12 | |
Job user-defined list 13 |
D | Job user-defined list 13 | Stelle Benutzerdefiniert Liste 13 | |
Job user-defined list 14 |
D | Job user-defined list 14 | Stelle Benutzerdefiniert Liste 14 | |
Job user-defined list 15 |
D | Job user-defined list 15 | Stelle Benutzerdefiniert Liste 15 | |
Job user-defined list 16 |
D | Job user-defined list 16 | Stelle Benutzerdefiniert Liste 16 | |
Job user-defined list 17 |
D | Job user-defined list 17 | Stelle Benutzerdefiniert Liste 17 | |
Job user-defined list 18 |
D | Job user-defined list 18 | Stelle Benutzerdefiniert Liste 18 | |
Further information for job opening |
M | Additional information | Zusätzliche Informationen | Additional information on Job opening (Free text field) |
Applicant Requirements fields: Vacancy |
||||
Field of education |
M | Expected degree | Erforderliche Ausbildung | This is an expected condition for any applicant applying for the job |
Professional experience |
M | Expected experience | Erforderliche Berufserfahrung | This is an expected condition for any applicant applying for the job |
Skills and languages |
M | Expected skills | Erforderliche Fertigkeiten | This is an expected condition for any applicant applying for the job |
Educational qualification |
D | Educational qualification | Ausbildungabschluss | This is an expected condition for any applicant applying for the job |
Stakeholders |
||||
Responsible HR contact |
D | Stakeholder type | Stakeholderart | All job-related stakeholders have been bundled under a single dimension |
Responsible HR contact |
D | Stakeholder name | Name | Name of stakeholder/person for the above type in Job |
HR |
D | Stakeholder role | Stakeholderrolle | Standard AM roles |
Job platform-related fields |
||||
Job platform |
D | Job boards | Stellenbörsen | |
Job platform provider |
D | Job boards | Stellenbörsen | |
Recruiter company |
D | Recruiter agency | Personalagentur | Name of recruiting agency |
Recruiter name |
D | Recruiter | Personalvermittler | Recruiter's name (person) |
Branch office-related fields |
||||
Branch office ID |
M | Branch office ID | Niederlassungs-ID | |
Branch office name |
D | Branch office name | Niederlassungsbezeichnung | |
Branch office city |
D | Branch office city | Ort der Niederlassung | |
Branch office country |
D | Branch office country | Land der Niederlassung |
Application Cube
AM Application Field name | Dimension/Member Property | English Dimension (Caption) | German Dimension (Caption) | Explanation |
---|---|---|---|---|
Application: Basic fields |
||||
Application ID |
D | Application ID | Bewerbungs-ID | Unique Application ID in AM |
Application creation date |
M | Application creation date | Erstellungsdatum der Bewerbung | |
How did you hear about the job? |
D | Job referral | Stellenempfehlung | Source of application |
Application status |
D | Application status | Bewerbungsstatus | |
Application Type |
D | Application type | Bewerbungsart | Email, internet, recruiter application etc. |
Application: Evaluation fields |
||||
Quality |
D | Quality | Qualität | Assessment given by HR |
Evaluator |
D | Evaluator name | Bewerter | Person who specifies Rating/Overall evaluation/Quality |
Evaluator type |
D | Evaluator type | Rolle des Bewerters | Evaluator role i.e. Line Manager, Committee Member etc. |
Proposed next step |
D | Proposed next step | Nächster Schritt | Application next status proposed by evaluator |
Rating |
D | Rating | Gesamtbewertung | Rating provided by LM, Deputy LM, Gremium, 3rd party |
Unsolicited application |
D | Unsolicited application | Initiativbewerbung | Signifies in BA whether application is unsolicited or not (true/false value) |
Name |
D | Name | Name | Name of person who assesses the application |
Role |
D | Role | Rolle | AM role of person who assesses the application |
Applicant Cube
AM Applicant Field name | Dimension/Member Property | English Dimension (Caption) | German Dimension (Caption) | Explanation |
---|---|---|---|---|
Gender |
D | Gender | Geschlecht | |
Applicant ID |
D | Applicant ID | Bewerber ID | Applicant's unique ID number |
Applicant Name |
M | Applicant Name | Bewerber Name | Applicant's unique ID number |
Birth Date |
M | Birth Date | Geburtsdatum | Applicant birth date |
Country |
D | Applicant country | Bewerberland | Country |
ZIP |
D | Applicant zip | Bewerber-PLZ | ZIP/Postal code |
City |
D | Applicant city | Bewerberort | City |
User-defined date master data 1 |
M | User-defined date master data 1 | Benutzerdefiniert Datum-Stammdaten 1 | User-defined date master data 1 |
User-defined date master data 2 |
M | User-defined date master data 2 | Benutzerdefinierte Datum-Stammdaten 2 | User-defined date master data 2 |
User-defined date master data 3 |
M | User-defined date master data 3 | Benutzerdefinierte Datum-Stammdaten 3 | User-defined date master data 3 |
User-defined date master data 4 |
M | User-defined date master data 4 | Benutzerdefinierte Datum-Stammdaten 4 | User-defined date master data 4 |
Civil status |
D | Civil status | Zivilstand | |
Commuter permit |
D | Commuter permit | Grenzgängerbewilligung | |
Resident permit |
D | Resident permit | Aufenthaltsbewilligung | |
Education level |
D | Education level | Ausbildungsabschluss | |
Nationality |
D | Nationality | Nationalität | |
How did you hear about us? |
D | Company referral | Unternehmensempfehlung | How did you hear about us? is the original field name in AM which indicates how the applicant learned about the company. |
Pool |
D | Pool | Pool | Applicant pool |
Applicant type |
D | Applicant type | Bewerberart | Applicant type should indicate whether this is an internal applicant (AM user) or recruiter applicant (himself) or external applicant (person outside of company). |
Optional selection list applicant 1 |
D | Optional selection list applicant 1 | Optionale Auswahlliste Bewerber 1 |
Life-cycle transition
AM Application Field Name | Dimension(D)/ Member Property(M) | Englische Dimension (Caption) | Deutsche Dimension (Caption) | Explanation |
---|---|---|---|---|
Application Status |
In BA we have introduced three different "Application Status" Dimensions below to provide user flexibi-lity to create reports as needed. | |||
Application Status |
D |
Start application status |
Startstatus Bewerbung |
Shows all application status linked with application. When joined with End Application status user can determine the duration between two status. |
Application Status |
D |
End application status |
Endstatus Bewerbung |
Shows all application status linked with application. When joined with "Start application status" user can determine the duration between two status. |
Last Application Status |
D |
Current application status |
Aktueller Bewerbungsstatus |
Shows last status of the application. |
Application Status Start & End date calendars |
BA user has access to two calendars for Start and End Date status for "Application Status" below. With two calendars user can calculate the duration between any two status as needed. For Example. How long it takes for a Job from "New" Status to "Filled" Status. To see calculation use Measure " Time in Between start and end status of jobs". For multiple jobs the duration will be shown as Average. | |||
Application Status(year) |
D |
Application status start date-Year |
Bewerbungsstatus Startdatum-Jahr |
Shows year of the application status. User can find out all application with same status in particular year. |
Application Status(quarter) |
D |
Application status start date-Quarter |
Bewerbungsstatus Startdatum-Quartal |
Shows quarter of the application status. User can find out all application with same status in particular quarter. |
Application Status(Month) |
D |
Application status start date-Month |
Bewerbungsstatus Startdatum-Monat |
Shows month of the application status. User can find out all applications with same status in particular month. |
Application Status(Date) |
D |
Application status start date-Date |
Bewerbungsstatus Startdatum-Datum |
Shows date of the application status. User can find out dates of application status for applications as needed |
Application Status(year) |
D |
Application status end date-Year |
Bewerbungsstatus Enddatum-Jahr |
Shows year of the application status. User can find out all applications with same status in particular year. |
Application Status(quarter) |
D |
Application status end date-Quarter |
Bewerbungsstatus Enddatum-Quartal |
Shows quarter of the application status. User can find out all applications with same status in particular quarter. |
Application Status(Month) |
D |
Application status end date-Month |
Bewerbungsstatus Enddatum-Monat |
Shows month of the application status. User can find out all applications with same status in particular month. |
Application Status(Date) |
D |
Application status end date-Date |
Bewerbungsstatus Enddatum-Datum |
Shows date of the application status. User can find out dates of application status for applications as needed |
Job Status |
In BA we have introduced three different "Job Status" Dimensions below to provide user flexibility to create reports as needed. | |||
Job Status |
D |
Start Job Status |
Startstatus Stelle |
Shows all job status linked with a job. When joined with "End Job status" user can determine the duration between two status. |
Job Status |
D |
End Job Status |
Endstatus Stelle |
Shows all job status linked with a job. When joined with "Start Job Status" user can determine the durati-on between two status. |
Last Job Status |
D |
Current Job Status |
Aktueller Stellenstatus |
Shows last status of the job. |
Job Status Start & End date calendars |
In BA we have introduced two calendars for Start and End Date status for "Job Status" below. With two calendars user can calculate the duration between any two status as needed. For Example. How long it takes for a Job from "New" Status to "Filled" Status. To see calculation use Measure " Time in Between start and end status of jobs". For multiple jobs the duration will be shown as Average. | |||
Job Status(year) |
D |
Job status start-Year |
Stellenstatus Startdatum-Jahr |
Shows year of the job status. User can find out all jobs with same status in particular year. |
Job Status(quarter) |
D |
Job status start-Quarter |
Stellenstatus Startdatum-Quartal |
Shows quarter of the job status. User can find out all jobs with same status in particular quarter. |
Job Status(Month) |
D |
Job status start-Month |
Stellenstatus Startdatum-Monat |
Shows month of the job status. User can find out all jobs with same status in particular month. |
Job Status(Date) |
D |
Job status start-Date |
Stellenstatus Startdatum-Datum |
Shows date of the job status. User can find out dates of job status for jobs as needed |
Job Status(year) |
D |
Job status end-Year |
Stellenstatus Enddatum-Jahr |
Shows year of the job status. User can find out all jobs with same status in particular year. |
Job Status(quarter) |
D |
Job status end-Quarter |
Stellenstatus Enddatum-Quartal |
Shows quarter of the job status. User can find out all jobs with same status in particular quarter. |
Job Status(Month) |
D |
Job status end-Month |
Stellenstatus Enddatum-Monat |
Shows month of the job status. User can find out all jobs with same status in particular month. |
Job Status(Date) |
D |
Job status end-Date |
Stellenstatus Enddatum-Datum |
Shows date of the job status. User can find out dates of job status for jobs as needed |
BA-Specific Dimensions
BA-Specific Dimensions (non-AM fields) | BA-Specific Dimension description |
---|---|
Year |
Based on cube, shows year of Job creation/Application creation |
Quarter |
Based on cube, shows quarter of Job creation/Application creation |
Month |
Based on cube, shows month of Job creation/Application creation |
Week |
Based on cube, shows week of Job creation/Application creation |
Day of year |
Based on cube, shows Day of year of Job creation/Application creation |
Day of week |
Based on cube, shows Day of week of Job creation/Application creation |
Day of month |
Based on cube, shows Day of month of Job creation/Application creation |
Date |
Based on cube, shows date of Job creation/Application creation |
Current job status |
Most recent status of the job. This enables combined analysis on the current/last status of the job. |
Job status range |
Thresholds for status measures of jobs in days |
Applicant status |
Hints whether applicant is current employee of company or new candidate/applicant. |
Social Networking |
Hints if Applicant is registered on Linkedin or Xing networking sites |
Current application status |
Most recent status of the application. This enables combined analysis on the current/last status of the application. |
Application status range |
Thresholds for status measures of application in days |
BA-Special Dimensions
Stakeholder concept |
Idea to introduce the Stakeholder grouping concept in the BI Area, in order to make it easy to prepare reports for everyone affiliated with/responsible for the job in question. |
Stakeholder grouping in jobs |
|
Stakeholder name |
Person name affiliated with the job |
Stakeholder type |
Person Type affiliated with the job in any role, e.g. HR, Deputy HR, Hiring Manager, Deputy Hiring Ma-nager, hiring committee etc. |
Stakeholder branch |
Branch to which the stakeholder is related |
Sample use case |
Filter out the gremium / HR for multiple jobs by name or type with flexibility for reporting/analytics pur-poses. |
Evaluator |
Name of the perosn who provides the evaluation |
Rating |
Assessment value provided by the Evaluator |
Proposed next step |
Applicant Status proposed by Evaluator for the next step |
Evaluator role |
Role of the Evaluator e.g. HR, Deputy HR, Hiring Manager, Deputy Hiring Manager, Third Party |
Business case |
Provides evaluation data for this application for various evaluators. |
BA Measures
Measure | Description |
---|---|
Applicants Cube |
|
Number of applicants |
Total number of Applicants (job candidates), irrespective of application |
Number of jobs |
Total number of jobs with at least 1 application |
Average age of applicant |
Age of applicant (as average) calculated from DOB on date of application |
Applications Cube |
|
Hired count |
Number of applications with "hired" status |
Hiring rate |
Percentage of applications with “hired” status |
Number of applications |
Total number of applications, including job applications and unsolicited applications |
Number of jobs |
Total number of jobs with at least 1 application |
Average age of applicant |
Age of applicant (as average) calculated from DOB on date of application |
Average time to status |
Average number of days before application status changes to another status |
Average time in status |
Average number of days that application stays in the given status |
Jobs Cube |
|
Number of jobs |
Total number of jobs, irrespective of application |
Average time to status |
Average number of days before job status changes to another status |
Average time in status |
Average number of days that job stays in the given status |
Lifecycle Transition(BETA) |
|
Average time in between status - Application |
Average number of days between any two status ( Status dates) for application(s) |
Average time in between status- Job |
Average number of days between any two status ( Status dates) for job(s) |
Average time in between status - Job/Application |
Average number of days between start job status and start application status or vice versa. |
BA Calculated Measures (user-defined measures/KPIs)
In Analyzer, you can work with measures in several ways to accomplish tasks, such as renaming a mea-sure, creating a calculated measure, and editing a calculated measure. When updating the details of a measure or adding a calculated measure, you are making changes to the data model from within Analy-zer. When you save these changes, they are now a part of the data source for other users to access. We call these types of changes to the data source inline modeling, since these changes are reflected im-mediately in the data source you are working with. This approach allows you to make model changes easily in Analyzer to benefit other users immediately.
Adding a Calculated Measure to the Data Source
Calculated measures are user-defined measures based on a user's customizations to base measures in the data model. By applying a formula, in this case an MDX statement, to a selected base measure, the user creates a calculated measure to use in their Analyzer report.
Since Pentaho 6.0, you can save your calculated measure to the data model while creating or editing your report in Analyzer. Previously, if you wanted to add a calculated measure to the model for others to use in their reports, you had to submit a request to IT and wait until it was available. Now you can save the calculated measure to the model from within Analyzer, so you can use that new measure without re-loading your report. In addition, after you save your report, other users can immediately benefit from your calculated measure.
When you create a calculated measure using a measure in the Available Fields list in Analyzer, it is added to the data source when you save your report. To create a calculated measure within Analyzer, create or open an existing report in Analyzer.
1. In the Available Fields list, click a measure to select it and then click the down arrow next to it.
2. From the shortcut menu which appears, select Create Calculated Measure. The New Calculated Measure dialog box appears.
Field | Description |
---|---|
Name |
The name of the measure as it displays in the model. |
Format |
Choose how this measure should be formatted, such as currency, general number, or percentage. Use the drop-down arrow to select a format from a system-defined list, or select the “Text” icon next to the field to enter a custom format. If you do not specify a format, the default value of the first base measure is used as the format. |
Decimal |
Optionally specify the number of decimal places for the results. |
Formula |
In the right panel, enter the formula for your calculated measure. You can type the MDX statement ma-nually, or you can use the list on the left to drag measures into the right panel. You can also use the symbol buttons below to help create your statement, or just use your keyboard to type in the expression. |
Create subtotals using measure |
Select this check box to use this calculated measure when adding up subtotals in your report. |
3. In the Name field, enter a name for your calculated measure.
4. In the Format field, specify how you want the results of your measure to appear in your report. You can optionally specify the number of decimal places for the results. If you do not specify a format, the default value of the first base measure is used as the format.
5. In the right panel, enter the formula for your calculated measure. You can type the MDX statement manually, or you can use the list on the left to drag measures into the right panel. You can also use the symbol buttons below to help create your statement, or just use your keyboard to type in the expres-sion.
6. Select the Calculate subtotals using measure formula check box to use this calculated measure when adding up subtotals in your report.
7. Click OK to save this calculated measure. When you save your report, your calculated measure will also be saved to the data model. Once you save the report, the measure will be available for future re-ports which use this data source. Or you can click Cancel to close the dialog box without saving your changes.
BA Conditional Formatting
Conditional formatting in the Analyzer data grid means that cells’ appearance will be affected by the data they contain. The most common form of conditional formatting is stoplight reporting, where cell back-grounds are colored red, green, or yellow depending on user-defined thresholds. Analyzer offers some simple pre-defined methods of conditionally formatting numeric data. Follow the directions below to implement conditional cell formatting.
1. Right-click a measure in the grid, then select Conditional Formatting from the context menu. A sub-menu with conditional formatting types will appear.
2. Select your preferred number format from the list.
The analyzer report will refresh and apply the formatting choice you specified.
Indicator Type | Description |
---|---|
Color scale |
The background cell color will be shaded according to the value of the cell relative to the highest and lowest recorded values in that measure. There are several color progressions to choose from. |
Data bar |
The cell background is partially filled with a solid color proportional to the scale of the cell's value rela-tive to the highest and lowest recorded values in that measure. |
Trend arrow |
An upward or downward arrow is displayed to the right of the cell value depending on whether it contains a positive or negative value. |
BA Member Properties
The member properties concept is used in BA for reporting purposes, e.g. to display free-text data specific to applications or jobs.
All of the most commonly used free-text fields in the Umantis application have been made available as member properties, and can be used in reports as desired. Examples include Job created by, Reques-ter etc.
Identify and Display Member Properties When a number in parentheses appears next to a dimension in a list of available fields, that dimension is associated with specific member properties. You can use those properties to constrain dimensions.
1. To review available fields, click Add more fields to the report on the report toolbar.
2. Locate a dimension in the Available fields list that includes a number in parentheses, e.g. Job ID (13), Application ID (8).
3. Locate the corresponding dimension in your report. Right-click the row or column header for that di-mension, then click Show Properties. A menu displays the member properties you can choose from.
4. Select or clear the member property you want to display in or remove from the report, then click OK.
5. Your analyzer report is filtered by your choice of member properties.
One limitation of member properties is that they cannot be filtered like dimensions can be when used in reports.
For a complete list of member properties, see the BA Dimension page.
BA Business Rules
The following business rules provide users with a basic overview of access rights and visibility of data in the BA area.
Create and save new analytics report |
1. All users can view the report based on reports embedded in Iframes in the view(s) they have access to (e.g. SelfServiceLine, SelfService Board etc.). 2. At present, only system administrators, adminis-trators and HR can create reports (i.e. only these groups have access to the Business Analytics user console). 3. Only system administrators and administrators can embed a report in an Iframe (i.e. only these groups are authorized to use CWC mode). |
Business Rule - Data Visibility |
Branch office restrictions affect which data the user can see in reports/charts; if the Branch office res-trictions flag is on for a given user, then that user can access only the data from their own branch of-fice(s). To allow a user to see all data, the Branch office restrictions flag should be set to off. |
Business Rule - Reports |
A user can create and save reports in their private user folder (folder with username). To share reports publicly, the reports can be moved/copied to the Public folder. The main Public folder is used to share best practices reports with all users (who have access to the BI console). |
Business Rule - Export Report |
Reports can be exported from the BI Editor/reports embedded in Iframes based on access to the user. |
Business Rule - Customized KPI/measures |
Users with access to the BI console can create their own user-defined measures/KPI (calculated mea-sures) by using the MDX. |
BA Language Support
Languages currently supported in BA user console — main Pentaho shell: German, English, French, Japanese | |
Languages currently supported for AM content / reports / translations of table data: All languages sup-ported in AM as per the language of the logged-in user. | |
Languages currently supported for BA dimensions/measures: English (default), German |
BA Best Practice Reports
The following table presents examples of frequently used reports. These can also be found on the Samples tab in your Business Analytics solution. Note that these example cases are based exclusive-ly on anonymized data.
Report | Settings | Video |
---|---|---|
Applicants and vacancies over time with trend ![]() |
|
(Video - tbd) |
Quality of applications for Top 15 branches ![]() ![]() |
|
|
Applicants by type of application over time ![]() |
|
|
Applications by status and major sources ![]() |
|
|
Application status by time-to-status and thresholds
|
|
|
Number of applications for status new vs. hired by major sources |
|
|
Number of vacancies by division and form of employment over time |
|
|
Time-to-status for vacancies over time
|
|
|
Time-to-Position-filled by divisions of main branch
|
|
|
Time-to-Status vacancy published vs. position filled by job platforms
|
|
|
Time-to-hire by job platform
![]() |
|
FAQs
The following is a list of frequently asked questions / common problems asso-ciated with Business Analytics:
S.No | Topic | Possible Reasoning |
---|---|---|
1. |
Why do I see fewer jobs or applications in Applicant Management than in Business Analytics reports? For example, why do I see 100 applications in the Application overview when there are 125 in the BA report? | In BA, nothing is deleted (no data at all). So, if users delete any jobs or applications in the main applica-tion, then the count can differ. |
2. |
Why do I see more jobs in the Jobs cube than in the Applications cube, e.g. 230 jobs in the Applications cube and 320 jobs in the Jobs cube? | In the Applications cube, only those jobs with a minimum of 1 application is shown, whereas in the Jobs cube, all jobs are shown regardless of the number of applications. |
3. |
Which cube I should use to create the report? | Choose the appropriate cube for the entity, i.e. Jobs, Applications or Applicants. BA Cubes BA Dimensions |
4. |
What is the difference between Reporting and Analyzer reports? | The major difference is that reporting is more concerned with the current content/data for the entity, whe-reas the Analyzer is used to show statistics over a period of time. |
5. |
How can I embed a report in a screen (Iframe)? | See the instructions at the following link: BA User Console |
6. |
How can I use a new field from the umantis application in the report for reporting/analytics? | Please check out the Schema repository and enable the field (dimension): BA Schema Editor |
7. |
How can I rename or hide dimensions in a cube that my company is not using? | See instructions here: BA Schema Editor |
8. |
Individual sorting of the selection lists from AM is not included in Business Analytics. | The sequence of the displayed values in AM may be set for a single supported language. A global se-ries is desirable for numerous analyses to present the sequence of events (e.g.: depiction of the logical time sequence for the relevant status in the recruiting process). This feature is in progress and will be available in a later release. Workaround: In Business Analytics, a click on the column head can ar-range everything in alphabetical order or reverse alphabetical order. |
9. |
Values are displayed for dimensions which have long since been deleted. | The dimensions may display the Status value = “imported” for the job status. From the perspective of Business Analytics, this is correct, as the status did exist at an earlier time. The dimensions may display the Status value = “imported” for the job status. From the perspective of Business Analytics, this is correct, as the status did exist at an earlier time. |
BA Glossary
Item | Description |
---|---|
Pentaho |
Third party BI tool integrated in the Umantis suite. The Pentaho BA Server is a Web-based framework that leverages elements of Pentaho Analysis and Pentaho Reporting to provide easy-to-use tools for creation and sharing of reports and dashboards. |
Business Analytics (BA) User Console |
The BA User Console is part of the Pentaho tool for creating and modifying reports. |
Schema |
A schema is a collection of cubes and virtual cubes. It can also contain shared dimensions (for use by those cubes), named sets, roles, and declarations of user-defined functions. |
Cube |
A cube is a collection of dimensions and measures, all centered on a fact table. In the context of Uman-tis AM, there are cubes defined for areas i.e. Application, Applicant & Vacancy. |
Dimension |
Dimensions are linked one-to-one with the Application Management fields. For example, the Branch Office field is linked with the Job Title dimension in BI. Most fields with selection lists are created as dimensions so that users can filter the data effectively. |
Member Property |
Member properties are subcategories/attributes of dimensions. With member properties, user cannot filter the data. Free-text fields in the Umantis application are mostly created as member properties. |
Measures |
A measure is an aggregated numeric value. It is typically a sum of selected numbers in a column, or a count of the number of items in a list. The datatype of this measure can be String, Numeric, Integer, Boo-lean, Date, Time or Timestamp. The default datatype of a measure is Integer if the measure's aggregator is Count; otherwise it is Numeric. In the Umantis context, Number of Applicants and Number of Jobs are formulated as measures. |
Charts |
Visualization/ Graphic converted from the tabular form of a report. Every report can be converted to a chart of the desired type, e.g. pie chart, histogram etc. |
Reports |
Analyzer Reports is an intuitive analytical visualization tool that filters and drills down into business in-formation contained in Pentaho Analysis data sources. Use Analyzer Reports if you want to compile data quickly in an interactive environment, perform advanced sorting and filtering of your data, and want to see chart visualizations that include conditional stop-lighting. It is important that these reports consist of a combination of dimension(s) plus measure(s); otherwise, the data shown in report will not be correctly formulated. |
Slowly Changing Dimension(SCD) |
• Type I: Changes in the source system result in a corresponding change in the target dimension. For example, if a Job Title is changed from “Scrum Master” to “Scrum Master Developer", then it will be updated in BA as well. (We do not retain the old value in such cases, e.g. “Scrum Master”.) • Type II: Changes in the source system result in inserting timestamped versions of dimension rows multiple times in the target dimension. This allows you to quickly find any version of the dimension rows at any given point. For example, if the Job Status has changed from “Approved” to “Filled”, both the Job Status values are retained/stored in the BA area. Note that in order for a dimension to qualify as Type II, a time-stamp is required every time a value is added or changed. |
Analysis Report |
Analyzer has an easy to use, web-based, drag-and-drop design environment that can be used by anyone who wants to dynamically explore data and drill down to discover previously hidden details. You do not need any special expertise to use Analyzer. You can display Analyzer reports in a dashboard in the User Console. |
Data Source |
Actual source of the data, separated into different cubes with relationships among them. Currently sup-ported data sources (cubes) are Applicants, Application & Jobs. |
Dashboard |
Pentaho Analyzer offers many ways to visually display data. These graphics are called visualizations, and include maps, charts, and grids. After creating the reports, users have the option to create dash-boards that use multiple reports. |
Authorization |
Access privileges defined for the user based on their role and other conditions in the Umantis solution. For BI-related authorization, see link. |
MDX |
Used to create the calculated measures. |