Conditional Child Node Creation via Ancestor Metadata Runtime Values

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current case management systems face challenges in efficiently managing complex data requirements and conditional node creation in business processes, often requiring custom code and not leveraging metadata runtime values effectively.

Innovation Solution

A system that conditionally creates child nodes based on ancestor node metadata runtime values, allowing end users to request node creation without the need for custom code, by identifying and evaluating metadata expressions within the case model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom code is used to create child nodes in case management systems, then flexibility and control are improved, but device complexity and development time increase

Engineering Contradiction:
ImproveflexibilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system enables end users to create child nodes by specifying ancestor node identifiers and metadata expressions without requiring custom code. The case management system automatically evaluates metadata runtime values and creates child nodes based on the expressions, making the system self-configuring and eliminating the need for developer intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Metadata expressions are defined in advance in the case model, specifying the conditions under which child nodes should be created. These expressions are evaluated at runtime against ancestor node metadata values, allowing the system to pre-configure the logic for node creation without requiring custom code during execution.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If custom code is written for node creation logic, then specific business requirements are met, but productivity and deployment time decrease

Engineering Contradiction:
ImprovecustomizationVSAvoidproductivity
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

End users directly configure child node creation logic through metadata expressions without requiring developer custom code. The system automatically handles expression evaluation and node creation, enabling business users to independently adapt the system to changing requirements and significantly improving deployment speed.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses metadata expressions that reference ancestor node metadata parameters to dynamically determine child node creation. By changing metadata values and expressions rather than code, the system adapts to different business requirements while maintaining high productivity and fast deployment.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If metadata runtime values are not leveraged, then system simplicity is maintained, but adaptability and responsiveness to business conditions decrease

Engineering Contradiction:
ImprovesimplicityVSAvoidadaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

Metadata expressions serve as an intermediary between ancestor node metadata runtime values and child node creation decisions. The expressions evaluate metadata values without requiring complex custom code, maintaining system simplicity while enabling the system to dynamically adapt to changing business conditions based on runtime data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10007683B1Conditional creation of child nodes based on ancestor node metadata runtime values
Publication Date: 2018.06.26 EMC IP HLDG CO LLC
  • US10007683B1 patent drawing
  • US10007683B1 patent drawing
  • US10007683B1 patent drawing

AI summary

Conditional creation of child nodes based on ancestor node metadata runtime values are described. A system receives, from an end user device, a runtime request to create an instance of a child node in a case model. The system identifies an instance of an ancestor node associated with the instance of the child node. The system identifies a runtime value of metadata associated with the instance of the ancestor node and corresponding to the instance of the child node. The system determines whether the runtime value of the metadata satisfies a condition. The system creates the instance of the child node in response to a determination that the runtime value of the metadata satisfies the condition. The system enables the end user device to access the created child node.