Pseudo Data Fields in CRM Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional CRM systems, end users are unable to create new data fields for account objects without IT intervention, leading to delays and inefficiencies, especially in industries like pharmaceutical sales where temporary fields are often needed.
Innovation Solution
A method allowing end users to generate and manage pseudo data fields within the CRM system, using a data model with two objects - a pseudo data field configuration object and a pseudo data field object - that behave like actual data fields but do not require IT intervention, enabling users to configure and store user inputs separately from actual CRM data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If end users are authorized to create new data fields on account objects in the CRM system, then the ease of operation and productivity are improved, but the system complexity and data integrity risks increase
Solution Approach 1:
The patent segments the data field system into two distinct types: actual CRM data fields (managed by IT professionals) and pseudo data fields (managed by end users). This segmentation allows end users to create and manage their own fields without affecting the core CRM system structure, thereby improving ease of operation while maintaining system complexity at acceptable levels.
Solution Approach 2:
The patent introduces pseudo data fields as an intermediary layer between end users and the actual CRM system. These pseudo fields act as a buffer that allows user-level customization without requiring changes to the underlying CRM data model, thus enabling user autonomy while preserving system integrity.
2Productivity
If end users are authorized to create new data fields on account objects in the CRM system, then the productivity is improved, but the time for IT intervention and field creation delays are reduced
Solution Approach 1:
The patent enables end users to perform self-service by allowing them to create, configure, and manage their own pseudo data fields directly through the CRM interface without requiring IT professional intervention. This eliminates waiting times and empowers users to immediately address their data needs, significantly improving productivity and eliminating time loss associated with IT request cycles.
3Reliability
If pseudo data fields are stored separately from actual CRM account data, then the data integrity is maintained and system stability is improved, but the device complexity increases
Solution Approach 1:
The patent segments the data storage structure into separate repositories: actual CRM account data is stored in the core CRM database, while pseudo data field values are stored in a separate pseudo data field object. This segmentation maintains data integrity by preventing user-created fields from contaminating or complicating the core CRM data model, while the separation itself manages complexity through clear architectural boundaries.
Data Source
AI summary
Systems and methods for generating a pseudo data field in a CRM system to allow end users to generate and manage pseudo data fields for account objects in the CRM system, which may behave like actual data fields of account objects in the CRM system but live outside the CRM account. The present invention uses a data model that includes two objects to allow end users to generate and manage the pseudo data fields. One of the objects is pseudo data field configuration object, which may be used to configure the pseudo data fields that should be made available to end users. The other object is pseudo data field object which may be used to record user responses or values users use to populate the pseudo data field.