NextGen FSM
2026 Wave Two 2026 Wave One 2025 Wave Two 2025 Wave Three
NextGen FSM
2026 Wave Two 2026 Wave One 2025 Wave Two 2025 Wave Three
Breadcrumbs

Configure the procurement request default filter in the mobile app

This Reference topic provides the technical specifications and configuration details for the company.fsm.mobile.ProcurementRequestDefaultStatusFilter parameter. This parameter allows administrators to define the default status filter applied to the Procurement Request monitor within the mobile application.

Overview

By configuring this company-level parameter, you can align the mobile user experience with your organization’s operational workflow. For example, setting a default status of Successfully Sent ensures technicians immediately see items ready for pickup, while not setting it provides a full lifecycle view of all requests.

Parameter Specifications

The following table outlines the configuration requirements for the default filter parameter.

Property

Details

Parameter Key

company.fsm.mobile.ProcurementRequestDefaultStatusFilter

Type

String

Access Level

System Administrator / Configuration Interface

Default Behavior

If empty or invalid, the system dont’t set the filter and shows ALL the procurement request

Allowed Values

The parameter accepts the following case-sensitive status codes. These codes must align with the backend master data and are typically retrieved by the mobile app via the Statuses API.

Status Code

Display Name (Description)

<empty string>, not set

All Statuses (Default)

SENT_OK

Successfully Sent

SATISFIED_PARTIAL

Partially Satisfied

SATISFIED_FULL

Fully Satisfied

NOT_SATISFIED

Not Satisfied

Note: While the system supports various status codes (such as DRAFT, OPEN, or CANCELLED), the mobile filter is primarily optimized for the logistics-driven codes listed above.

System Validation and Fallback Logic

To ensure application stability, the FSM platform and mobile client adhere to the following validation rules:

  • Validation at Configuration: The administration interface validates that the entered value is either <empty> or a valid status code.

  • Runtime Fallback: If the parameter is missing, contains an invalid value, or refers to a status code not returned by the API during mobile synchronization, the mobile app will automatically fallback to the <empty> filter.

  • Consistency: This is a company-level setting. All mobile users within the same environment will inherit this default filter setting upon initialization.

  • How to configure Company Parameters