Pseudo Data Fields for CRM Account Objects

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional CRM systems restrict end users from creating new data fields for account objects, requiring IT intervention and resulting in lengthy delays, especially when temporary fields are 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, enabling users to configure and store user inputs separately from actual CRM data, without needing IT intervention.

Engineering Contradictions & Design Principles

VSEngineering 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

Engineering Contradiction:

Improveease of creating data fieldsVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a pseudo data field object as an intermediary layer between the user interface and the actual CRM account object. This pseudo object handles field creation and data storage requests, allowing users to create fields without directly modifying the CRM system's metadata structure. The pseudo data field controller mediates between user actions and the underlying CRM system, resolving the contradiction by enabling ease of operation while maintaining system integrity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the data field functionality through the pseudo data field object. Instead of allowing direct creation of actual CRM data fields, the system creates a pseudo copy that mimics the behavior and appearance of real fields. This copy can be freely created and modified by users without affecting the actual CRM system's metadata, thus improving ease of operation while avoiding system complexity increases.

Inventive Principle:

Principle #26Copying

2Reliability

If IT professionals create new data fields on CRM account objects, then data integrity is maintained, but the loss of time and productivity decrease

Engineering Contradiction:

Improvedata integrityVSAvoidtime to create data fields

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a pseudo data field object that copies the essential functionality of actual CRM data fields. Users can create and configure these pseudo fields immediately without waiting for IT intervention, as they operate on the pseudo object layer rather than modifying actual CRM metadata. This eliminates the time delay while maintaining data integrity through the controller's mediation.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent enables end users to independently create and manage their own data fields through the pseudo data field mechanism. Users can configure pseudo fields, store data in them, and manage their lifecycle without requiring IT professional involvement. The system provides self-service capabilities that were previously only available through IT channels, thus reducing time loss while maintaining appropriate controls.

Inventive Principle:

Principle #25Self-service

3Stability of the object's composition

If the CRM system allows custom field limits per object, then system stability is maintained, but the adaptability and versatility decrease

Engineering Contradiction:

Improvesystem stabilityVSAvoidadaptability of data fields

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent segments the data field functionality into two distinct layers: actual CRM data fields with system-enforced limits, and pseudo data fields with flexible creation. The pseudo data field object separates the user-facing field creation capability from the underlying CRM system constraints. This segmentation allows the system to maintain stability through actual field limits while providing adaptability through unlimited pseudo field creation for temporary or experimental needs.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces pseudo data fields as temporary, disposable objects that can be freely created and discarded without impacting the permanent CRM system structure. These pseudo fields serve as short-lived placeholders for temporary data collection needs, allowing users to create fields quickly for transient purposes and remove them without affecting system stability. The pseudo fields are inexpensive in terms of system resources compared to actual CRM metadata changes.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS11023667B1System and method for generating and managing pseudo data fields in CRM

Publication Date: 2021.06.01 VEEVA SYSTEMS INC

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.