Link Constraint Module for SharePoint List Modification Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In SharePoint systems, users with permission to modify lists often make changes that can harm multiple components accessing those lists, leading to operational issues and decreased productivity due to the lack of awareness about which fields are used by these components.

Innovation Solution

A smart linker module generates link constraint data to track which components access specific list fields and sends alerts to authorized users when modifications are attempted, preventing harmful changes by warning them of potential impacts and restricting unauthorized modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If permission control is given to list creators and site owners to modify lists, then ease of operation is improved, but reliability deteriorates due to harmful changes affecting multiple components

Engineering Contradiction:
Improvepermission controlVSAvoidsystem stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically detecting which list fields are being accessed by SharePoint components before allowing modifications. This advance detection enables the system to warn users about potential impacts before they make harmful changes, thus maintaining both ease of operation and system reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by notifying list creators and site owners about the components that will be affected by their intended modifications. This feedback loop allows users to make informed decisions about whether to proceed with changes, balancing operational freedom with system stability

Inventive Principle:
Principle #23Feedback

2Reliability

If manual permission control is implemented to prevent harmful changes, then reliability is improved, but device complexity increases due to manual tracking requirements

Engineering Contradiction:
Improvemodification safetyVSAvoidpermission control system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system employs self-service by automatically detecting and tracking which SharePoint components access which list fields without requiring manual intervention. This automation eliminates the need for complex manual permission management while maintaining high reliability in preventing harmful changes

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary mechanism that automatically monitors and tracks the relationships between list fields and consuming components. This intermediary layer handles the complexity of tracking dependencies, simplifying the overall system while ensuring reliable modification control

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If users are restricted from modifying lists, then reliability is improved, but ease of operation deteriorates due to limited modification capability

Engineering Contradiction:
Improvesystem stabilityVSAvoidmodification capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies dynamics by making permission control adaptive rather than static. Users can modify lists when no components are affected, but the system dynamically restricts or warns them when components depend on the fields being modified. This dynamic approach maintains both reliability and operational flexibility

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10628602B2Controlling content modifications by enforcing one or more constraint links
Publication Date: 2020.04.21 QUEST SOFTWARE INC
  • US10628602B2 patent drawing
  • US10628602B2 patent drawing
  • US10628602B2 patent drawing

AI summary

Embodiments of the present disclosure include systems and methods for controlling modification of a data file that is accessed by multiple components of an application platform. The method for controlling modification of a data file includes: preparing a link constraint data that includes information of a data file and a component of an application platform, the component being associated with the data file; preparing an alert data that includes information of the data file and a person having a permission to modify the data file; responsive to an attempt of a user to modify the data file, retrieving the information of the component from the link constraint data and the information of the person from the alert data; and sending a notice of the attempt to at least one of the person and the user.