Flow Template Engine for Real-Time Metadata Propagation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing digital interfaces for entities like retailers and corporations require cumbersome and error-prone processes for propagating changes throughout sequential flows, leading to frustrating user experiences, costly delays, and inefficient resource usage.

Innovation Solution

A system that allows for seamless propagation of metadata changes throughout master and sub-flows during runtime, using a centralized source to define and modify runtime configurations, enabling environment-specific variables and bypassing sub-flows with custom metadata, thus avoiding the need for new flow versions and deployments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If changes are propagated throughout sequential flows by creating new flow versions, then the digital interfaces can function correctly, but the process becomes slow and error-prone

Engineering Contradiction:

Improvecorrectness of digital interface functionVSAvoidtime for propagation process

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating flow templates that pre-define sequential flows with all necessary configurations. When changes are needed, the system propagates modifications to existing flow instances based on the template, rather than creating entirely new versions. This preliminary structuring allows for efficient updates while maintaining correctness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses flow templates as reusable copies that can be instantiated multiple times. Instead of manually creating and propagating changes through each flow version, the system copies the template definition and automatically propagates modifications to all instances, significantly reducing the time and errors associated with manual versioning.

Inventive Principle:

Principle #26Copying

2Reliability

If changes are propagated throughout sequential flows by creating new flow versions, then the digital interfaces can function correctly, but the process becomes cumbersome and error-prone

Engineering Contradiction:

Improvecorrectness of digital interface functionVSAvoidease of propagation process

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system creates flow templates that serve as reusable copies. Modifications to the template automatically propagate to all flow instances, eliminating the need for manual updates to each version. This copying mechanism maintains correctness while dramatically improving ease of operation.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system enables self-service propagation where the flow template automatically updates its instances when modifications are made. The system serves itself by automatically detecting changes and propagating them throughout the flow hierarchy without requiring manual intervention, making the process both reliable and easy to operate.

Inventive Principle:

Principle #25Self-service

3Reliability

If new flow versions are created and deployed to production, then changes can be propagated, but computational resources are heavily consumed

Engineering Contradiction:

Improvepropagation of changesVSAvoidcomputational resource usage

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of creating and deploying multiple heavy flow versions, the system uses lightweight flow templates that can be copied and instantiated. Modifications to the template propagate efficiently to instances without requiring full version deployments, significantly reducing computational resource consumption while maintaining reliable change propagation.

Inventive Principle:

Principle #26Copying

4Reliability

If flow changes are propagated through versioning and deployment, then digital interfaces function correctly, but user experience deteriorates due to delays

Engineering Contradiction:

Improvefunctionality of digital interfaceVSAvoidspeed of implementation

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary structuring by creating flow templates that define the complete sequential flow configuration upfront. This allows for rapid propagation of changes to instances without requiring lengthy versioning and deployment cycles, improving productivity while maintaining functionality.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses flow templates as reusable copies that can be instantly instantiated and updated. Changes propagate quickly from the template to instances without the delays associated with traditional versioning and deployment processes, significantly improving implementation speed while ensuring digital interfaces remain functional.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11500859B2System and method for propagating modifications in flows

Publication Date: 2022.11.15 SALESFORCE INC

AI summary

Described herein is a system and method for propagating modifications in flows. In an embodiment, a central system activates a master process (e.g., master flow), including a sub-process (e.g., sub-flow) and a pre-programmed object (e.g., component). The master process is configured to execute a task using the sub-process and pre-programmed object. The central system initializes a variable corresponding to the master process. The central system further identifies a metadata object using the variable. The metadata object defines a runtime configuration of the master process and sub-process. The central system receives a modification to a setting of the metadata object and propagates the modification of setting in the metadata object to the master process and sub-process.