Approaches to Improved Workflow Orchestration
Publication Date: 2016-Jul-27
The IP.com Prior Art Database
An approach to improving the way software works together through if-then workflows.
Page 01 of 11
APPROACHES FOR IMPROVED WORKFLOW ORCHESTRATION
The following detailed description refers to the accompanying drawings. Wherever convenient, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several embodiments and features of the present disclosure are described herein, modifications, adaptations, and other implementations are possible, without departing from the spirit and scope of the present disclosure.
In general, embodiments of the present disclosure may provide systems, methods, and computer-readable media for improved workflow and interoperability. The disclosed approach may facilitate workflow automation across software products. This may allow tighter integration of software products. The automation may provide a way to keep data and models and synch, utilize workflows across applications, and integrate and automate reporting across software products.
In one embodiment, the approach is realized as an application for designing other software applications (such as desktop applications, mobile applications, etc.) that modularizes workflows. The approach may modularize workflows rather than inextricably tying the workflows to a single data model, app shell, execution context, etc.
In one embodiment, an application runs in the background (potentially on a server or in the cloud) that hosts integration components supporting interoperability. In one embodiment, the service contains: data model mappings that support data transfer between target application workflows; recipes that define simple automation workflows; shared services (such as logging, connection services, units management, etc.); and a security module that validates access to the APIs embedded in the applications, to prevent unwanted integration with the system by third parties.
A user interface may be provided that makes clear to the user what integration features are available based on their software environment. In one example, this component may determine what software the user has installed and limit exposure of integration features to those compatible with the user's installations.
Figure 1 illustrates one embodiment of an approach to orchestration. An orchestration engine may provide a recipe library, a connector library, a shared utilities component, and a
Page 02 of 11
securities component. The recipe library may indicate what steps the user can automate. The connector library may specify indicate how to translate data and workflow state from one application to another. The shared utilities component may handle units management, reporting, systems diagnostics, and other shared services and functions. The security module may ensure that the APIs and exposure are limited to prevent non-security or unauthorized interaction.
The solution may facilitate sharing underlying data items between applicati...