Record Templates for Dynamic Workflow Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems lack an efficient mechanism to automatically create and manage interrelated records across projects, making it time-consuming and error-prone to replicate workflows from one project to another, especially in project management where similarities in workflow exist.

Innovation Solution

A database system that applies record templates to create interrelated records across tables, enabling dynamic calculation of start and end dates, and managing dependencies, allowing for repeatable and scalable workflows by using a record template module to instantiate data objects with predetermined relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If workflows are manually copied from one project to another, then project replication is possible, but the process is time-consuming and error-prone

Engineering Contradiction:
Improveworkflow replication accuracyVSAvoidtime to replicate workflows
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates templates from existing project workflows that can be copied and applied to new projects. The template module captures the structure, tasks, and relationships of existing workflows, enabling automated replication without manual copying, thus reducing both time and errors.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-defining workflow templates with all necessary tasks, dependencies, and configurations before project creation. This allows workflows to be instantly applied to new projects without manual setup, eliminating the time-consuming manual copying process while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If automations and scripting are used to semi-automate workflow replication, then some automation is achieved, but detailed understanding of records and schema is required and tailoring to specific use cases is still needed

Engineering Contradiction:
Improveworkflow replication automationVSAvoidsystem configuration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The template module enables self-service automation by automatically capturing workflow structures and applying them to new projects without requiring users to write scripts or configure complex automations. The system handles the replication process autonomously based on predefined templates, reducing both automation extent and configuration complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The template system provides universal functionality that works across different project types and use cases. A single template can be applied to multiple projects with different configurations, eliminating the need for custom scripting for each specific use case while maintaining high automation levels.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If databases are designed specifically for each project, then project-specific requirements are met, but prior projects cannot be efficiently reused

Engineering Contradiction:
Improveproject-specific database adaptabilityVSAvoidworkflow creation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments database schemas into reusable template components that can be independently applied to different projects. The template module divides workflow structures into modular units (tasks, dependencies, configurations) that can be selectively replicated, allowing project-specific adaptation while maintaining efficiency through reuse of common elements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The template system provides dynamic adaptability where templates can be customized and configured for different project types while maintaining a consistent underlying structure. This allows the same template framework to serve multiple project-specific needs, balancing adaptability with reusable productivity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240330027A1Record Templates
Publication Date: 2024.10.03 FORMAGRID INC
  • US20240330027A1 patent drawing
  • US20240330027A1 patent drawing
  • US20240330027A1 patent drawing

AI summary

A database system provides templates that can be applied to create new data objects. The database system may instantiate a data object having fields that are dynamically calculated based on data in other data objects. In some instances, the database system may dynamically calculate start or end dates for a project based on another date in another project. Data objects and templates can be linked in various dependencies, such as a parent template that can be linked to multiple children templates in a linear order, where the database system can update a value at the parent template and automatically have the update flow through the sequence of children templates due to the linked relationship.