# US 2015/0149876 A1 · Status viewer

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0149876 A1
- Document ID: US20150149876A1
- Status: Published application
- Kind: A1
- Application number: 14/468,583
- Filed: 2014-08-26
- Published: 2015-05-28
- Earliest claimed: 2013-11-26
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Edmund Alexander Davis; Yuandi Jin; Kelsey Von Tish
- Web page: https://patentgrep.com/patent/US20150149876A1

## CPC

- G06F 40/18: of spreadsheets (form-filling G06F40/174)
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F 16/972: {Access to data in other repository systems, e.g. legacy data or dynamic Web page generation}
- G06F 40/177: of tables; using ruled lines
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to providing spreadsheets in a desktop integration framework that include error reports for validations. In various embodiments, a modeless error viewer is provided that allows end users to view an errors list for any failed row at the same time as the user corrects these errors.

## Claims

### Claim 1

A non-transitory computer-readable medium storing code that when executed by one or more processors associated with one or more computer systems configures the one or more processors for creating documents of desktop applications that act as user interfaces for web-based applications, the non-transitory computer-readable medium comprising:
code for creating contents of a document in a native application format associated with a first application;
code for associating one or more user interface elements with a portion of the contents of the document, the one or more user interface elements each being a component of a second application and providing a link between the portion of the contents of the document and data associated with data models provided by web-based applications in communication with the second application;
code for associating a second user interface element with the document, the second user interface element being a component of the second application and providing a view of status information created in response to a user interacting with the portion of the contents of the document associated with the first user interface element; and
code for generating metadata associated with the document based on the associating of the one or more user interface elements with the portion of the contents of the document and the associating of the second user interface element with the document.

### Claim 2 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for associating a second user interface element with the document comprises code for configuring the second user interface element to provide a view of runtime errors of the document.

### Claim 3 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for associating a second user interface element with the document comprises code for configuring the second user interface element to provide a view of runtime errors of the one or more user interface elements.

### Claim 4 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for associating a second user interface element with the document comprises code for configuring the second user interface element to provide one or more options for correcting runtime errors of the document.

### Claim 5 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for associating a second user interface element with the document comprises code for configuring the second user interface element to provide one or more explanations of runtime errors of the document.

### Claim 6 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for associating the first user interface element with the portion of the contents of the document comprises code for associating a text box, label, button, list, table, radio button, checkbox, input widget, or output widget.

### Claim 7 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for creating the contents of the document in the native application format associated with the first application comprises code for creating a spreadsheet using a spreadsheet desktop application.

### Claim 8 (depends on 1)

The non-transitory computer-readable medium of claim 1 wherein the code for creating the contents of the document in the native application format associated with the first application comprises code for creating a word processing document using a desktop publishing application.

### Claim 9 (depends on 1)

The non-transitory computer-readable medium of claim 1 further comprising:
code for publishing the document and the metadata associated with the document to the web-based application such that the document becomes usable as a user interface to the web-based application.

### Claim 10 (depends on 1)

The non-transitory computer-readable medium of claim 1 further comprising:
code for retrieving the document from the web-based application;
code for rendering the document based on the document and the metadata associated with the document at runtime to determine how the user interface element contributes to the user interface;
code for receiving user input;
code for validating the user input according to one or more data validation rules associated with the web-based applications;
code for generating status information based on a validation of the user input; and
code for rendering the status information using the second user interface element.

### Claim 11

A method comprising:
creating, by a computer system, contents of a document in a native application format associated with a first application;
associating, by the computer system, one or more user interface elements with a portion of the contents of the document, the one or more user interface elements each being a component of a second application and providing a link between the portion of the contents of the document and data associated with data models provided by web-based applications in communication with the second application;
associating, by the computer system, a second user interface element with the document, the second user interface element being a component of the second application and providing a view of status information created in response to a user interacting with the portion of the contents of the document associated with the first user interface element; and
generating, by the computer system, metadata associated with the document based on the associating of the one or more user interface elements with the portion of the contents of the document and the associating of the second user interface element with the document.

### Claim 12 (depends on 11)

The method of claim 11 wherein associating a second user interface element with the document comprises configuring the second user interface element to provide a view of runtime errors of the document.

### Claim 13 (depends on 11)

The method of claim 11 wherein associating a second user interface element with the document comprises configuring the second user interface element to provide a view of runtime errors of the one or more user interface elements.

### Claim 14 (depends on 11)

The method of claim 11 wherein associating a second user interface element with the document comprises configuring the second user interface element to provide one or more options for correcting runtime errors of the document.

### Claim 15 (depends on 11)

The method of claim 11 wherein associating a second user interface element with the document comprises configuring the second user interface element to provide one or more explanations of runtime errors of the document.

### Claim 16 (depends on 11)

The method of claim 11 wherein creating the contents of the document in the native application format associated with the first application comprises creating a spreadsheet using a spreadsheet desktop application.

### Claim 17 (depends on 11)

The method of claim 11 wherein creating the contents of the document in the native application format associated with the first application comprises creating a word processing document using a desktop publishing application.

### Claim 18 (depends on 11)

The method of claim 11 further comprising:
publishing the document and the metadata associated with the document to the web-based application such that the document becomes usable as a user interface to the web-based application.

### Claim 19 (depends on 11)

The method of claim 11 further comprising:
retrieving the document from the web-based application;
rendering the document based on the document and the metadata associated with the document at runtime to determine how the user interface element contributes to the user interface;
receiving user input;
validating the user input according to one or more data validation rules associated with the web-based applications;
generating status information based on a validation of the user input; and
rendering the status information using the second user interface element.

### Claim 20

A system comprising:
a processor; and
a memory storing a set of instructions which when execute by the processor configure the processor to:
create contents of a document in a native application format associated with a first application;
associate one or more user interface elements with a portion of the contents of the document, the one or more user interface elements each being a component of a second application and providing a link between the portion of the contents of the document and data associated with data models provided by web-based applications in communication with the second application;
associate a second user interface element with the document, the second user interface element being a component of the second application and providing a view of status information created in response to a user interacting with the portion of the contents of the document associated with the first user interface element; and
generate metadata associated with the document based on the associating of the one or more user interface elements with the portion of the contents of the document and the associating of the second user interface element with the document.
