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

one year ago
Question about the new Event Driven Validation (EDV) Adapter feature. We currently use Patrol to montior certian high-risk actions in Online Banking if the session is deemed suspect only or require a SAC regardless if the login is deemed either non-suspect or suspect. 1. How does this work with how the login is classified? Can you choose to only require EDV if the login is deemed suspect? 2. Can this be used with existing extensions that were developed by Q2? For instance, if we want to require step-auth for Member to Member transfers. Can I create an EDV extension with this new freature to require a SAC for that particular audit action? Thanks Bradley
Question about the new Event Driven Validation (EDV) Adapter feature. We currently use Patrol to montior certian high-risk actions in Online Banking if the session is deemed suspect only or require a SAC regardless if the login is deemed both non-suspect or suspect. 1. How does this work with how the login is classified? Can you choose to only require EDV if the login is deemed suspect? 2. Can this be used with existing extensions that were developed by Q2? For instance, if we want to require step-auth for Member to Member transfers. Can I create an EDV extension with this new freature to require a SAC for that particular audit action? Thanks Bradley
Event Driven Validation (EDV) Adapter

Question about the new Event Driven Validation (EDV) Adapter feature. We currently use Patrol to montior certian high-risk actions in Online Banking if the session is deemed suspect only or require a SAC regardless if the login is deemed both non-suspect or suspect. 1. How does this work with how the login is classified? Can you choose to only require EDV if the login is deemed suspect? 2. Can this be used with existing extensions that were developed by Q2? For instance, if we want to require step-auth for Member to Member transfers. Can I create an EDV extension with this new freature to require a SAC for that particular audit action? Thanks Bradley
#