The Landing Experience supports prompt filters on user report used in custom widgets through widget context selectors. This feature is available for all user types and both dashboard levels, system and company.
Context filters can be accessed via the
icon at the top of the LE dashboard. Note, if there are no prompt filters for any user reports linked to an LE dashboard widget, the filter icon will not appear.
The context fields are sorted by Widget Name, Field Name. For each context filter, the details are as follows:
Group Name of the Context Filter or field name used by the Context Filter
Comparison operator and value and
Widgets the Context Filters are used
The value selected as the comparison value on the user report, will be the initial value being filtered on. On the Landing Experience, users will have the ability to change the value of the filter, and the widget will update once the
button is selected. Once changed, you can click
for the values to reset to the initial values.
Context filter values are saved per user per dashboard, which means the context values a user selects will not impact anyone else accessing the same dashboard.
Things to Note
Landing Experience Administrator have the ability to group context filters that have the same matching data type.
If a prompt filter is set to inactive, or the comparison operator is “Is Blank” or “Is Not Blank” the context filter will not appear.
If the company ID is used as a prompt filter, it will not appear as a context filter, however, it will still be leveraged in filtering the dashboard; the comparison value entered will be used as the filter value. It is recommended to use company name as a context filter instead of the company ID. Users will not be able to drill down into widgets if the company ID is a prompt filter.
Context filters do not support Prerequisite reports
Text and SQL Lookup context fields are supported with a typeahead, Drop Down list. For these fields and other lookup fields, the number of maximum rows displayed is controlled by the System Preference: Maximum Rows Displayed (GDMAXROWS). If a value does not appear in the list because of this preference, users can still enter in a value and filter based on that. Check with your Equus Representative should you need to change this preference.
Custom SQL fields can be used as context filters and can be grouped. This do not support the Typeahead drop down list at this time
The Vendor Picker, Resource Picker, and Account Picker components are not supported at this time
The configuration user report for the statistic list widget does not support Context Filter logic as this user report only contributes to the look of the statistic list widget
Money and Numeric fields are now supported by their respective field type. This also follows browser formats.