CRM View Layout Customization With Drag-and-Drop Grouping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional Customer Relationship Management (CRM) applications lack native customization capabilities for list and detail views, requiring workarounds like integrations or paid services for redesign, without implicit, built-in solutions.
Innovation Solution
A dynamic CRM page design system using a no-code, drag-and-drop interface with enhanced grouping techniques, allowing users to customize CRM pages on a blank canvas, integrating with ZOHO applications, and optimizing layout through a layout building engine that handles overlapping elements using wrappers and absolute positioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional CRM applications are used, then system stability is maintained, but customization capability is lost
Solution Approach 1:
The CRM interface is segmented into reusable component blocks (header, footer, content areas, navigation elements) that can be independently configured and assembled. This allows customization without redesigning the entire system, resolving the contradiction by enabling adaptability through modular components while maintaining system stability.
Solution Approach 2:
The system transitions from static predefined layouts to dynamic configurable interfaces where users can modify component positions, visibility, and properties at runtime. This dynamic approach enables customization while the underlying system architecture remains stable and manageable.
2Adaptability or versatility
If workarounds like integrations or paid services are used for redesign, then customization capability is improved, but cost and complexity increase
Solution Approach 1:
The system enables end-users to perform customization themselves through an intuitive drag-and-drop interface and configuration options, eliminating the need for external integrations or paid services. Users can independently modify their CRM interfaces, resolving the contradiction by making customization accessible without additional cost or complexity.
Solution Approach 2:
The customization engine provides universal capabilities that work across different CRM modules and user roles through a single unified interface. This multi-functional approach replaces multiple specialized integrations with one versatile native solution, improving ease of implementation.
3Adaptability or versatility
If native customization capabilities are added to CRM applications, then adaptability is improved, but device complexity increases
Solution Approach 1:
The customization system is nested within the existing CRM architecture as a configurable layer that leverages underlying framework capabilities. This nested structure allows customization features to be added without fundamentally redesigning the core system, managing complexity through layered architecture.
Solution Approach 2:
Customization is achieved through parameter configuration rather than structural modification. Users adjust parameters such as component visibility, positioning, and properties through a configuration interface, allowing adaptability without increasing system complexity.
4Adaptability or versatility
If computed fields and formulas are used, then functionality is improved, but computational requirements increase
Solution Approach 1:
Computed fields and formulas are pre-compiled and cached during system initialization or when dependencies change, rather than being evaluated in real-time for every operation. This preliminary computation reduces runtime computational requirements while maintaining full functional capability.
Data Source
AI summary
Disclosed are techniques to facilitate Customer Relationship Management (CRM) data utilization and display to suit organizational and team goals, methods, requirements, and more. A system includes a CRM page building engine, a layout building engine, a rendering engine, a request handling engine, a CRM datastore, an element datastore, and a layout datastore. For example, a design system is implemented as a no-code builder that facilitates creation through a drag-and-drop interface, which is intuitive and user-friendly. A layout building engine processes the CRM element data, which comprises the absolute position of the CRM element on the canvas. The layout building engine performs grouping and/or sub-grouping process to wrap the CRM element in the layout. The layout building engine outputs layout data for each element. The resulting element set is a separable element set or a non-separable element set. The resulting set is aligned to place its elements in the exact position or order. On successful fetching of all the required data, the layout data will be mapped with the CRM data and its application elements, based on its type and the action to be performed.