Reusable Process Model Objects for Multi-Condition, Multi-Action Workflows

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software applications struggle to support workflows with multiple conditions and multiple actions due to the lack of a defined structure, making it infeasible to store and maintain static files for every possible multi-condition, multi-action workflow.

Innovation Solution

Dynamically generate a process model object for multi-condition, multi-action workflows using a template, superimpose user-provided information with implicit information, and store the structure of the model object in a data store for reuse, avoiding the need for full process model objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static files are used to represent workflows, then single condition single action workflows can be supported, but multi-condition multi-action workflows cannot be supported due to lack of defined structure

Engineering Contradiction:

Improveworkflow complexity supportVSAvoidstructure definition complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent transitions from static workflow files to dynamic process model objects that can adapt to different workflow configurations. The system dynamically generates and executes workflow definitions at runtime, allowing the same infrastructure to handle varying levels of workflow complexity without requiring predefined static structures for each scenario.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The invention creates a universal process model object framework that can represent both simple single-condition/single-action workflows and complex multi-condition/multi-action workflows using the same underlying structure. This unified approach eliminates the need for different representation methods for different workflow types.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If static files are stored for every possible workflow, then complete workflow definitions are available, but storage and maintenance becomes infeasible due to large volume of unique workflows

Engineering Contradiction:

Improveworkflow definition completenessVSAvoidnumber of workflow files

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

Instead of storing complete workflow definitions for every possible scenario, the system stores template process model objects that can be copied and instantiated multiple times with different parameters. This allows the same underlying template to serve multiple workflow variations, dramatically reducing the number of files that need to be stored and maintained.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The invention uses parameterized process model objects where specific workflow variations are achieved by changing parameters rather than creating entirely new files. This parameter-driven approach allows the system to generate specific workflow instances from general templates, reducing storage requirements while maintaining the ability to define complete workflows when needed.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If process model objects are stored for reuse, then configuration efficiency improves, but computational resources and storage are consumed

Engineering Contradiction:

Improveworkflow configuration efficiencyVSAvoidcomputational resource consumption

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The system extracts and stores only the essential structural elements of process model objects for reuse, rather than storing complete process model objects with all their data and configurations. This extraction approach allows efficient reuse of core workflow patterns while minimizing storage requirements and computational overhead for managing reusable components.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20250278280A1Dynamically generating a reusable process model object for a workflow including multiple conditions and multiple actions

Publication Date: 2025.09.04 INTUIT INC

AI summary

A method for dynamically generating process model objects for workflows includes: obtaining a request from a user of a software application for configuring workflows, the request being for an initial workflow including multiple conditions and multiple actions, the request including user-provided information for one or more of the multiple conditions and one or more of the multiple actions; mapping the initial workflow to a template for generating process model objects for workflows, the template comprising a single condition block to represent the multiple conditions and a single action block to represent the multiple actions; extracting the user-provided information from the request; and dynamically generating a process model object for the initial workflow based, at least in part, on the extracted user-provided information and information associated with the template.