In Product Configuration expressions, the current Implies operator behaves bi‑directionally, which can result in unintended constraint behavior when only a one‑way dependency is required.

There is a strong need for a unidirectional (one‑way) operator, similar to Implies, but without reverse enforcement. This would allow configuration rules where the source condition enforces a target condition, but not vice versa.

Current issue:

Today, when using the Implies operator in expression constraints, selecting the target condition can indirectly enforce or restrict the source condition as well. This makes it difficult to model common real‑world configuration logic where dependencies are strictly one‑directional.

As a result-

• Configuration logic becomes more complex
• Additional workaround constraints are required
• Models are harder to maintain and understand
• Risk of incorrect product combinations increases

Proposed Solution

Introduce a new unidirectional operator (for example: ImpliesOneWay, IfThen) that:

• Enforces the constraint only when the source condition is met
• Does not apply any reverse logic
• Does not restrict the source when the target is independently selected