In the conditional logic for properties it’s only possible to choose one property at the moment as the controlling property. To create more sophisticated dependencies, it would be helpful, to combine multiple properties as the controlling condition (e.g. “Pipeline” = “Sales Pipeline” AND “Product Type” = “Product A”)
This would be very useful for us as well. Sometimes pipelines have different requirements, and it would be great to be able to add that in as a condition in addition to another controlling property,
I just stumbled upon conditional properties today (wow). I’ve been looking for this specifically for ticket pipeline statuses for quite some time! But… it’s half-baked. Similar to forms, there’s only a single layer of logic (the “controlling property” logic), which isn’t helpful for my org in the vast number of situations I need it for.
Example:
If pipeline is A, status is B, and product type is C, then require X, Y, and Z
Definitely needed !! Same use case as mentionned above.
Definitely needed ! I have the same use cases as mentionned above. It is too restrictive right now and could be way more powerful if we could add some “AND” conditions.
+1 on behalf of a customer 
Would be great to have this option!
+1, same use cases as above. Not having this leads us to create more Pipelines than we would otherwise need to achieve this logic and it is still not where we need it.
+1 on behalf of a customer too!
I was just thinking how I needed to include two properties in one condition related to our Support teams ticket management.
I want certain properies to be required when my team closes a ticket.
For example, Request type = XYZ & Ticket Status = XYZ
Definitely needed !!
+1, absolutely needed !
It would be helpful to be able to create conditional property logic based on more than one controlling property. At the moment, it is only possible to set up conditional property logic based on one property i.e. if Property A = X, show property B.
However, we’d like to set it up so that if Property A = X AND Property B = X, show Property C.
This would be really helpful to make sure we’re only showing the most relevant information for our team!
+ 1, we need it !!!
Agreed! More sophisticated controlling property capability would make such a big difference to our deal processes.
Still no update on this, clients are crying out for it!
+1 this is very limiting at the moment.
Hi everyone! My name is Hallie and I’m a Program Manager on the CXM Team. Thanks so much for all of your feedback on this feature. 
Improvements to conditional logic for properties such as this are being made this year, and I will be updating this post as more details become available. In the meantime, please continue to upvote and leave feedback on this post for our product team. Thank you!
+1. AND/OR logic support would dramatically expand what’s possible for enforcing data hygiene. This kind of compound logic is fairly foundational to rule-based systems.
For context, I’d like to require that my users populate certain deal properties before they can mark any deals for a certain subset of products as late stage. But that requires AND/OR logic, so currently I have to use a workflow workaround to populate a null value in deals where the property doesn’t apply. It’s messy, complicated, and potentially confusing to have to explain to others. Would love to see this on the roadmap.
@hhiggins Hi Hallie! Great to see that this is finally getting attention!
Are there any updates or an ETA for when this might be released?