Row Types

Learn about row types in legacy forms.

You can assign the following types to a row in a Legacy Form.

DatePicker Type

Displays the calendar on the start page.

  • Func argument:

    You can set a specific date or use the $curDay variable (default) to define the day displayed.

  • Valuename argument:

    You can define a name that you can use as a parameter in the Func or any other argument within the same Legacy Form. See the example in see RecordList Type.

  • Options argument:

    For example, you can define the date picker's behavior, see Configuring the Date Picker's Behavior on the Start Page.

RecordList Type

Displays records like child records in the Details view.

You can add more than one RecordList row to a Legacy Form. The record lists are searched for content in the order they are added. If no data can be found for the first RecordList, data is searched for the second one, and so on.

  • Func argument:

    You can define the following options:

    • The name of the Search&Listconfiguration from where the field group name is taken.
    • A link record: You can either leave it empty or enter ID .$ curRep if you want to display records linked to the current rep.
    • A filter name
    • Param1 (optional)

    Example:

    The default configuration contains a DatePicker row that has Calendar as Valuename assigned. You can therefore reference the date picker with $Calendar.

    The default configuration contains MA; ;MA.Date ;$Calendar in the record list's Func field resulting in the date picker's date (defined in its Func argument) being handed over as $parParam1 to the given MA.Date filter. The record list is then only displayed for the current day.

    Further available parameters: FI ;$ MARecord or KP;$MARecord.

    You can add a RecordList row and assign FI ;$ MARecord or KP;$MARecord in the Func field. If the user taps on a record in the MA list, the corresponding FI or KP record is displayed in a list.

  • Options argument:

    You can define the following options in JSON syntax:

    • MaxResults: Limits the number of records shown.
    • RequestOption: Defines how the data is searched for, e. g. {"RequestOption": "Best"}
    • NoDetails: If set to true, the user cannot switch to the Details view.
    • DisablePaging: If set to true, paging is not available if records in a list are formatted in row or classic layout, see ListStyle Input Argument.

StaticText Type

You can only add a StaticText row after a RecordList. The text entered in the Valuename column is displayed in the application if no data is found.

Map Type

The Func arguments for the RecordList type also apply to the Map type, see RecordList Type. But the data is displayed in a map.
Note: If the Search&List configuration given in the Func column has also a Default Action assigned, this action is executed when the user makes a long-tab on a pin in the map.

The configured List control must return four fields:

  • GPS y-coordinate
  • GPS x-coordinate
  • Title (shown in the map)
  • Address

You can set the ColSpan field detail to combine the values of more fields, see Combining Field Values. If a row does not have GPS coordinates, its location is determined by the address field.

HTML Type

You can define that, for example, a client's web page is displayed. Web pages can only be displayed in online mode.

  • Enter the URL in the Func column.
    • You can add the current rep's name or ID to the URL with the $curRep or $curRepId variables, for example, http://www.google.at/search?q=$curRep;
  • Adjust the height by entering JSON into the TD-Attributes column.

ActionForm and TriggerExecution Types

The parameters and functions of these two forms are described in the topic, see Executing Server Workflows with Parameters.

InsightBoard Type

Displays an Insight Board.

Example: By default, the SMARTBOOK application menu is displayed on the start page in the out-of-the-box version, see StartPage.LegacyMenuTemplate.

Analysis and Query Types

You can add an analysis (as of CRM.pad 2.1) and a query (as of Version 2.1.1) to a Legacy Form.

Enter the analysis or query name in the Func argument. You can also add a link record (e.g. the name of a RecordList row).