Mobile configuration

This content is for Spring ’26. Switch to the latest version for up-to-date documentation.

Aforza utilises custom metadata to configure mobile settings used throughout Field and related apps. Changing these settings affects how the mobile app behaves and should only be done by administrators before go-live. Aforza ships with default mobile configuration that works out of the box.

Create A New Mobile Configuration

From any of the Aforza applications select App Launcher.
In the displayed menu select Aforza Admin.
Select Mobile Config from the side menu
Select Create New
Enter your config details:
- Label
- Assigned Profiles
- Is Active
Enter the different options (described below).
Click Save.

Details

Visit Settings

Account credit lock:

This configuration dictates how the application responds when an account balance surpasses a predefined threshold.

None: The end user can proceed with the visit, and no status will be recorded, requiring no further action.
Soft: The end user will be notified that the visit will be flagged unless a payment is made to bring the account back within the specified threshold.
Hard: The end user won’t be able to execute any visit tasks until a payment is processed to bring the account back within the defined threshold. The control will include a Make Payment call to action (CTA).

Custom balance field:

This picklist enables flexibility on which field value is being referenced for the account balance if not the default aforza__Account_balance__c field.

Use offline account payment adjustments:

If a custom balance field handles account payments, enable this setting to improve the accuracy of temporary offline balance adjustments..

Use offline overpayment adjustments:

If you’re using a custom balance field that handles invoice overpayments, enable this setting to improve the accuracy of temporary offline balance adjustments.

Support

Support Enabled:

Setting this to true will enable the App Info menu item in Field where the user can see debug information for their current install / session and generate a report containing this info that can be sent to Aforza customer support / development team via email or any other communication channel (via the phone’s native sharing menu).

Auto Download Visit Resources:

The account resources can be downloaded directly from the account record page and allow you to display account related files. Auto download resources can be set with the mobile configuration json to ensure resources are downloaded for offline usage.

Additional Nearby Account

Accounts Min Radius KM:

The Syncing Engine will dynamically calculate and sync all nearby stores within a radius of your visits perimeter. This means that if you decide to drop in at a store unannounced, the store’s data will be offline and ready to use. This field sets the minimum radius.

Accounts Max Radius KM:

Order Settings

Number of Orders For History:

This value can be between 0-6 and will determine the number of historical, activated orders that are synced down to the device for each account

Objects To Sync

Object Settings

To add an object to be synced down to the Aforza application, use the following steps:

Navigate to the Objects To Sync option in the drop down menu.
Select the object you wish to sync.
Select Add Object.
Navigate to the added object within the list and expand.
Complete the following data dependent upon requirement:
- Can Create - will allow the user to create a new record for the chosen object in Field. Note: If can create is set to false for Audit, Object or Guide objects, the item will be removed from the task Actions list.

Note: Turning the CanCreate function to false can determine the presences of certain fields throughout Aforza processes and should therefore be applied cautiously. Example: Payment transaction set to off results in the make payment option being removed from the order flow, similarly with deliveries and invoices.

Can Delete - will allow the user to delete a record for the chosen object in Field.
Can Edit - will allow the user to edit a record for the chosen object in Field.
In Side Menu - will add the object to the side menu within Field.
Record Limit - restricts the number of records for the chosen object in Field
Use the following configuration screens to tailor the record experience for the chosen object
- Edit smart action - enables the association of a smart action against the chosen object in Field. A name, target and type should be set.
- Edit layout form - the fields displayed when creating or editing a record for the chosen object.
  - Field can be set to required.
  - Record type application can be set for each field.
- Edit layout list view - the fields displayed when viewing a list of records against the chosen object.
  - Field can be set to required.
  - Record type application can be set for each field.
- Edit record sort - Select a field and sort method for record display ordering
- Edit filter groups - custom filters can be added to control the records being synced for the chosen object.
- Edit tabs - Select the tabs to be displayed for the chosen object. This can include related objects, these will need to be configured using the relevant parent child lookup api data.

Field supports enhanced user-related object filtering to reduce sync data volumes and improve performance. You can fine-tune which records (products, promotions, assortments) download to each device so only relevant data is synced. To use it effectively, override default filters at the object-to-sync level and set OverrideAppDefaultFilters to true.

Example (conceptual JSON fragment):

{
  "OverrideAppDefaultFilters": true,
  "Filters": [
    {
      "Key": "aforza__Owner__c",
      "Operator": "includes",
      "Value": "{{User.FirstName}}"
    }
  ],
  "ApiName": "Product2"
}

This pattern can sync only products whose owner metadata matches the logged-in user-a simple illustration of user-context filtering.

Mobile configuration

Details

Objects To Sync

Enhanced user-related object filtering