General Input Arguments

The following input arguments apply to many action templates. The topics describing the action templates contain input arguments specific to them.

Input Arguments Description


Names of additional filters that are applied, separated by comma.


Name of the referenced Search&List configuration, fallback: field group of the same name.

For client reports you can also define a specific link to be applied with the following syntax:



List of filters that are enabled by default, separated by comma.

Filter1 - Filter<n>

Defines the filters that are available to the user when he taps on the  (Filter) button. The number of available filters depends on the action template.


The name of an additional fixed filter that is applied.


If set to true, the full text search is applied. The asterisk (*) can also be used as a placeholder at the beginning of a search criterion.


If set to true, the (online/offline) button allowing the user to search data online is not displayed. Only the offline search is available.

Default value: false


If set to true, the action defined by the SavedAction argument is ignored and after adding a new child record, its root record is displayed.


Defines the info area for which records are displayed.


The identification number of the linked record, links the record to the given LinkId.


The record linked to the current record.


If you do not want to use the default link to the parent record, you can define a specific link.

With NoLink you can prevent a link being set.


Defines the record that is the parent or root record, usually the current record (e.g. in edit mode, the record to be edited, and in New mode, the linked parent record, i.e. the record from which the New mode was started).

If left empty, the parent record's RecordId is applied, e. g. for samples the activity's RecordId.


Records, e. g. calendar items, can be filtered by reps. Enter the filter name to be applied, e.g. MA.ParamRep.

Some filters (as MA.ParamRep) require parameters.

RequestOption or


Defines how data is read. Depending on the action called, not all options are applicable. The default value also depends on the action.

The following options are available:

  • Fastest: Data is read offline, if available. If not found offline, the data is searched online if a server connection is available.
  • Best: Data is searched for online. If no network connection is available, data is read offline
  • Online: Data is always read online (data cannot be displayed if no network connection was established)
  • Offline: Data is always read offline only.


Name of a filter that specifies the conditions the current record has to meet so that an operation is carried out. For example, if a report (i.e. an order) was signed by a customer, it cannot be edited anymore.


Available option:

NoEmptySearch: If the search field is empty, the search is not started.


If set to true, a button to send an e-mail is displayed after the action was executed, e.g. after a client report was generated.

Default value: false


Name of a context menu action that generates the e-mail's body based on the current record's data. Transfers data like the e-mail address and the subjects to the e-mail client.

If more than one action (separated by comma) are given, a dialog box is displayed and the user can select the desired action.


If set to true, a PDF report based on the record's and its children's data (e. g. an offer and its offer items) is generated and attached to the e-mail.

Default value: false


If set to ASC (default), data is sorted in ascending order. DESC sorts the data in descending order.


If set to true, the user can swipe to the next or previous record.

If left empty, the View.RecordSwipeEnabledDefault Web Configuration parameter is applied, >> View.RecordSwipeEnabledDefault in the Aurea CRM web Administration guide.


Name of a template filter that sets, for example, initial values when a child record is created.