Routing Framework for Business Object Attachments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack control over the storage location of business object attachments, which are typically stored in a content repository rather than with the business object, leading to arbitrary placement by the content management system, which may not be desirable.
Innovation Solution
A routing framework that uses business object identifiers and type identifiers to define routing attribute fields, calculating a target content repository and path for attachments, allowing specific and rule-based storage within a content management system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the content management system arbitrarily determines where to store an attachment, then the content management system has flexibility in storage management, but the business object loses control over the storage location of its attachments
Solution Approach 1:
The patent introduces a routing framework as an intermediary layer between the business object repository and content management system. This routing framework evaluates routing rules and determines the target content repository and path for attachments, thereby giving business objects control over storage locations without requiring the content management system itself to be complex. The routing framework acts as a mediator that translates business object requirements into storage decisions.
2Productivity
If attachments are stored in a centralized content repository, then storage management is simplified, but retrieval efficiency decreases due to the need to search across multiple repositories
Solution Approach 1:
The patent implements local quality by allowing different content repositories to be optimized for specific business object types or departments. Instead of a single centralized repository, the system creates multiple specialized repositories where attachments are stored based on their association with specific business objects. This enables faster retrieval by directing searches to relevant repositories rather than searching across all repositories, while maintaining organized structure through routing rules.
3Reliability
If attachments are stored with the business object in the business object repository, then data integrity is improved, but storage scalability is reduced
Solution Approach 1:
The patent segments the storage system into two parts: the business object repository stores metadata and references to attachments, while the content management system stores the actual attachment files in specialized content repositories. This segmentation maintains data integrity by keeping the business object reference intact while allowing the attachment storage to scale independently. The routing framework ensures that attachments remain associated with their business objects through structured path naming conventions.
Data Source
AI summary
Particular embodiments store a business object attachment in a specific storage location associated with a business object. In this embodiment a computer receives an attachment for the business object along with information regarding the business object. The information regarding the business object may include a business object identifier and a business object type identifier. With this information, the computer defines routing attribute fields for the attachment. Using the routing attribute fields and the business object type identifier, the computer calculates a target content repository and a target path for the attachment. The computer then determines which content management system contains the target repository and interfaces with that target content management system to direct that content management system to store the attachment in the target repository at the target path.