Versioned Script Management System for Cloud Platform Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cloud computing, managing script versions is challenging as updates can introduce regressions in client instances that rely on specific script behaviors, and modifying scripts to fix issues can lead to unintended changes that revert with platform updates.

Innovation Solution

A versioned script management system that tracks version information for each script, allowing for platform release updates without overwriting client-modified versions, and enables clients to manage script versions independently, ensuring consistent behavior across updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If platform release updates are deployed to modify script instructions, then script performance and logical errors are improved, but regressions are introduced in client instance objects that rely on the original script behavior

Engineering Contradiction:

Improvescript correctnessVSAvoidbehavior compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments script management into multiple independent versions, where each script can have its own version history. This allows the system to maintain both the original script version (for compatibility) and the updated script version (for correctness), enabling selective application of fixes without forcing all clients to adopt potentially breaking changes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary version tracking and compatibility assessment before deploying updates. By maintaining version metadata and assessing compatibility impacts beforehand, the system can prepare rollback mechanisms and compatibility layers in advance, preventing regressions from occurring in the first place.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If scripts are modified to change behavior for specific clients, then client-specific requirements are met, but subsequent platform updates overwrite the modified scripts, reverting to original behavior

Engineering Contradiction:

Improveclient-specific behaviorVSAvoidscript version persistence

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent applies local quality by allowing different versions of the same script to coexist for different client instances. Each client can have its own customized script version with specific behavioral modifications, while other clients continue using the standard platform version. This localized versioning preserves client-specific adaptations without being overwritten by global updates.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent creates and maintains copies of script versions. When a client modifies a script, the system creates a preserved copy of that modified version. During platform updates, the system can selectively apply updates to non-modified scripts while preserving copies of client-modified scripts, ensuring that local adaptations persist across platform evolution.

Inventive Principle:

Principle #26Copying

3Productivity

If platform releases frequently update scripts, then platform functionality and bug fixes are improved, but client instances experience regressions and instability

Engineering Contradiction:

Improveplatform evolution speedVSAvoidclient instance stability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements dynamic version management where the system adaptively determines which script versions to apply to which clients based on compatibility assessments. Rather than forcing uniform updates across all clients, the system dynamically selects appropriate versions, allowing rapid platform evolution for some clients while maintaining stability for others who are still on previous versions or have custom modifications.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent prepares cushioning mechanisms in advance by maintaining version history and rollback capabilities. Before deploying potentially destabilizing updates, the system preserves previous working versions and assesses compatibility risks. If regressions are detected or predicted, the system can automatically revert to previous stable versions, cushioning clients from the full impact of rapid platform changes.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11474845B2System and method for versioned script management

Publication Date: 2022.10.18 SERVICENOW INC

AI summary

This disclosure is directed to a versioned script management (VSM) system that enables a client instance to implement versioned script management. A versioned scripts table includes one or more fields storing version information for each script. The version information tracks platform release information (e.g., family, patch, and/or hotfix release version information) of each script, while also tracking client-specific versions of these scripts that have been modified after release. The VSM system includes instructions to create a modified version of an existing script and to perform a platform release update of platform scripts without overwriting or changing the behavior of client-modified versions of these scripts. As such, the VSM system enables script modifications, as part of client customization and/or platform updates, while avoiding the possibility of introducing regressions as a result of these modifications.