Action Templates
Action templates define what is displayed in the application, what actions the user can carry out, etc.
You can assign action templates to e. g. buttons, context menu items etc. You can specify input arguments that define e. g. the info areas called, the filters that are applied and more.
This chapter only describes CRM.pad-specific action templates or CRM.pad-specific input arguments. For more information on action templates, seeAurea CRM web Administrator Guide.
FORM:<Name>
Some action templates exist twice, with and without the FORM prefix,
e.g. RecordListView and Form
:RecordListView
.
Assign the prefixed action template when function parameters are handed over, for example, if you want to call an action template from a Legacy Form (e. g. start page) see Legacy Forms.
The parameters entered in the Func column are handed over in the given order:
Syntax:
(
!Func0
;!Func1;!Func2{…})
Example:
If the function parameters (MA;
;MA.Dashboard
{…}) are given in Form:RecordListView, MA
is handed over as ConfigName and MA.Dashboard
as FilterName.
CONFIGURATTION:<Name>
Action templates with the CONFIGURATION: prefix contain pre-defined
sub-configurations e. g. for Pricing or Questionnaires.
For example; CONFIGURATION
:PRICING contains the basic pricing configuration that can be
referenced from various action calls (and therefore needs not be defined in the action
call separately).
TILE:<Name>
In CRM.pad only the following action templates are supported:
-
TILE:Record, see Tile:Record. -
TILE:Search, see Tile:Search.
All other existing TILE:
<Name> action templates are currently only used in
CRM.mobile.