| Workflow data binding -> Monitor Keywords |
|
|
  Workflow data bindingUSPTO Application #: 20070276689Title: Workflow data binding Abstract: A workflow data binding system facilitates binding of a data component to a feature of a software component. Prior to the binding, a graphical indication of the software component and a graphical indication of the feature of the software component are displayed. In addition, an indication of an element of the data component is displayed in a display area approximately adjacent to the displayed software component. The workflow data binding system receives a user input command to bind the data component to the feature of the software component. The user input command may include dragging the indication of an element of the data component from the data component display area to the feature of the software component and subsequently dropping it on the feature. As a result, the workflow data binding system automatically generates script or code that provides executable instructions to bind the feature of the software component to the data component. (end of abstract) Agent: Perkins Coie LLP Patent-sea - Seattle, WA, US Inventors: Kirk Slone, Daren Yong, Eric Jobin USPTO Applicaton #: 20070276689 - Class: 705001000 (USPTO) Related Patent Categories: Data Processing: Financial, Business Practice, Management, Or Cost/price Determination, Automated Electrical Financial Or Business Practice Or Management Arrangement The Patent Description & Claims data below is from USPTO Patent Application 20070276689. Brief Patent Description - Full Patent Description - Patent Application Claims
CROSS-REFERENCE TO RELATED APPLICATION(S) [0001] This patent application claims the benefit of commonly owned U.S. Provisional Patent Application Ser. No. 60/800,056, filed on May 12, 2006, entitled "Data Binding For Workflow," which is incorporated herein in its entirety by reference. This patent application also incorporates by reference the following commonly owned patent applications: U.S. Provisional Patent Application Ser. No. 60/532,776, filed Dec. 24, 2003, Canadian Patent Application No. 2,443,454, entitled "Data Binding Method in Workflow System," filed Sep. 11, 2003, and U.S. patent application Ser. No. 10/938,118, entitled "User-Friendly Data Binding, Such As Drag-And-Drop Data Binding In A Workflow Application," filed on Sep. 10, 2004. BACKGROUND [0002] In the context of applications software development, the practice of data binding addresses the common need for an application to access data stored in an independent data source. Generally, data binding involves retrieving data from a data source and subsequently facilitating the use of the retrieved data. In a more specific example, data binding allows a mapping from data (e.g., XML (Extensible Markup Language) data or database data) to a class or other programming structure associated with the application (e.g., a Person class, a Product class, a Meeting class, etc.). In another example, data binding may be used to retrieve data for use in setting up a software component, such as a "web control" (e.g., list box, drop-down list, etc.) that encapsulates a user interface and other related functionality. After the programmer specifies the data source to be bound (e.g., a data set containing a list of names), a data binding method or function is called, which fills the control with the data (e.g., the names from the list). [0003] Because it provides access to external data, data binding is considered a useful technique. In addition, it also provides some level of protection and integrity for the body of data being accessed. However, traditional data binding techniques have proven awkward and difficult for programmers to control and implement. [0004] Improvements in data binding techniques continue to be made based on specially configured application programming interfaces (APIs) and other tools. Despite these improvements, data binding still proves to be a bottleneck for more rapid application development, especially for beginner programmers who are not comfortable writing the script or code needed to implement data binding. [0005] In a workflow application, "forms" can be used to collect or provide information. So that software developers do not need to write extensive code to provide information in a form or collect user input from a form, the software developers can employ data binding techniques to connect data sources (in the form of XML files or objects) to a workflow form. However, current programming environments (e.g., Microsoft Visual Studio 2005.RTM. or Microsoft .NET.RTM. 2.0 do not provide methods to permit direct binding of data objects to Microsoft Windows.RTM. forms or web forms. BRIEF DESCRIPTION OF THE DRAWINGS [0006] FIG. 1 is a block diagram showing an example of an environment for creating and using custom components under one embodiment of the workflow data binding system. [0007] FIG. 2A is a display diagram showing a design view in the integrated development environment of FIG. 1. [0008] FIG. 2B is a display diagram showing an object tree view in the integrated development environment of FIG. 1. [0009] FIG. 3 is a display diagram showing an unbound web form and associated controls. [0010] FIG. 4 is a display diagram showing an unbound form and associated controls. [0011] FIG. 5 is a display diagram showing data binding performed by dragging and dropping XML data onto a web form. [0012] FIG. 6 is a display diagram showing data binding performed by dragging and dropping XML data onto a form. [0013] FIG. 7 is a display diagram showing data binding performed by dragging and dropping database data onto a web form. [0014] FIG. 8 is a display diagram showing data binding performed by dragging and dropping database data onto a form. [0015] FIG. 9 is a flow diagram showing a routine for automatically generating script or code for data binding. [0016] FIG. 10 is a display diagram showing a design view of the integrated development environment. [0017] FIG. 11 is a block diagram showing class binding in the integrated development environment. [0018] FIG. 12 is a sequence diagram showing a data binding sequence. [0019] FIG. 13 is a flow diagram illustrating a data binding process and data flow. [0020] The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed workflow data binding system. [0021] In the drawings, the same reference numbers and acronyms identify elements or acts with the same or similar functionality for ease of understanding and convenience. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the Figure number in which that element is first introduced (e.g., element 204 is first introduced and discussed with respect to FIG. 2). Continue reading... Full patent description for Workflow data binding Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Workflow data binding patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Workflow data binding or other areas of interest. ### Previous Patent Application: Techniques for processing recyclable containers Next Patent Application: Electronic healthcare information management for on-demand healthcare Industry Class: Data processing: financial, business practice, management, or cost/price determination ### FreshPatents.com Support Thank you for viewing the Workflow data binding patent info. IP-related news and info Results in 1.50879 seconds Other interesting Feshpatents.com categories: Electronics: Semiconductor , Audio , Illumination , Connectors , Crypto , |
||
