Looks like you have a use case where the end user requires to not just see the transactional data she/he is responsible for, but analyse it further and act upon it. You have made a good choice by considering the SAP Fiori Elements – Analytical List Page for this app.
Analytical List Page
This suits best for the following:
- Analyse data from different perspectives
- Perform Root Cause Analysis
- Get a unified view of transactional and analytical data
- Allow interplay between chart and table using the hybrid view
Let us dive further to understand the different parts of the Analytical List Page. Complete documentation on the topic can be found here,
The three main parts of an ALP are Title, Filter and Content Area as represented by A, B and C in the following image:
The tile area comprises of the following parts:
- KPI Tags
- Variant Management
- Chose filter modes and customize filter area
- Share – To share the ALP application url via email/save as a tile etc
These are the KPIs(Key Performance Indicators) related to the data shown in this app and allow progressive disclosure and navigation through KPI Cards. An example of such a KPI is Year over Year comparison of an indicator like “Overdue Receivables” for the current quarter in comparison to that of the same quarter in the previous year. The KPI Tag can be clicked to get a quick view of the chart giving further details of the same. Navigation from this view is supported as well.
Note that since this KPI is part of the header area the filters applied do not impact the values shown here.
Both Page and control level variants are supported by Analytical List Page. This helps save the end users preference in the form of a variant to ease access of regularly used filters, settings etc.
Page Level variants
You can use page-level variant management if you wish to capture filter selection, filter mode, view mode, auto-hide icon state (eye-icon), chart and table configuration (measures and dimensions), sort order, and grouping. This is the default variant supported by ALP.
Control level variants
Control-level variant management is used to define separate variants for filters, charts, and table sections. To achieve this you have to set “smartVariantManagement” = “false”, in the app-descriptor (manifest) file of your ALP project.
The filter variant stores filter area selections and the filter mode. When you load the stored variant, both the filter area selection and filter mode appear.
Note that the following are not supported:
- Turn off variant management for only selected controls (filter, chart, or table area)
- Use control-level variant management and page-level variant management together
Filter Modes and customisation
ALP offers both Visual and Compact filters for easier visualisation of data.
In addition to this the fields shown in each can be customised using the Adapt Filter option on the UI.
This shows the filterable values in the Smart Filter bar on which the the data shown in the content area will be filtered. Documentation links can be found here .
The visual filters in addition to providing a way to select a filter value, show additional analytical data. A use case could be to compare presumed data to your planned data. In this case the presumed and data is shown via Visual Filter, giving the end user also an option to drill down further(in the content area) based on the dimensions shown in the visual filter chart. More documentation on how to configure Visual Filters can be found here.
In hybrid mode the selections in the chart influence the data shown in the table, either by means of highlighting of rows that are impacted by the selection or by filtering the rows based on the selection. This is configurable by means of the auto-hide or the eye icon.
Note that a set of KPI tags that are filterable, or react to the filter content are available in the content area. More details on this can be found in the documentation link under the header “Filterable KPI”
Navigations to other applications are supported at row(in case of table) and header levels by means of navigation actions in the content area.
In addition to the features listed above if you wish to also extend it, here is a list of all the app extensions supported as of now.
Hope this blog was helpful, next in series will be a detailed walk through for each of the sections, related annotations and extensions. Look forward to hear your feedback and comments.
Related Blogs in this series: