Increment Login Count node
The Increment Login Count node increments the successful login count property of a managed object.
Use the Login Count Decision node to change the flow of the journey based on the count.
Compatibility
| Product | Compatible? | ||
|---|---|---|---|
PingOne Advanced Identity Cloud |
Yes |
||
PingAM (self-managed)
|
Yes |
||
Ping Identity Platform (self-managed) |
Yes |
Inputs
This node’s Identity Attribute specifies the property it requires in the incoming node state. It uses this property to access the managed object.
Configuration
| Property | Usage |
|---|---|
Identity Attribute |
The attribute used to identify the managed object in IDM. Default: |
Errors
If this node fails to access the managed object, it throws an exception with a No object to increment message.
If this node fails to increment the login count, it logs an Unable to increment login count warning message.
Example
The following journey uses the Increment Login Count node to update the login count on successful authentication:
-
The Platform Username node injects the
userNameinto the shared node state. -
The Data Store Decision node determines whether authentication is successful.
-
The Increment Login Count node (outlined in the image) updates the login count.
-
The Inner Tree Evaluator node invokes the following nested journey for progressive profiling:
-
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 still missing.
-
The Page node requests additional input for the profile.
-
The Patch Object node stores the additional input in the managed object profile.