This answer provides a way to capture the following common pattern for Rules: "If conditions A and conditions B, then do actions" for fixed conditions A and actions. Instead of creating a separate condition set component for every conditions B (and then use those components inside some kind of "abstract" Rules component as a variable), the following approach is way easier:
- Create a condition set component for conditions A, say My component for conditions A.
- Create an action set component for actions, say My component for actions.
- For every conditions B, create a new Rule.
- For every new Rule, add My component for conditions A to the conditions, and My component for actions to the actions. Then, complement the conditions with conditions B.
Result: we fixed the never-changing conditions A and actions in 2 Rules components. That saves us a lot of redundant repetitive work. If we want to implement 10 cases of the general pattern, then we end up with 10 Rules + 2 Rules components = 12 Rules in total.
Let's compare this approach with the initial idea. We would have to create 10 Rules components for the conditions B + 1 "abstract" Rules component + 10 Rules that contain this "abstract" Rules component in their actions = 21 Rules in total.
The advantage of the proposed alternative approach is less Rules in total. The disadvantage is that every Rule needs to include the same action set and condition set components. But to be honest, adding those 2 components to the Rules takes much less clicks and time than creating new Rules... I think this problem nicely illustrates the power of action sets and condition sets in the Rules module (a feature that might seem somewhat obscure for beginners).