Enterprise System Object Generation via Template Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for generating enterprise system objects, such as workflow, report, interface, conversion, enhancement, and forms (WRICEF) objects, are time-consuming, manpower-intensive, and result in customized objects that cannot be shared or continuously tested, leading to wastage of human and computing resources.
Innovation Solution
A generation system that receives user request data, maps technical object content data to pre-defined interface format data based on business rules, and generates enterprise system objects, either using existing mappings or creation data from users, to quickly and automatically produce scalable and shareable objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual methods are used to generate enterprise system objects, then customization flexibility is maintained, but time consumption and manpower requirements increase significantly
Solution Approach 1:
The patent uses templates as reusable copies of enterprise system object structures. These templates define standard patterns for workflows, reports, interfaces, conversions, enhancements, and forms. By copying and adapting template structures rather than creating objects from scratch, the system maintains customization flexibility while dramatically reducing generation time and manual effort.
Solution Approach 2:
The patent performs preliminary actions by pre-defining object structures, validation rules, and configuration patterns in templates before actual object generation. Business rules and data mappings are established in advance within the templates, so that when objects are generated, the heavy lifting of structural design and validation logic has already been completed, enabling rapid customization.
2Ease of operation
If customized enterprise system objects are generated manually, then specific user requirements are met, but resource wastage occurs due to inability to share and reuse objects
Solution Approach 1:
The patent makes enterprise system objects universal by enabling their sharing across multiple users and projects through version control and repository management. Objects generated using templates can be stored, retrieved, and reused by different users for different purposes, transforming previously single-use customized objects into multi-functional reusable assets that reduce resource wastage.
Solution Approach 2:
The patent merges individual user customizations into shared repository objects. When a user generates or modifies an object, changes can be consolidated and merged with existing template versions or other users' objects, creating a unified knowledge base of reusable components that benefits the entire organization rather than remaining isolated in individual workspaces.
3Ease of manufacture
If traditional generation methods are used, then object creation is possible, but continuous testing and validation become cumbersome and time-intensive
Solution Approach 1:
The patent implements automated feedback mechanisms through validation rules defined in templates and continuous testing capabilities. When objects are generated or modified, the system automatically validates them against predefined business rules and data mappings, providing immediate feedback on compliance and correctness. This eliminates manual testing cycles and enables continuous validation without significant time overhead.
4Device complexity
If manual enterprise system object generation is performed, then control over object details is maintained, but scalability of the generation process is limited
Solution Approach 1:
The patent segments the enterprise system object generation process into distinct, manageable components: templates define structural patterns, business rules define validation logic, data mappings define transformation relationships, and version control manages object evolution. This segmentation allows each component to be independently configured and controlled while enabling the overall process to scale efficiently across multiple users and objects.
Data Source
AI summary
In some implementations, a device may receive user request data from a user device associated with a user. The device may retrieve pre-defined technical object content data from an enterprise system. The device may retrieve pre-defined interface format data and a pre-defined business rule from a first data structure and a second data structure, respectively, based on the user request data. The device may determine whether a mapping, for generating an enterprise system object, is stored in a third data structure. The device may map the technical object content data to the pre-defined interface format data, based on the mapping and the pre-defined business rule, to generate mapped data when the mapping is stored in a third data structure. The device may generate the enterprise system object based on the mapped data. The device may perform one or more actions based on the enterprise system object.