Inserting Custom Activities in Orchestrated Application Suites
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application suites lack the capability to incorporate custom activities within their orchestrated processing flows, limiting their flexibility and functionality.
Innovation Solution
The solution involves identifying an element of interest in a base suite, determining its scope, and inserting a custom activity after the end of that scope to create a deployment suite, where the custom activity is executed between applications in the processing flow, enhancing the suite's functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom activities are inserted into an orchestrated application suite, then the functionality and adaptability of the suite are improved, but the device complexity increases
Solution Approach 1:
The patent segments the application suite into a base suite (containing core orchestrated applications) and customizable components (custom activities). This segmentation allows the base suite to remain simple and stable while enabling functionality extension through modular custom activities that can be inserted at specific points without altering the core structure.
Solution Approach 2:
The patent extracts the customization capability from the core application suite by separating custom activities as distinct, removable components. This extraction allows users to add or remove custom activities independently, improving adaptability without permanently increasing the complexity of the base orchestrated suite.
2Adaptability or versatility
If custom activities are inserted into an orchestrated application suite, then the adaptability of the suite is improved, but the scope of elements to track increases
Solution Approach 1:
The patent introduces an intermediary mechanism (the scope determination module) that automatically identifies and tracks the boundaries of elements affected by custom activities. This intermediary manages the scope tracking automatically, allowing adaptability to improve while preventing manual scope management complexity from increasing proportionally.
3Adaptability or versatility
If custom activities are inserted after determining the scope of an element, then the processing flow becomes more tailored, but the loss of time for scope determination occurs
Solution Approach 1:
The patent performs preliminary scope determination before inserting custom activities, but optimizes this process by using automated analysis of the processing flow to quickly identify element boundaries. This preliminary action enables tailored processing flows while minimizing time loss through efficient automated scope identification rather than manual analysis.
Data Source
AI summary
An aspect of the present disclosure provides for inserting custom activities in orchestrated application suites. In an embodiment, an element of interest is first identified in a base suite. The scope of the element of interest in the base suite is then determined. A custom activity is inserted after an end of the scope of the element of interest to form a deployment suite corresponding to the base suite. According to another aspect, the base suite comprises a set of applications, wherein the end of scope of the element is determined to be in a first application of the set of applications, wherein a second application of the set of application immediately follows the first application in a processing flow of the base suite. The custom module is placed between the first application and the second application, wherein the custom module when executed performs the custom activity.