Skip to main content

Exceptions by Policy & Category widget in the Landing Experience

This heat map Chart widget counts approved exceptions that are at the intersection of the top ten policies and ten categories in use; however, the resulting chart displayed is governed by the amount o

Updated over 2 weeks ago

This heat map Chart widget counts approved exceptions that are at the intersection of the top ten policies and ten categories in use; however, the resulting chart displayed is governed by the amount of space available to the widget. Darker cells indicate a higher number of exceptions for the specific policy. Its purpose is to allow users to understand which policies may require modifications to address exceptions being routinely requested.

Screenshot of Exceptions by Policy and Category

Functionality

  • Selecting a cell will show the list of all the records associated to that Policy & Category.

  • From the selected cell, a list will be displayed in table format. An option to view the assignment record when

    quick link icon

    is clicked.

    Screenshot of Exceptions by Policy and Category details

Records from Categories from Assignment Exceptions and Policy from Assignments where:

  • Assignment is active and authorization is not cancelled AND

  • Exception is Approved AND

  • Categories is one of the top 10 categories in use AND

  • Assignment Policy is one of the top 10 active policies in use

Data is displayed in a heat map chart; count of exceptions for each policy/category intersection. If zero policies or zero categories are found, "No exceptions found" is displayed.

Things to note

  • By default, the chart is 5x5 cells, with the highest numbered on the top left. But as user expands or reduces the widget size, new cells are added/removed from the bottom and right side of the widget, to display up to 10 rows/columns.

  • Displays the Policy’s External Name (and not just the Name) in the chart.

  • Core flex exceptions are shown after the authorization has been promoted. They are not denoted differently from any other exception generated on the assignment.

Did this answer your question?