fc.mystique.filters.string
Changed on:
26 Nov 2025
| Setting Area | UI component |
|---|---|
| Supported context levels: | ACCOUNT |
Overview
`fc.mystique.filters.string` is an account-level setting that controls wildcard behavior for all string-based filters. It defines whether search uses partial matching (starts with/contains), exact matching (no wildcards), or a mix (e.g., only trailing wildcard). This helps balance performance and usability by avoiding costly leading-wildcard queries while still allowing flexible search.
New accounts will include this setting by default for consistent behavior.
Values
| Data Type | Values |
|---|---|
| JSON |
|
Detailed technical description
Parameters
`prefix`- Controls whether a leading wildcard is applied.`true`→ search pattern becomes`"%value"`(matches any text ending with the input).`false`→ no leading wildcard (search starts with the input).
`postfix`- Controls whether a trailing wildcard is applied.`true`→ search pattern becomes`"value%"`(matches any text starting with the input).`false`→ no trailing wildcard (search ends with the input).
Behavior
- If
`prefix`is not specified (undefined) → treated as`false`(no leading wildcard). - If
`postfix`is not specified (undefined) → treated as`false`(no trailing wildcard).
Examples
1{
2 "prefix": false,
3 "postfix": true
4}1{
2 "prefix": true,
3 "postfix": true
4}1{
2 "prefix": false,
3 "postfix": false
4}System default (when setting is not defined)
If `fc.mystique.filters.string` is not defined at all, the system default is full wildcard search (`%value%`)
(both `prefix` and `postfix` treated as `true`) to maintain backward compatibility.
Interaction with field-level overrides
- Individual string filters (
`fc.filter.string`) can define a field-level override via the`wildcardFilter`property. - When
`wildcardFilter`is defined for a filter, it overrides`fc.mystique.filters.string`for that specific field. - When
`wildcardFilter`is not defined, the filter uses the global behavior from`fc.mystique.filters.string`(or the system default if the setting is missing).
This makes `fc.mystique.filters.string` the default wildcard policy for an account, with the option to fine-tune specific filters as needed.
Configuration example
1POST: {{fluentApiHost}}/graphql
2
3
4GraphQL Query:
5mutation CreateSetting {
6createSetting(input: {
7 name: "fc.mystique.filters.string",
8 valueType: "JSON",
9 lobValue: "{ \"prefix\": false, \"postfix\": true}",
10 context: "ACCOUNT",
11 contextId:0}) {
12 id
13 name
14 }
15}Update example
1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4 updateSetting(input: {
5 id: 1,
6 name: "fc.mystique.filters.string",
7 valueType: "JSON",
8 lobValue: "{ \"prefix\": true, \"postfix\": false}",
9 context: "ACCOUNT",
10 contextId: 0}) {
11 id
12 name
13 }
14}