RecordListView

This action template displays records in List view.

Below is a list of input arguments:

Input Argument

Description

Enabled Filter

Comma-separated list of filters that are enabled by default.

Note: Do not enter filters that contain parameters.

ScanMode

If set to true, the user can scan items with a barcode scanner. Default value: false.

SearchPageMode

Defines the mode that is applied if an alternate Expand configuration (or a configuration that is different from the info area name) exists where the colors for the bar left of a search result item is defined.

Possible values:

  • &1 (default): For example, it is not checked, whether the search result contains items of a virtual info area.
  • &2: Displays the colored bar for the default Expand configuration as well.
  • &4: Displays the colored bar for virtual info areas as well, if the Expand configuration's name is the same as the virtual info area's name.
  • &8 (ignore colors): No colored bars are displayed.

To combine values, add the values (e. g. &3 for &1 plus &2).

SwipeDetailRecords

If set to true, the user can swipe from one record to the next when this action is executed.

Note: You can also define that the swipe function is globally enabled by setting the View.RecordSwipeEnabledDefault Web configuration parameter, see View.RecordSwipeEnabledDefault.

Sections

If this argument is empty or set to false, items in (company and person) lists are not grouped.

If set to any other value, list items are grouped based on the list item's first letter. An index is displayed on the left side of the list. If the user taps on the desired letter, records starting with that letter are displayed.

CalendarView

Obsolete, for compatibility purposes only. Use CalendarView instead.

CalendarPopOverConfiguration

Obsolete, for compatibility purposes only. Use CalendarView instead.

MaxResults

Max. number of records displayed in list.

DetailsActionSwitchFilter

Name of the filter that defines the quick action applied.

MapView

If set to true, geo coordinates of address data is displayed in the map (if the geo coordinate fields were added to the referenced List control).

ListStyle

Defines the style how a list is displayed, see ListStyle Input Argument.

ListStyle Input Argument

Note: The ListStyle Input Argument only applies to CRM.pad version 2.x.

You can define with the ListStyle argument, how a list is displayed. The following options are available:

Input Argument

Description

row

Each record is displayed in a row.

rowOnly

Each record is displayed in a row. Cannot be changed.

card

Two records are displayed in portrait mode or three records as cards in landscape mode in a row.

card23

Two records are displayed in portrait mode or three records as cards in landscape mode in a row. Cannot be changed.

card2Only

Two records are shown as cards in a row. Cannot be changed.

classic

Former CRM.pad 1.x list style. Cannot be changed.

The following only applies if you have the row and card value is assigned:

  • The user can switch from row to card style with a pan gesture.
  • In landscape mode only: If no value is specified, row is default behavior. The default behaviour can be overwritten by the List.ClassicLayout Web Configuration parameter, see List.ClassicLayout.

Showing All Annotations in a Map

By default, CRM.Pad does not load all annotations in a Map view. It only displays those items that are viewed in the result list view pane. For example, if a search result list view for a Company infoarea search has 100 Companies in the search result list and the user scrolled and viewed only 40 companies in the search result list, then only those 40 company locations are annotated and displayed in the Map view.

To annotate and display all the items in the result list view, set the option ShowAllAnnotationInMap to true in the RecordListView action template. See the screenshot below:



Aurea recommends that you do not display all annotations in a map, if you do not have a set up to provide the latitude and longitude geographic coordinates for the searched items. See, Adding a Map for more details.

Without such a setup, CRM.Pad uses the reverse geocoder to deduce the latitude and longitude based on the address. The geocoder API has a limitation of 50 requests per minute. This is usually not sufficient to load all annotations for the search result items, in a map.