Dynamic Form Integration in Word Processing via API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud-based database systems, integrating and managing data across different types of files remains a manually intensive and time-consuming process, often leading to duplicate efforts and stale data versions, as users need to create and manage multiple versions of forms and surveys across various platforms.

Innovation Solution

A system that integrates an Application Programming Interface (API) into word processing applications to enable the creation and management of dynamic forms within documents, allowing users to define form fields and configurations, which are then stored in a document database, and automatically syncs responses to a spreadsheet database, reducing manual effort and improving collaboration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If forms are manually created and managed across different platforms, then users can collect and analyze response data, but the process becomes time-consuming and requires manual inspection and updates

Engineering Contradiction:
Improveform management efficiencyVSAvoidtime for form creation and updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent merges the form creation and management functionality directly into the word processing application interface. When users type a trigger phrase like '@form' in a document, the system automatically generates a form within that same document context, eliminating the need to switch between separate form creation tools and document editors. This integration allows users to create, distribute, and collect responses to forms without leaving their word processing environment, significantly reducing the time and effort required for form management.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If forms are created as standalone files, then they can be distributed independently, but they become stale as changes occur in the source file or database

Engineering Contradiction:
Improvedata synchronizationVSAvoidform update capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements automatic feedback mechanisms that continuously monitor the source document and database for changes. When the source file or database is updated, the system automatically detects these changes and updates the embedded forms accordingly. This feedback loop ensures that forms remain synchronized with the latest data without requiring manual intervention, maintaining both reliability of data synchronization and adaptability to changes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent embeds form templates and structures directly within the source document during the initial creation phase. By pre-configuring the form fields, data sources, and update mechanisms within the document itself, the system prepares the form to automatically adapt to future changes in the source data, eliminating the need for separate form files and ensuring continuous synchronization.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If multiple versions of forms are managed manually, then different iterations can be tracked, but duplicate efforts and version control become problematic

Engineering Contradiction:
Improveform version trackingVSAvoidversion management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system creates embedded copies of form structures directly within the source document, rather than maintaining separate form files. Each form is generated as a lightweight representation that references the master data source, automatically copying only the necessary structural information while maintaining a single source of truth. This approach tracks version changes through the document's own version control mechanisms without requiring separate form version management.

Inventive Principle:
Principle #26Copying

4Extent of automation

If forms are integrated within documents using API, then automation and real-time updates are achieved, but the system complexity increases

Engineering Contradiction:
Improveform integration automationVSAvoidsystem integration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces a lightweight intermediary component that sits between the word processing application and the data source. This intermediary automatically handles the complex tasks of form generation, data binding, and synchronization without requiring the user to directly manage the integration complexity. The intermediary translates simple user actions (like typing '@form') into sophisticated automated processes, achieving high automation while masking the underlying system complexity from end users.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11416677B2Dynamic resource management systems and form integration methods
Publication Date: 2022.08.16 SALESFORCE INC
  • US11416677B2 patent drawing
  • US11416677B2 patent drawing
  • US11416677B2 patent drawing

AI summary

Computing systems, database systems, and related methods are provided for supporting dynamic resources. One exemplary method involves generating a graphical representation of a document on a client device communicatively coupled to the server over a network, receiving indication to add a form to the document, generating one or more graphical user interface elements manipulable to define one or more fields of the form within the graphical representation of the document in response to the indication, receiving metadata defining the one or more fields of the form via the one or more graphical user interface elements, and storing the metadata defining the one or more fields of the form in a database in association with a document object corresponding to the document.