NoSQL Selection Rules
The primary role of a NoSQL selection rule is to execute queries against a NoSQL database. As such, it serves as the analog of a standard or basic selection rule in a SQL environment. You can configure criteria within a NoSQL selection rule, and then get a count of the records that match the criteria. You can use NoSQL selection rules to configure blocks within an audience, and execute them when running interaction workflows, in order to retrieve records in respect of which to take action.
NoSQL selection rules are made available in the Rule Designer toolbox when running RPI against a NoSQL data warehouse, or where the current RPI client has been configured with one or more NoSQL auxiliary databases.
You can generally use a NoSQL selection rule in a NoSQL environment in other contexts where you would use a standard or basic selection rule for SQL. For example, you would set a channel Filter using a selection rule at a SQL client, but you would do the same using a NoSQL selection rule at a NoSQL client.
NoSQL selection rules can also be used to make content applicability decisions at a rule smart asset.
Further information on using NoSQL selection rules can be found across the RPI documentation.
Access to NoSQL selection rule functionality is controlled by the following functional permissions:
Selection Rule – NoSQL – Count
Selection Rule – NoSQL – Data Viewer
Selection Rule – NoSQL – Design
Selection Rule – NoSQL – Export
This section details features of NoSQL selection rules that are specific to the file type. Details of features shared between NoSQL selection rules and other files supported in the Rule Designer can be found in that interface’s documentation.
In this section: