Description: Right now, conditional logic in Record Customization for property cards only allows a property card to be displayed if a property equals a specific value. This is helpful, but it limits flexibility in building more dynamic, context-aware record views. Use Case: For example, I want to show Card A if a dropdown property equals “Active.” But I also want to show Card B if that same property is either blank (unknown) or set to something else (e.g., “Inactive,” “Archived,” etc.). Currently, there’s no way to set conditions for “not equal to” or “is unknown”, which would let us build cleaner and more user-specific record views. Request: Please add support for additional conditional logic in property card display rules, such as: • “Is not equal to” • “Is unknown” • “Contains” or multi-option matching This would be a huge improvement for customizing internal CRM experiences based on record status, lifecycle stage, or any property used for internal segmentation or process control. Thanks!
...read more