Current Limitation
Currently in Freshsales, when setting up dependent fields, the dependent field is automatically positioned below its parent field in the record layout. While this relationship makes sense logically, it creates limitations in designing optimal layouts for our teams' workflows.
Use Case
In our organization, we need certain fields to become required based on other field values, but we want to maintain our carefully designed layout that groups related information together. The current dependent field functionality forces us to compromise between having conditional requirements and maintaining an intuitive layout.
Proposed Enhancement
Add the ability to make fields conditionally required without forcing them to be repositioned in the layout. This would:
- Allow fields to become required based on other field values
- Maintain the field's original position in the layout
- Preserve our ability to group related fields together logically
- Keep our forms clean and intuitive for our users
Benefits
- Improved User Experience: Users can work with forms that maintain a logical flow and grouping of information
- Better Data Quality: We can still enforce data requirements when needed
- Flexible Layout Design: Administrators can create optimal layouts without compromising on data validation rules
