...
These are some more advanced formatting flags:
flagname | behaviour | notes |
|---|---|---|
/f qrcode(<size>) | Outputs the value of the Token as a QR Code. | Size must be an integer value which will be the width and height of the QR Code in Pixels. For example: {{ FIELD_NAME \f qrcode(200) }} |
n.b. Formatting flags will ignore case and special characters at the beginning and at end. So all of the below are identical behaviour:
...
Here are the currently support list of Variables:
variable name | behaviour | notes |
|---|---|---|
$currentdate | ||
$currenttime | ||
$currentuser | This returns a reference to the Contact of the current user (i.e. the one creating the document from the template), you can then use '.' notation to drill into all the usual data of the current user. | |
$currenttenant | This returns a reference to the Contact of the current tenant (i.e. the company or org the AgileCase account belongs to), you can then use '.' notation to drill into all the usual data of the current tenant. This is useful for getting common data for letterheads such as company addresses, phones numbers etc. You can store any global information as custom fields against the Tenant record and then output it using this variable. | |
$formlink(<formid>) | Outputs a URL linking to a published Form. | Learn more about Shared Forms in the AgileCase v2 documentation. |
$importdoc(<formid>) | Outputs the result of one template within another. i.e. for common elements you want to have in a single place but reuse across templates. Most commonly used for headers and footers. | Only available in MS Word Document format templates. Has no effect in other template formats. |
$formlink supports a special flag "/NEW" which forces a new Shared Form instance to be created. When /NEW is omitted the form is reuse an existing Shared Form instance if one exists, or create one if it does not.|
...