Virtual forms

• US 7,757,177 B1
• Filed: 03/21/2006
• Issued: 07/13/2010
• Est. Priority Date: 03/21/2006
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Bohm, Matthew B., McClanahan, Craig R.
• Primary Examiner(s): Huynh; Ba
• Assistant Examiner(s): Iturralde; Enrique W
• Application Number:
  US11/385,519
• Time in Patent Office: 1,575 Days
• Field of Search: 715/221, 715/760, 715/762, 715780-782, 715/821
• US Class Current: 715/760
• CPC Class Codes: G06F 40/174 Form filling; Merging

Abstract

A technology enabling a developer to configure a graphical user interface (GUI) such that only a subset of the inputs contained in the GUI will be processed, depending on the user'"'"'s interaction with the GUI. The configuration identifies one or more logical units known as virtual forms, with each virtual form identifying zero or more input components from the GUI that are said to participate in the virtual form, and one or more submission components from the GUI that are said to submit the virtual form, such that when a user interacts in some particular way with (e.g., clicks) a component that submits a virtual form, only the inputs that participate in that virtual form are processed while other inputs in the GUI are not processed.

Claims

1. A method for an input processing framework system to conditionally process a subset of values available to the system depending on an object initiating processing, the method comprising:

providing virtual form configuration metadata about an overall set of objects, where each object in the overall set can be a value holder, an initiator, or both a value holder and an initiator, the value holder holding a value that can be processed by the system, the initiator triggering the processing;

wherein the metadata comprises a plurality of virtual forms, with each virtual form optionally identifying a name, and with each virtual form identifying zero or more of the value holders from the overall set as participants in that virtual form, and with each virtual form identifying one or more initiators from the overall set as submitters of that virtual form, such that each value holder from the overall set can be identified as a participant in zero or more virtual forms, and such that each initiator from the overall set can be identified as a submitter of zero or one virtual form, and each value holder from the overall set can be identified as a participant in two or more virtual forms,

such that when an initiator that is identified as a submitter of a virtual form triggers processing by the system, the system processes only the values held by the value holders that are identified as participants in that virtual form, and the system does not process the values held by value holders that are not identified as participants in that virtual form, and,

wherein processing includes the input processing framework system itself performing operations on the held values, the operating including

performing all configured conversions on the held values,

invoking all configured validation checks on the held values,

evaluating all bindings configured on the value holders holding the held values,

and storing each held value in a location determined by the evaluating; and

displaying, on a display, two or more virtual forms at the same time.

2. The method of claim 1 wherein:

an object in the overall set that is both a value holder and an initiator and that is identified as a participant in one or more virtual forms can simultaneously be identified as a submitter of one of those virtual forms or a different virtual form.

3. The method of claim 1 wherein:

when an initiator that is identified as a submitter of a virtual form triggers processing by the system, the implementation of the input processing framework system is able conditionally either to retain or discard the unprocessed value of each value holder that does not participate in that virtual form, wherein some such implementations of the input processing framework system expose an API that can be used to establish whether each such value holder retains or discards its unprocessed value at a particular point in time.

4. The method of claim 1 wherein:

the objects in the overall set are visual or non-visual user interface (UI) components that operate within the input processing framework system;

the input processing framework system is capable of being used by software applications that present a UI, such as web applications or rich client UI applications;

the value holder objects are input components, an input component being any component capable of accepting input,

the initiator components are submission components, a submission component being any component capable of initiating processing, such as, in the case of a web application, any button, link, or component configured with client-side scripting that causes a request to be made to the server application that uses an input processing framework.

5. The method of claim 4 wherein:

the method places no topographical limitations on where the user interface (UI) components can be positioned within the user interface, even a user interface that does not use CSS (cascading style sheets) positioning or a similar technology for the positioning of user interface (UI) components.

6. The method of claim 4 wherein:

when an initiator that is embedded within a row of a table component and that is identified as a submitter of a virtual form triggers processing by the system, some implementations of the input processing framework system impose an additional limitation on which values are processed, the limitation being that such implementations do not process the values held by value holders that appear in rows of the table other than that row.

7. A computer-readable storage medium having information stored thereon for directing a processor to conditionally process a subset of values available to an input processing framework system depending on an object initiating processing, the information comprising:

instructions for providing virtual form configuration metadata about an overall set of objects, where each object in the overall set can be a value holder, an initiator, or both a value holder and an initiator, the value holder holding a value that can be processed by the system, the initiator triggering the processing;

wherein the metadata comprises a plurality of virtual forms, with each virtual form optionally identifying a name, and with each virtual form identifying zero or more of the value holders from the overall set as participants in that virtual form, and with each virtual form identifying one or more initiators from the overall set as submitters of that virtual form, such that each value holder from the overall set can be identified as a participant in zero or more virtual forms, and such that each initiator from the overall set can be identified as a submitter of zero or one virtual form, and each value holder from the overall set can be identified as a participant in two or more virtual forms,

such that when an initiator that is identified as a submitter of a virtual form triggers processing by the system, the system processes only the values held by the value holders that are identified as participants in that virtual form, and the system does not process the values held by value holders that are not identified as participants in that virtual form, and,

wherein processing includes the input processing framework system itself performing operations on the held values, the operating including

performing all configured conversions on the held values,

invoking all configured validation checks on the held values,

evaluating all bindings configured on the value holders holding the held values, and

storing each held value in a location determined by the evaluating; and

instructions for displaying two or more virtual forms at the same time.

8. The storage medium of claim 7 wherein:

an object in the overall set that is both a value holder and an initiator and that is identified as a participant in one or more virtual forms can simultaneously be identified as a submitter of one of those virtual forms or a different virtual form.

9. The storage medium of claim 7 wherein:

when an initiator that is identified as a submitter of a virtual form triggers processing by the system, the implementation of the input processing framework system is able conditionally either to retain or discard the unprocessed value of each value holder that does not participate in that virtual form, wherein some such implementations of the input processing framework system expose an API that can be used to establish whether each such value holder retains or discards its unprocessed value at a particular point in time.

10. The storage medium of claim 7 wherein:

the objects in the overall set are visual or non-visual user interface (UI) components that operate within the input processing framework system;

the input processing framework system is capable of being used by software applications that present a UI, such as web applications or rich client UI applications;

the value holder objects are input components, an input component being any component capable of accepting input,

the initiator components are submission components, a submission component being any component capable of initiating processing, such as, in the case of a web application, any button, link, or component configured with client-side scripting that causes a request to be made to the server application that uses an input processing framework.

11. The storage medium of claim 10 wherein:

no topographical limitations are placed on where the user interface (UI) components can be positioned within the user interface, even a user interface that does not use CSS (cascading style sheets) positioning or a similar technology for the positioning of user interface (UI) components.

12. The storage medium of claim 10 wherein:

when an initiator that is embedded within a row of a table component and that is identified as a submitter of a virtual form triggers processing by the system, some implementations of the input processing framework system impose an additional limitation on which values are processed, the limitation being that such implementations do not process the values held by value holders that appear in rows of the table other than that row.