Workflow Expansion Program for MFP License Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional license management systems struggle to manage workflows as data files, making it difficult to provide them as expansion programs with menu display and license management capabilities similar to traditional applications on multi-function peripherals (MFPs).
Innovation Solution
The solution involves configuring a workflow as a 'flow bundle' that includes a definition file, manifest file, and icon images, allowing it to be installed and displayed on the MFP's main menu like an expansion program, using the OSGi framework, which enables registration and license management of workflows as independent applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If workflow is provided as data file (XML), then workflow definition flexibility is improved, but license management capability deteriorates
Solution Approach 1:
The workflow system is segmented into two distinct components: workflow definition files (XML data) and executable flow applications. The flow application acts as a container that encapsulates the workflow definition file, manifest file, and icon image, enabling the workflow to be managed as a unified expandable program unit that supports license management while preserving XML-based definition flexibility.
Solution Approach 2:
The flow application serves as an intermediary layer between the workflow definition file and the license management system. It packages the workflow definition file along with a manifest file containing license information and an icon image, creating an expandable program structure that enables license management without compromising the underlying XML-based workflow definition flexibility.
2Ease of manufacture
If workflow is provided as data file, then ease of modification is improved, but menu display capability deteriorates
Solution Approach 1:
The system separates the workflow definition (XML data maintaining ease of modification) from the presentation layer (icon image and manifest file). The flow application packages these components together, enabling the workflow to be displayed on the main menu with an icon while preserving the XML-based definition that can be easily modified.
Solution Approach 2:
The manifest file acts as an intermediary that bridges the workflow definition file and the menu display system. It contains metadata including icon image information and workflow identification, enabling the workflow to be displayed on the main menu while the underlying XML definition remains editable and modifiable.
3Reliability
If workflow is treated as independent application, then license management is improved, but device complexity increases
Solution Approach 1:
The flow application framework provides universal functionality for managing workflows as expandable programs. It handles license verification, menu display, and execution for all workflow types through a standardized structure containing manifest files, icon images, and workflow definition files, reducing the need for separate management mechanisms for different workflow types.
Solution Approach 2:
The workflow definition file is nested within the flow application structure, which also contains the manifest file and icon image. This nested structure allows the workflow to be managed as a unified expandable program while maintaining the hierarchical organization that simplifies system management and reduces overall device complexity.
4Ease of operation
If workflow is displayed on main menu, then user accessibility is improved, but system complexity increases
Solution Approach 1:
The manifest file serves as an intermediary that provides the flow application with menu display information including icon images and workflow identification. This standardized manifest structure enables automatic registration and display on the main menu without requiring complex custom registration mechanisms for each workflow.
Solution Approach 2:
The flow application framework provides a universal registration mechanism that handles menu display for all workflows through a standardized process. The system automatically registers flow applications based on their manifest files, enabling consistent menu display across different workflow types without increasing system complexity.
Data Source
AI summary
A flow application receives an event generated by an MFP. If a type of data relating to the event is an expansion program including a definition file, and if an event type is installation, the flow application registers an object associated with the definition file included in the expansion program according to installation of the expansion program.