Conditional Logic Properties when using Deal Won Rules

I am utilizing the Deal Pipeline Conditional Stage Properties to require the Sales Team to enter in data for certain properties when moving a Deal to “Closed Won”. One of these properties has conditional logic associated with it, so that if you answer “Yes” it prompts 2 other questions. But this conditional logic is not getting pulled over into the Deal Pipeline rules when a user moves a deal to “Closed Won” it’s just requiring the 2 conditional properties. Any thoughts how this might be solved?

Hey @JLethin - thanks for posting in the Community!

I’d like to tag in some of our experts here to see how this may be possible! @ChrisoKlepke, @HFisher7, and @CateDuarte - any thoughts on how @JLethin may be able to set this up?
Shane, Senior Community Moderator

Hi @JLethin,

Are you sure you set up the conditional logic correctly? You can find instructions here: Set up conditional logic for enumeration properties

This sometimes gets confused with limiting available options based on a controlling property: Limit available options based on a controlling property

When following the steps from the first link, this is working fine for me, see this example where a dependent property is shown when competitors are selected as closed lost reason:

and

If you’re experiencing something else, please show screenshots of your pipeline required property settings as well as your conditional logic for the enumeration property.

Best regards!

Hey @JLethin,
Both conditional stage properties and property-level conditional logic are straightforward when set up correctly, so I want to ensure we’re aligned on the process.

To help with clarity, I’ve added a couple of screenshots below that outline the recommended setup.

Example scenario:
While moving a deal to the Closed Won stage, you have a property called “Contract Signed” with dropdown values (Yes / No).

  • If Yes is selected, additional related properties should appear based on conditional logic.
  • If No is selected, those dependent properties should remain hidden (unless conditional logic is configured for it too)

Could you please confirm the exact steps you’re following while configuring this? This will help us quickly identify any gap that may be getting missed.