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
Are WEDGE_ADDRESS_CONFIGS supported in an SSOHandler or must/should I use VENDOR_CONFIGS?

I want some configuration settings in my SSO extension to be sourced from the database and was following the instructions from the Online Banking Form Tutorial in the Configuration section to use WEDGE_ADDRESS_CONFIGS:
https://docs.q2developer.com/tutorials/online_banking/configuration.html
and to pump them into the database using the cli

$ q2 update_installed

but nothing seems to end up in the database.

Looking at the SSO Extension Tutorial, I see VENDOR_CONFIGS being used. Is that the way to go for SSO Extension configs?

Many thanks,
Bill

Posted 4 years ago
Votes Newest

Answers


nvm

Found the answer a bit lower down in the SSO Tutorial:

If you take a look at the example SSO extension above, you will see a VENDOR_CONFIGS dictionary. SSO extensions are located in the Q2_Vendor database table, whereas other SDK extensions are located in the Q2_Form table. This means that SSO extensions can not use the standard Wedge address configs. If you need values stored in the database, use VENDOR_CONFIGS. For most development purposes, vendor configs work exactly the same as Wedge address configs. Define them in the extension, and they are populated into the database at install and can be changed. Access them in your code using self.vendor_configs.get()

Posted 4 years ago
218 Views
1 Answer
4 years ago
4 years ago
Tags