Lava Filters

The Community page has a list of all the filters that are available. If a filter is available on the Mobile application it will be marked as such.

The Escape Filter

It is recommended to always include the Escape filter when using Lava text strings in a mobile application. This will encode the string, in case there are some crazy characters included in there that could break things.

{{ item.Title | Escape }}

Shell Lava Variables

The following variables and properties are available in all Lava contexts when executing Lava on the mobile application shell.

• PageParameter

• CurrentPerson

• Device

• PageValues

• AppValues

CurrentPerson

The CurrentPerson object that is available on the mobile shell is a stripped down version of what you are used to using on the Server side. It does not support all the same properties, but most of the ones you are most likely to use should be available.

Device

The Device variable gives you access to the type of device in use by the user. At present the following fields are available.

PageValues

Page values are used along with Page Events to allow you to customize your user experience. The PageValues object is just a dictionary of string/object pairs that you can use any way you want. There is no defined structure to them. You can read more about their use in the Page Events section.

AppValues

Similar to PageValues, the AppValues is a simple dictionary that you can store custom data into. However, the major difference is that AppValues will persist between application restarts. One simple usage might be to store a preference in how a page is displayed. You might present the user with a show/hide option that shows or hides certain elements on the page - all processed on the mobile shell. You can use AppValues for this and the value will persist between different visits to the page as well as a full restart of the application.

Server Lava Variables

When you are using Lava to customize the experience from the server side, for example in a Content block set to server-side Lava rendering, the following variables are available to you.

• PageParameter

• CurrentPerson

• ​Device​

In addition, the Content block defines these additional variables when processing a callback event. You can check out the Advanced: Dynamic Content page for more details on their contents.

• Command

• Parameters

Lava Commands

The mobile application provides a few additional Lava commands that you can use in different circumstances.

setpagevalue

This command allows you to set a specific value in the PageValues dictionary.

{% setpagevalue key, value %}

Both key and value can either be specified as literal values or as variable references, so both of the following are functionally the same.

{% assign name = 'MaxLength' %}
{% assign max = 100 %}
{% setpagevalue name, max %}
​
{% setpagevalue 'MaxLength', 100 %}

You can then access your PageValue by simply accessing it like any other Lava object, for example:

{% assign oldMax = UserValues.MaxLength %}

You can even access PageValues by way of bindings in your XAML:

<Label Text="{Binding UserValues.MaxLength}" />

setappvalue

This command allows you to set a specific value in the AppValues dictionary.

{% setappvalue key, value %}

Both key and value can either be specified as literal values or as variable references, so both of the following are functionally the same.

{% assign name = 'MaxLength' %}
{% assign max = 100 %}
{% setappvalue name, max %}
​
{% setappvalue 'MaxLength', 100 %}

You can then access your AppValue by simply accessing it like any other Lava object, for example:

{% assign oldMax = AppValues.MaxLength %}

You can even access AppValues by way of bindings in your XAML:

<Label Text="{Binding AppValues.MaxLength}" />

NOTE

Because these application values must be persisted to the local database, you should attempt to keep them limited to simple primitive types, such as numbers, strings, booleans. Any other more complex object or array types may or may not restore back from the database as you expect.