Reporting 2.0 is the new reporting tool for standard and custom reports. The new tool must be self-enabled and is intended to provide you with a simplistic and intuitive way to build and use reports. Enabling does not impact Standard or Custom Reports. This is a powerful new engine that delivers a single application for creating reports.
The following features are available with the February '20 release:
- Aggregate Values and Totals
- Additional Summary Options for Chart Data
- Incumbent Permissions/Constraints Apply to Succession Reports
- Expand/Collapse Filter Section on Report Viewer
- Applicant User Alias - Note: This functionality was previously made available as part of the 6 December 2019 patch release.
For detailed information about creating and viewing reports, see the following existing topics in Online Help:
Note: You will continue to have full access to standard and custom reports following self-enablement of this functionality in your portal.
Reporting 2.0 (Early Adopter) is intended to give you a chance to get familiar with the tool in your Production and/or Pilot environment before it is made generally available (GA) in a future release. Early Adopters can build both ad hoc reports and report templates with their data by adding columns, specifying filter logic, and specifying filter properties.
While all clients are encouraged to be a part of the Reporting 2.0 (Early Adopter), it is important to make sure the features meet your needs. The following are a few components of an Early Adopter:
- Experienced in building Custom Reports
- The Early Adopter will build report templates and share them with other users. These other users do not necessarily need to be experienced in building Custom Reports as they will simply be using templates and downloading reports.
- My portal has User and Learning, Recruiting, Performance, Extended Enterprise, or Succession Data
- I understand that not all existing Custom Reporting features are currently available in the Early Adopter but I am eager to start using the features that are available now
- As Anna Administrator, I build and maintain reports for my organization.
- I am most interested in the filter properties because I can:
- Make it easier for Viewers to know which criteria to set.
- Hide confusing filters.
- Limit how Viewers interact with filters.
- I build reports and bring in my favorite standard and custom fields.
- I share reports with other users and let them know they have a new report.
- I spend the most time making sure the filter logic is correct and easy to use.
- As Vicky Viewer, I run reports for my team.
- I do not have the create permission, thankfully, because I am too busy to learn how to build reports.
- I love running report templates others have built for me. I change a couple filters like date.
- If I need something complex changed in the report, I will talk to Anna Administrator and ask her to change it for me.
The Reporting 2.0 functionality must be self-enabled. For self-enablement information. All clients can opt-in to Early Adopter in Stage, Pilot, and Production portals. See Enable Reporting 2.0.
Each Early Adopter client should have a stakeholder experienced with building custom reports. The stakeholder(s) should build report templates and share them with other users. The other users do not need Custom Reports experience, as they will simply be using templates and downloading reports. Note: Without a stakeholder with fair to moderate Custom Report experience (or comparable experience with a reporting/analytics tool), the user experience may not be as successful.
The Reporting 2.0 functionality is controlled by a series of permissions that allow you to create more specific reports by report field. For this reason, permissions are at more of a granular level with this functionality.
The permissions are broken down by the main product level permission, section level, and then at the field level. For example, if you wanted to report on Instructor Led Training (ILT) in the system, you would need:
- The Reporting - Manage permission to create reports.
- The Reporting - View permission to preview reports and view reports.
You would also need:
- The top-level product specific permission to create reports related to that product.
- e.g. Reporting - Learning - Manage
- The section specific permission to create reports for that feature within the product.
- e.g. Reporting - Learning - ILT - Manage
- The field level permissions to be able to create reports with the specific fields for that feature within the product.
- e.g. Reporting - Learning - ILT - ILT Facility - Manage
If a user does not have each level of permission, then they may not have access to the report builder, or the section may not be visible, or the fields within the section may not be visible. Also, if a user does not have the top-level product permission, then none of the fields for that product will be visible, such as the fields for LMS reports.
The power of this granularity of permissions is that you can give access to as many or as few fields as necessary for your users. For example, you may give users access to the User section but not give them access to the User Identifier section if that contains sensitive data for your portal.
For the full list of existing permissions and their relationships, see the permissions spreadsheet in Online Help.
Constraints exist at the section level for permissions. At this time, the following constraints are available: