US2020272456A1PendingUtilityA1

Techniques and Architectures for Maintaining Metadata Version Controls

57
Assignee: SALESFORCECOM INCPriority: Mar 8, 2017Filed: Oct 28, 2019Published: Aug 27, 2020
Est. expiryMar 8, 2037(~10.7 yrs left)· nominal 20-yr term from priority
G06F 8/71G06F 8/53G06F 8/48
57
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Techniques and architectures for maintaining metadata version controls. A change to metadata within a computing environment is detected. Metadata subject to the change is decompiled into a source object that is in a format compatible with a version control system (VCS). The source object is stored in the VCS with relationship information to indicate a relationship to another source object, if the relationship is determined.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, are configurable to cause the one or more processors to:
 detect a change to metadata within a computing environment;   decompile, with one or more hardware computing components coupled with at least one physical memory device, metadata subject to the change into a source object that is in a format compatible with a version control system (VCS);   store the source object in the VCS with relationship information to indicate a relationship to another source object, if the relationship is determined.   
     
     
         2 . The non-transitory computer-readable medium of  claim 1  wherein the format comprises one of a text file, a XML-compatible file, a programming language file, an APEX code compatible file. 
     
     
         3 . The non-transitory computer-readable medium of  claim 1  further comprising instructions that, when executed by the one or more processors, are configurable to:
 compile, in response to a version change request, at least one source object stored in the VCS to metadata corresponding to a previous change; 
 deploy the metadata to an environment to restore metadata in the environment to a version prior to the previous change. 
 
     
     
         4 . The non-transitory computer-readable medium of  claim 3  wherein the compiling is performed in response to a database trigger. 
     
     
         5 . The non-transitory computer-readable medium of  claim 3  wherein the compiling is performed in response to a request from the computing environment. 
     
     
         6 . The non-transitory computer-readable medium  1  wherein the compiling is performed in response to a database trigger. 
     
     
         7 . The non-transitory computer-readable medium of  claim 6  wherein the trigger occurs in response to metadata file comparisons that are performed at pre-selected intervals. 
     
     
         8 . The non-transitory computer-readable medium of  claim 1  wherein the VCS provides relationship and dependency information in a storage structure to indicate relationships between decompiled files. 
     
     
         9 . The non-transitory computer-readable medium of  claim 1  wherein the VCS provides relationship and dependency information in versioning information to indicate relationships between decompiled files. 
     
     
         10 . A method comprising:
 detecting a change to metadata within a computing environment;   decompiling, with one or more hardware computing components coupled with at least one physical memory device, metadata subject to the change into a source object that is in a format compatible with a version control system (VCS);   storing the source object in the VCS with relationship information to indicate a relationship to another source object, if the relationship is determined.   
     
     
         11 . The method of  claim 10  wherein the format comprises one of a text file, a XML-compatible file, a programming language file, an APEX code compatible file. 
     
     
         12 . The method of  claim 10  further comprising:
 compiling, in response to a version change request, at least one source object stored in the VCS to metadata corresponding to a previous change; 
 deploying the metadata to an environment to restore metadata in the environment to a version prior to the previous change. 
 
     
     
         13 . The method of  claim 12  wherein the compiling is performed in response to a database trigger. 
     
     
         14 . The method of  claim 12  wherein the compiling is performed in response to a request from the computing environment. 
     
     
         15 . The method of  claim 10  wherein the compiling is performed in response to a database trigger. 
     
     
         16 . The method of  claim 15  wherein the trigger occurs in response to metadata file comparisons that are performed at pre-selected intervals. 
     
     
         17 . The method of  claim 10  wherein the VCS provides relationship and dependency information in a storage structure to indicate relationships between decompiled files. 
     
     
         18 . The method of  claim 10  wherein the VCS provides relationship and dependency information in versioning information to indicate relationships between decompiled files. 
     
     
         19 . A system comprising:
 a physical memory device;   one or more hardware processors coupled with the physical memory device, the one or more processors configurable to detect a change to metadata within a computing environment, to decompile, with one or more hardware computing components coupled with at least one physical memory device, metadata subject to the change into a source object that is in a format compatible with a version control system (VCS), and to store the source object in the VCS with relationship information to indicate a relationship to another source object, if the relationship is determined.   
     
     
         20 . The system of  claim 19  wherein the format comprises one of a text file, a XML-compatible file, a programming language file, an APEX code compatible file.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.