fc.rubix.order.sourcing.criteria
Setting
Changed on:
26 Sept 2025
| Setting Area | Orders, UI component |
|---|---|
| Supported context levels: | GLOBAL |
Overview
This Setting defines the Reference Sourcing Criteria Schema. It lists:
- available Sourcing Criteria
- their tags
- parameter descriptors (including UI component metadata)
It allows business users to configure Criteria within Sourcing Strategies.
Packages
Values
| Data Type | Values |
|---|---|
| JSON | |
Detailed technical description
The `fc.rubix.order.sourcing.criteria` Setting provides the reference schema of Sourcing Criteria used for Sourcing Strategies. It defines:
- the complete list of reference Sourcing Criteria
- their structure
- the user interface (UI) components required to configure them
Key Characteristics
Criterion Registry
The Setting acts as a reference catalog of available Sourcing Criteria. Each Criterion is represented as a JSON object with:
`name`
unique identifier for the Criterion`type`
mapped to a specific Criterion implementation in the`util-sourcing`library (Criteria Utilities)`tags`(e.g., ATS-agnostic, ATS-dependent, Exclusion)
classify Criteria by behavior- A set of
`params`
define configurable inputs and the UI components used to capture them (for example, threshold values, banded lists, or unit selectors)
Evaluation Order
Criteria are applied in the sequence they are defined within a Strategy:
- Exclusion Criteria (e.g., distance or network exclusions) can remove candidate Locations early in the evaluation
- Ranking Criteria assign ratings that are then normalized and compared across Locations
- Additional Criteria serve as tie-breakers until a final ranking is established
This distinction enables precise modeling of sourcing priorities across metrics such as distance, availability, and capacity.
UI Integration
Business users interact with Sourcing Criteria through the configuration UI. The `params` definitions (such as `fc.field.multistring`, `select`, `integer`, or `input`) ensure that the correct entry component is automatically rendered for each Criterion. For example:
`fc.field.multistring`supports lists of values with optional exact match validation (`"exactSearch": true`)`select`presents predefined options, such as measurement units (`kilometres`or`miles`)`integer`captures numeric thresholds (e.g., minimum availability percentage)`input`allows direct entry of a single numeric or text value
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 criteria, a separate fc.rubix.order.sourcing.criteria.custom setting can be created.
3If a criterion 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.