The Schain Nodes Filter allows you to apply an action to a request based on the number of nodes in its Supply Chain object. The filter evaluates the final number of nodes available in the request at the time of filtering. If the client adds himself as a node to the Supply Chain, this node is included in the count.
For example, if the original request contains one publisher node and the client adds himself as the second node, the total number of nodes is two.
Configuration options
The Schain Nodes Filter consists of:
Action
The action defines what happens when the request matches the configured node-count condition.
Available actions:
| Allow | Filter |
| The request is allowed when its number of Schain nodes satisfies the selected condition. Requests that do not satisfy the condition are filtered out. | The request is filtered out when its number of Schain nodes satisfies the selected condition. Requests that do not satisfy the condition are not filtered by this rule.
|
Comparison operators
The following comparison operators are available:
| Greater equal | The condition is satisfied when the number of Schain nodes is greater than or equal to the configured value. For example, with: Allow requests with Greater equal 3 ⦁ 3 nodes - allowed; ⦁ 4 nodes - allowed; ⦁ 2 nodes - filtered out. The configured value is inclusive. Therefore, Greater equal 3 means ≥ 3, not > 3. |
| Equal | The condition is satisfied only when the number of Schain nodes exactly matches the configured value. For example, with: Allow requests with Equal 3 ⦁ 3 nodes - allowed; ⦁ 2 nodes - filtered out; ⦁ 4 nodes - filtered out. |
| Less equal | The condition is satisfied when the number of Schain nodes is less than or equal to the configured value. For example, with: Allow requests with Less equal 3 ⦁ 1 node - allowed; ⦁ 2 nodes - allowed; ⦁ 3 nodes - allowed; ⦁ 4 nodes - filtered out. |
| Less | The condition is satisfied when the number of Schain nodes is lower than the configured value. For example, with: Allow requests with Less 3 ⦁ 1 node - allowed; ⦁ 2 nodes - allowed; ⦁ 3 nodes - filtered out; ⦁ 4 nodes - filtered out. |
Numeric node-count value
The filter counts the nodes that are present in the request when the rule is evaluated. If the client adds himself as a node, the client node must be included in the total count.
Example
Assume the configuration is -> Allow requests with Greater equal 3
The original request contains one publisher node. The client adds himself to the Supply Chain as an additional node.
The final request contains:
⦁ 1 publisher node;
⦁ 1 client node.
Total: 2 nodes. Because 2 is less than 3, the request does not satisfy the condition and is filtered out.
If the incoming request contains four nodes, the request satisfies the condition because: 4 ≥ 3
Therefore, the request is allowed.
Numeric value
The node-count field accepts a number, such as:
⦁ 1;
⦁ 2;
⦁ 3.
The number is used together with the selected comparison operator to evaluate the Schain node count.
Summary
The Schain Nodes Filter evaluates the number of nodes in the final Supply Chain object.
To configure the filter:
1. Select an action, Allow or Filter.
2. Select a comparison operator.
3. Enter the required number of nodes.
4. Apply the rule to the request.
When counting nodes, include the client node if you add yourself to the Supply Chain.