Query Filter Decision node
The Query Filter Decision node checks if the contents of a user’s profile match the specified query filter.
Use this node to check whether an attribute of the user profile matches a specific pattern. For instance, use this in progressive profile flows to check if marketing preferences are set on a user’s profile.
Compatibility
| Product | Compatible? |
|---|---|
Advanced Identity Cloud |
Yes |
PingAM (self-managed) |
Yes |
Ping Identity Platform (self-managed) |
Yes |
Inputs
This node reads the Identity Attribute from the shared node state.
If it can’t read the Identity Attribute, it reads the userName.
It uses the value to look up the identity object.
Configuration
| Property | Usage |
|---|---|
Query Filter |
A query filter used to check the contents of an object. For details on constructing effective query filters, refer to Construct queries. Default: none |
Identity Attribute |
The attribute used to identify the managed object in the underlying identity service. Default: |
Example
Other journeys invoke the following progressive profile journey to capture missing profile attributes:
-
The Login Count Decision node triggers the rest of the journey depending on the login count and its settings.
-
The Query Filter Decision node determines whether managed object profile fields are missing.
-
The Attribute Collector node in the Page node requests additional input for the profile.
-
The Patch Object node stores the additional input in the managed object profile.