E-form Data Translation Layer for BPM Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business Process Model Engines face challenges in interacting with electronic forms due to the need for deep knowledge of e-form internal structures and vendor-specific APIs, leading to manual extraction and translation complexities, which restrict automation and increase resource usage.
Innovation Solution
A method and system for transparently composing and decomposing electronic form data into a format usable by Business Process Model Engines, eliminating the need for manual steps and vendor-specific APIs by using predefined rules to extract and convert e-form structure and layout information into a BPM-Engine understandable format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual extraction and translation methods are used to convert e-form data into BPM Engine format, then data can be processed by the BPM Engine, but the process requires deep knowledge of e-form structures and vendor-specific APIs, increasing operational complexity and resource usage
Solution Approach 1:
The patent introduces an intermediary translation layer that automatically converts e-form data into BPM Engine format. This intermediary system handles the complexity of vendor-specific APIs and e-form structures, allowing the BPM Engine to process data without directly interacting with the complex e-form formats. The translation layer acts as a mediator that simplifies the interface between diverse e-form sources and the BPM Engine.
Solution Approach 2:
The system enables self-service by allowing e-form data to be automatically translated and processed without requiring manual intervention or deep knowledge of e-form structures. The translation mechanism autonomously handles the conversion process, extracting necessary information from various e-form formats and presenting it in a standardized format that the BPM Engine can immediately process.
2Ease of operation
If e-form specific controls and APIs are used to extract data, then programmatic interaction with e-form data is achieved, but vendor-specific API knowledge is still required, limiting ease of operation
Solution Approach 1:
The patent implements a universal translation layer that can handle multiple vendor-specific e-form formats through a single interface. This universal system translates data from various e-form vendors (Adobe LiveCycle, Microsoft InfoPath, etc.) into a standardized BPM Engine format, eliminating the need for separate vendor-specific API knowledge. The translation mechanism is designed to be vendor-agnostic, supporting multiple formats through a unified approach.
3Reliability
If e-form data is stored directly in internal systems, then regulatory requirements are satisfied, but the BPM Engine cannot interact with the contents or data of those documents
Solution Approach 1:
The patent segments the handling of e-form data into two distinct pathways: one for storage and one for processing. E-form documents are stored in their original format to satisfy regulatory requirements, while simultaneously a translated version is generated for BPM Engine processing. This segmentation allows the system to maintain compliance while enabling full programmatic interaction with the data contents through the translation layer.
Data Source
AI summary
Certain example embodiments described herein relate to techniques for enabling a business process model (BPM) to be transparent (in whole or in part) from the source of data that triggers it. More particularly, certain example embodiments relate to techniques enabling transparent composition and decomposition of e-form data from one or more e-form formats into data that is directly usable by a Business Process Model Engine. Information from an e-form may, for example, be used in a business process, e.g., after a template or document type is created that represents the e-form in a format that the BPM Engine understands, and the e-form may be transparently composed into and decomposed out from the business data in certain example embodiments.