Fluent Commerce Logo
Docs

fc.rubix.order.sourcing.conditions

Setting

Changed on:

2 Dec 2025

Setting AreaOrders, UI component
Supported context levels:GLOBAL

Overview

This setting defines the Reference Sourcing Conditions Schema. It:
  • Establishes the structure of available Sourcing Conditions and their parameters
  • Allows business users to configure Sourcing Conditions through the user interface and apply them in Sourcing Strategies
  • Ensures flexibility and consistency in managing sourcing logic

Values

Data TypeValues
JSON

Detailed technical description

The `fc.rubix.order.sourcing.conditions` Setting provides the reference schema of Sourcing Conditions used  for Sourcing Strategies. It defines:
  • the complete list of reference Sourcing Conditions
  • their structure 
  • the user interface (UI) components required to configure them

Key Characteristics

Condition Registry

The Setting acts as a reference catalog of available Sourcing Conditions. Each Condition is represented as a JSON object with:
  • `name`
    unique identifier for the Condition
  • `type`
    mapped to a specific Condition implementation in the `util-sourcing` library (Condition Utilities)
  • One or more `tags` (e.g., Order, Customer, Delivery, Product)
    classify Conditions by corresponding JSON path location of the Sourcing Context 
  • A set of `params`
    describing the JSON `path`, `operator`, and `value` input component (for UI)

Scope Management

Some Conditions include a `conditionScope` parameter, which controls how the Condition is applied when multiple entities are present in the Sourcing Request:
  • ALL – the Condition must be satisfied by every entity (for example, all Products in the request)
  • ANY – the Condition must be satisfied by at least one entity
  • NONE - the Condition must not be satisfied by any entity (for example, no Item in the request may match the specified criteria)
The available `conditionScope` options are defined in the `SourcingConditionConstants` class of the Condition Utilities.This distinction enables precise modeling of business rules across collections such as Products, Networks, or Items.

UI Integration

Business users interact with Sourcing Conditions through the configuration UI. The params definitions (such as `fc.field.multistring`, `fc.field.datetime`, or `fc.field.filterComplex`) ensure that the correct data entry component is automatically rendered for each Condition. For example:

Configuration example

1This setting is automatically available for all accounts and does not require a creation process.

Update example

1This setting is immutable.
2To extend or override specific conditions, a separate fc.rubix.order.sourcing.conditions.custom setting can be created. 
3If a condition with the same name is defined in the custom setting, it takes precedence over the global one. 
4This ensures flexibility while preserving a stable baseline schema.