Can I use the same condition in more than one vService?

Short answer

Yes. Conditions (Conditions) are central and reusable records: a condition defined once can be selected in different Actions, in every vService that uses these actions, in the Conditional Backend Services, WAF Whitelist and Debug Mode condition fields of the vService form, in the profiles that take conditions (Caching, Reports) and in the DDoS Whitelist Condition field of L7 DDoS Protection; no copy is needed. Where the condition is used is followed from the Used in tab in the preview, and a change made to the condition is reflected in all the places where it is used.

How Does It Work?

1. The condition is defined once on the Load Balancer → Conditions screen.
2. The same record is selected in every field where a condition can be selected (action, vService field, profile); its negated form also comes in the same list.
3. Each vService produces its own configuration; the same condition and action are evaluated separately in each vService for its own traffic.

Way	Example
Adding the action that uses the condition to more than one vService	The "Block the management path" action in the Actions field of three vServices
Selecting the same condition in different actions	The office network condition in both the Block and the Add HTTP Header action
Using the condition directly in vService fields	The office network condition in the Conditional Backend Services block of one vService and in the WAF whitelist field of another vService
Using the condition in a profile	The same condition in a caching rule of a Caching profile; the profile is assigned to more than one vService

In TR7

• Condition lists are filtered according to the protocol and phase of the place where the condition will be used: an HTTP-specific condition cannot be selected in an L7 TCP vService, and a condition that works only in the response stage cannot be selected in a Conditional Backend Services block or in an On Request action.
• Hit Counter counts are shown for that vService in the Live Stats · Action Hits section of the vService, and in the Action Hits panel on the home page as the total of all the vServices the action is bound to.
• Conditions that are not used anywhere are found on the Load Balancer → Conditions screen with Filter → Used in → Unused entries.
• In a cluster setup, condition and action changes are transferred to the peer device automatically while Manual Sync Mode is off (default).

Common Misconceptions

• "A copy of the condition is needed for each vService." A single condition is used in all vServices; a copy is created only if a different value is needed for one of the vServices.
• "Every condition can be selected everywhere." The options are filtered according to the protocol and phase of the place of use.
• "Changing the condition affects only one vService." All the vServices that use the condition directly or through an action or profile are affected (When I change a condition or an action, which vServices are affected?).

How it is done in the documentation

• Conditions · Reusability of Conditions
• Conditions · The "Used in" tab must be checked
• Actions · Central, Single-Point Management

Related questions

• When I change a condition or an action, which vServices are affected?
• What is the difference between a Condition and an Action?
• How do I combine multiple conditions with AND / OR?