Portal Data List widget JSON parameters

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read
  • JSON parameters define aspects of the Portal Data list widget on the portal page.

    Note:
    This information assumes that you’re familiar with the JSON code format.
    Table 1. JSON parameters
    Parameter Description
    categories Each category displays a set of records from the Customer Case View Case [sn_customerservice_case] table that meets the filter criteria.

    For each category, you can choose from pre_defined_filters and run_time_filters predefined filter tabs, set the columns for the list view, and determine the fields to be shown in the card view.

    ID A unique identifier that enables the categories condition script to determine whether to show or hide categories on the widget.
    label Name of the category that appears on the navigation pane.

    If a label isn’t entered, the category doesn't appear.

    table The table from which the records are shown on the widget when a category is selected.

    By default, this field is set to the Case [sn_customerservice_case] table.

    list_view The name of the view that defines the list of columns or fields to appear on the widget.

    For more information on these views, see Create and delete views.

    If no value is provided, all columns are shown.

    card_view_primary_column A field from the defined table to be displayed in the first column of a card. For example, you can show the case number in the first column.
    card_view_secondary_column A field from the defined table to be displayed in the second column of a card. For example, you can show short description of the case record.

    This parameter is optional.

    card_view_additional_columns":"column1|column2|column3|column4 Field pairs from the defined table to be displayed as additional columns of a card.

    You can add a maximum of four additional columns.

    This parameter is optional.

    query":"active=true" Query to filter the records that display under the category.

    If no value is provided, all records are displayed.

    glyph":"glyph_name" The glyph to appear on the left of the category label in the navigation pane.
    The glyph name provided should be from the font-awesome library, which can be accessed at the following URL:
    https://fontawesome.com/v4/icons/

    The currently supported version of the font-awesome library is v4.7. If you use a glyph name from a different version, the image will not appear correctly.

    Note:
    If both a glyph and an image are defined, the image is displayed.

    This parameter is optional.

    "image_name":"file_img" An image to appear on the left of the category.

    The image name should be selected from the Images [db_image] table.

    Note:
    If both a glyph and an image are defined, the image is displayed.

    This parameter is optional.

    record_view_page The Service Portal that displays the page with details of any record accessed in the widget.

    This parameter is optional.

    By default, this field is set to the Case (csm_ticket) page.

    pre_defined_filters

    "filter_name":"Value",

    Display cases which are in New, Closed, Open, or Awaiting Info state in any selected category. These filters appear as tabs in the widget. Only Open and Closed case are included by default in the JSON code. The available values are:
    • filter_name: Name of the filter tab
    • Value: Name of the case state such as New, Closed, Open, or Awaiting Info.

    This parameter is optional.

    run_time_filters Displays column and its fields from the defined table as runtime filters in a drop-down list. These runtime filters filter the case records displayed in the widget based on different fields from the defined table. For example, you can display Priority as a column and State, Contact, or Updated as fields.

    If the runtime filters values are not provided in the column and selection_type parameters, the filter icon will not appear for the category.

    This parameter is optional.

    selection_type Display the type of selection. The available options are:
    • Single select: Single selection for the filter column
    • Multi select: Multiple selection values for the filter columns
    values

    "value":"4"

    Values from the defined table for the column parameter. The available values are:
    • Label: Name of a value
    • Value: Integer value of a field
    "ranges":

    "label":"Last Month", "query":"<Range condition>",

    Used to filter the records using a query defined in label and query parameters. For example, you can display case records that have been updated in the last month, last 3 months, or last 6 months.
    The range configuration is:
    • Label: Name of the filter option
    • Query: Query that defines a set of values grouped under a label

    This parameter is optional.

    "role_based_views":
    {
    "field_service_agent_view":"snc_field_technician",
    "agent_case_view":["snc_customer_service_agent","snc_manager"]
    }
    Used to display data list according to the role of the logged in user.

    List the roles in an array to map multiple roles to the same view. All roles in that array share the same view.

    For example, if you want both support agents and service managers to see the same case view, assign the same view (such as "agent_case_view") to both roles within an array.

    When a user has multiple roles the system uses the first matching view it finds.

    This parameter is optional.

    "guest_view":"viewname Used to display items for guest users or not logged in users. Map the view you want to display for the guest users.
    To make the items available to guest users, you must set these to public:
    • Portal Data List widget.
    • Page containing widget (For example, Cases and Tasks)
    • Page content instance

    For details, see Configure public access on the Portal Data List widget.

    This parameter is optional.

    "sort_by":"<column name>" Used for first‑load sorting of Data List.

    This parameter is optional.

    "sort_order":"<asc/desc>" Order of sorting the data list. Default is ascending.

    This parameter is optional.