Metadata Change Undo via Version Control Source Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional techniques for managing metadata are complex and inefficient, particularly in complex computing environments, as they rely on change logs that require reapplying changes from a known starting point, leading to errors and inefficiencies.

Innovation Solution

The use of a version control system (VCS) to decompile metadata into a manageable format, allowing for the creation of source files that can be easily managed and coordinated, enabling efficient undoing of metadata changes by compiling these source files to achieve desired versions without rolling back and reapplying changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional change log techniques are used to manage metadata, then changes can be tracked, but the management process becomes complex and inefficient requiring reapplication of changes from a known starting point

Engineering Contradiction:
Improvemetadata change trackingVSAvoidmanagement process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates source files that are copies or representations of the metadata state at specific points in time. These source files serve as manageable replicas that can be stored in version control systems, allowing users to undo changes by restoring to previous versions without complex reapplication processes. The source files capture the essential metadata state while being simpler to manage than full metadata instances.

Inventive Principle:
Principle #26Copying

2Loss of information

If change logs are used to manage metadata, then change history is maintained, but the process requires reapplying changes which leads to errors and inefficiencies

Engineering Contradiction:
Improvechange history preservationVSAvoidmetadata management efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent performs preliminary actions by creating and storing source files that represent metadata states before changes are applied. These source files are prepared in advance and stored in version control systems, so when undo operations are needed, the system can directly restore from these pre-prepared sources rather than reapplying changes from scratch. This eliminates the time-consuming and error-prone reapplication process while preserving complete change history.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If traditional metadata management is used, then metadata can be stored and communicated, but version control and rollback capabilities are lacking

Engineering Contradiction:
Improveversion control capabilityVSAvoidrollback operation simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces source files as an intermediary layer between the metadata system and version control mechanisms. These source files serve as a bridge that translates metadata states into a format suitable for version control systems. By using this intermediary representation, the system gains full version control capabilities including branching, merging, and rollback functions, while maintaining ease of operation through familiar version control interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10963444B2Techniques and architectures for providing functionality to undo a metadata change
Publication Date: 2021.03.30 SALESFORCE INC
  • US10963444B2 patent drawing
  • US10963444B2 patent drawing
  • US10963444B2 patent drawing

AI summary

Techniques and mechanisms for providing a functionality which is selectable to undo one or more changes to metadata in a computing environment. In an embodiment, one or more source objects, stored by a version control system (VCS), represent one or more previous metadata changes. In response to a detection of the one or more metadata changes, an element of a user interface is configured to be selectable for undoing the one or more metadata changes. In another embodiment, a subsequent selection of the element invokes a retrieval of the one or more source objects from the VCS. Based on the retrieval of the one or more source objects from the VCS, a compilation is performed to generate a program which is executed to undo the one or more metadata changes.