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
 
Answered
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?

Votes Newest

Answers


Using Global in quotations here for ease of understanding. Global will be in context of the running service in Staging or Production.

Anything stored in the repository will be global and anything stored in the database will be per environment. Vault can be either per environment or global. For custom messaging, I recommend either Wedge_address_configs or UI_Text(https://docs.q2developer.com/docs/guides/online_integration/ui_text.html)

-Trey

Posted one year ago
Trey Teter
489 × 4 Administrator
102 Views
1 Answer
one year ago
one year ago