Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
← Back to post

Revisions 2

Original
pic
⠿More
Jarrod Marshall
13 × 2
Configuration with multitenant configuration - best practices
Configuration with multitenant extension - best practices
Hi team, When building a multitenant extension is the configuration in the extension at the tenant (FI) level or is it global? I'm not familiar with the install/setup process per tenant so I was wondering if things like REQUIRED_CONFIGURATIONS or WEDGE_ADDRESS_CONFIGS are global or tenant specific? Example: I want to allow custom messaging per tenant/FI. Which route would be best?
Hi team, When building a multitenant extension is the configuration in the extension at the tenant (FI) level or is it global? I'm not familiar with the install/setup process per tenant so I was wondering if things like REQUIRED_CONFIGURATIONS or WEDGE_ADDRESS_CONFIGS are global or tenant specific? Example: I want to allow custom messaging per tenant/FI. Which route would be best?
#
#
one year ago
pic
⠿More
Jarrod Marshall
13 × 2
Configuration with multitenant extension - best practices
Hi team, When building a multitenant extension is the configuration in the extension at the tenant (FI) level or is it global? I'm not familiar with the install/setup process per tenant so I was wondering if things like REQUIRED_CONFIGURATIONS or WEDGE_ADDRESS_CONFIGS are global or tenant specific? Example: I want to allow custom messaging per tenant/FI. Which route would be best?
#