Transforming Analytics and Reporting
By Matthew Haavisto-Oracle on May 04, 2016
Content contributed by Balaji Pattabhiraman
A few months ago, I wrote in this blog about a feature in PeopleTools called Simplified Analytics. This is really transformative technology that puts tremendous power in the hands of end users, enabling them to perform ad-hoc analytics right in context of their transactions and business processes. It makes reporting timely, secure, and relevant.
Let's expand on that concept and take advantage of some other PeopleTools featues. In this case, imagine I am a manager or subject area expert. I've created several simplified analytics that I want to make available to my team for use in their daily work. Simplified analytics enables me to create a tile from any analytic I create. Those tiles can then be placed on any Fluid home page or Dashboard, which is another new PeopleTools feature. Lets see an example of this.
As a business administrator I've created several simplifed analytics for the My Team page. These are available in the My Analytics tab in Related Information.
Note that each tab on this page--Summary, Performance, Compensation, and Leave Balances--contains different analytics relevant to each topic. I've created these analytics to provide better decision support for these processes.
This calls for a quick review of an important part of the Simplified Analytics process. When creating or editing the analytic, I have the option of publishing the analytic so it can be used by others. (See this post for more info on creating a Simplified Analytic.)
When I choose to publish, I have the option of publishing to the My Analytics section of the Related Actions frame or publishing to the Tile Repository. Since I'll be creating an analytic dashboard, I'll save to the repository.
Now I can go to the Personalize option from the menu in any home page. From here I can create my new analytic home page. (This could be created as a Dashboard as well.)
In this case, I'll create a new home page called Team Analytics. This will provide a single access point for our group of analytics, making them available in a convenient form to all team members.
Now that I've created the new home page, I can add tiles representing the analytics that were created previously.
I'll add several analytic tiles and make this home page a robust and valuable analytic tool.
Once I save the page it is displayed. Here you see the home page with all the tiles I've added.
Now let's publish the home page and make it available to the team so all can benefit from it. (Note: If I don't publish the home page to other users I can still use it as a personal home page. One might do this for analytics that are used exclusively by me.)
Enter a name and label and any other field data necessary. In this case I'm making it public, but in many cases you will want to make a page like this available only to a particular role or permission list.
Now when someone on our team logs in, (in this case Rosanna) she will have access to the new Team Analytics page.
Note that the data from the analytics correspond to Rosanna's team. If the same analytics were published to a different group, the data would be relevant to that group. The data, context, and security are determined by the PS Query that forms the basis of the analytic.
This illustrates how you can extend the power of Simplified Analytics to make valuable decision support available to teams, not just individuals.