Dynamic XPS Filter Orchestrator for Workflow Adaptability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The XPS print path system lacks dynamic reconfiguration capabilities, sophisticated filter execution, and parallel processing, making it inadequate for advanced workflow management despite its widespread availability on operating systems.
Innovation Solution
A system and method that allow filters with policy rules and triggering conditions to be stored in a repository independent of the default workflow path, with an orchestrator executing these filters during processing, enabling conditional and parallel execution, and dynamic updating of filters without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the XPS print path system uses a statically configured set of dynamic libraries, then the system is readily available on widely distributed operating systems, but the system cannot easily be reconfigured dynamically and lacks sophisticated filter execution capabilities
Solution Approach 1:
The system segments filter configuration into two independent parts: a static default workflow path (XPS print path) and a dynamic repository of additional filters. The orchestrator acts as a mediator that combines these segments, allowing dynamic filter selection without modifying the core static structure. This enables adaptability while preserving system stability.
Solution Approach 2:
The orchestrator serves as an intermediary component between the static XPS print path and the dynamic filter repository. It evaluates triggering conditions, selects appropriate filters from the repository, and integrates them into the workflow path dynamically. This intermediary enables sophisticated filter execution without requiring changes to the underlying static system architecture.
2Productivity
If the XPS print path system processes documents sequentially through fixed libraries, then the system structure remains simple, but the system lacks parallel processing capabilities and sophisticated filter execution
Solution Approach 1:
The filter execution mechanism transitions from static sequential processing to dynamic parallel processing. The orchestrator evaluates triggering conditions for multiple filters simultaneously and executes triggered filters in parallel, while maintaining the ability to process filters sequentially when appropriate. This dynamic approach enables both parallel and sequential processing modes based on filter requirements.
3Adaptability or versatility
If filters are configured in the default workflow path, then the configuration is integrated into the system, but the system cannot be reconfigured dynamically without manual intervention
Solution Approach 1:
The system implements self-service through automatic filter configuration and updating. The orchestrator automatically evaluates triggering conditions and selects appropriate filters from the repository based on document properties and workflow requirements. Filter configurations can be updated dynamically in the repository without requiring manual intervention to reconfigure the entire system, enabling the system to serve itself with appropriate filters.
Solution Approach 2:
Filters are pre-configured in the repository with their triggering conditions and parameters defined in advance. This preliminary configuration allows the orchestrator to quickly select and apply appropriate filters during document processing without requiring real-time configuration decisions or manual setup during operation.
Data Source
AI summary
A system and method enhances a default workflow path of a workflow system. The system provides access to policy rules and associated triggering conditions not available to the default workflow path of the workflow system. The configured rules are stored in a repository, and may be dynamically reconfigurable. Selected ones of the rules and triggering conditions are bound to at least one resource, such as a printer. An orchestrator is installed as a default workflow path, e.g., as an XPS filter, and is thus executed during default workflow path processing for a job submitted to the default workflow path. The orchestrator may then perform additional processing functions including accessing the configured policy rules and associated triggering conditions. A processing unit may be executed if the associated triggering condition is satisfied.