The present invention relates generally to delivering electronic reports. More particularly, the present invention relates to delivering specific portions of electronic reports.
There are a number of commercially available products to produce reports from data stored in a database. For instance, Crystal Decisions, Inc. of Palo Alto, Calif., sells a number of widely used report generation products, including Crystal Reports™, Crystal Analysis™, and Crystal Enterprise™.
In many instances, reports are designed to have salient information as well as detailed information. Some users may wish to view a report in its entirety, while other users may wish to simply view the salient information included in the report. However, previous reporting approaches generally lack sufficient flexibility to deliver a specific portion of a report that may be of interest to a user. Rather, previous reporting approaches often delivered a report in its entirety or an entire page of the report at a time. Moreover, some users may wish to view specific portions of one or more reports. However, previous reporting approaches sometimes lack the ability to effectively link specific portions of one or more reports to provide a navigation path through the one or more reports.
Also, a report can include a number of elements such as, for example, a chart, a map, and the like. Certain devices such as cellular phones may not be able to properly display such a report. In accordance with previous reporting approaches, report designers often had to produce reports that were tailored for specific devices. Such approaches are time consuming and expensive, since multiple reports that contain similar information have to be produced.
It is against this background that a need arose to develop the apparatus and method described herein.
In one innovative aspect, the present invention relates to a computer-readable medium. In one embodiment, the computer-readable medium comprises a report parts viewer. The report parts viewer is configured to identify a first report object of a first plurality of report objects included in a first report. The report parts viewer is configured to facilitate display of the first report object absent each remaining report object included in the first report.
In another embodiment, the computer-readable medium comprises instructions to coordinate a navigation request for a first report object with a second report object. The first report object is included in a first report, and the second report object is included in one of the first report and a second report. The computer-readable medium also comprises instructions to produce a data context of the second report object in response to the navigation request. The computer-readable medium further comprises instructions to retrieve at least one instance of the second report object based on the data context of the second report object.
In another innovative aspect, the present invention relates to a method of processing reports. In one embodiment, the method comprises coordinating a request to view a first report with a first report object of a first plurality of report objects included in the first report. The method also comprises facilitating display of the first report object absent each remaining report object included in the first report.
Embodiments of the invention provide functionality to allow a specific portion of a report to be viewed without the rest of the report. In particular, embodiments of the invention allow flexibility in delivering a specific portion of a report that can be tailored for a particular user or for a particular computing device. Embodiments of the invention facilitate linking of various report objects to create a navigation path through one or more reports. Also, embodiments of the invention facilitate navigation to one or more instances of a report object by passing an appropriate data context to the report object.
For a better understanding of the nature and objects of the invention, reference should be made to the following detailed description taken in conjunction with the accompanying drawings, in which:
The CPU 108 is also connected to a memory 112 via the bus 110. The memory 112 stores a set of executable programs. One executable program is a report generator 116. The report generator 116 can utilize standard techniques to produce a set of reports 120. In particular, the report generator 116 can access a database 114 resident in the memory 112 to produce the set of reports 120. Each report of the set of reports 120 can include one or more report objects. A report object refers to a particular portion of a report. In some instances, a report object refers to a particular portion of a report that contains related information. A report object can correspond to, for example, a summary field, a detail field, a chart, a map, a bitmap, a crosstab, a text block, a group name, or a combination thereof.
Referring to
In the present embodiment of the invention, the report parts tool 118 can operate in conjunction with a report parts viewer 122. Unlike conventional report viewers, the report parts viewer 122 allows a user to view a specific portion of a report without the rest of the report. In particular, the report parts viewer 122 facilitates display of a set of report objects configured using the report parts tool 118. As discussed previously, various report objects can be linked to create a navigation path, and the report parts viewer 122 can coordinate navigation requests from a user with specific report objects to be displayed along the navigation path. In the present embodiment of the invention, the report parts viewer 122 can be integrated with Internet applications and wireless applications. In particular, the report parts viewer 122 can facilitate display of a set of report objects in applications such as, for example, portals or digital dashboards.
The report parts viewer 122 may be executed to display a set of report objects using, for example, a video monitor included in the set of input/output devices 106. Alternatively, or in conjunction, the report parts viewer 122 may be executed to allow a set of report objects to be displayed on a computing device 126. The computing device 126 may be a client computer, including conventional client computer components, or a portable computing device, including conventional portable computing device components. Examples of portable computing devices include personal digital assistants (“PDAs”) two-way pagers, and cellular phones. Unlike previous approaches, the report parts viewer 122 need not deliver data associated with an entire report or an entire page of the report to the computing device 126, which may not be able to properly process such data. Rather, the report parts viewer 122 can deliver data associated with a specific portion of the report to be displayed. The report parts viewer 122 can deliver different portions of a report to different types of computing devices, thereby avoiding the need to produce multiple reports for the different types of computing devices.
While the database 114, the report generator 116, the report parts tool 118, the set of reports 120, and the report parts viewer 122 are shown residing in the single computer 102, it should be recognized that such configuration is not required in all applications. For instance, one or more of these elements may reside in the computing device 126 or in a separate computer (not shown in
By way of example,
A report object (e.g., the report object 306) included in a report can be associated with a set of report object parameters. Examples of report object parameters include:
A report parts tool (e.g., the report parts tool 118) can configure a first report object of a set of report objects included in a first report as an initial report object. In the example shown in
A report parts tool (e.g., the report parts tool 118) can configure a second report object as a destination report object, which second report object can be associated with a first report object included in the same or a different report. A destination report object can correspond to a report object that is subsequently displayed along a particular navigation path. Multiple destination report objects can be configured, and the multiple destination report objects can be sequentially or simultaneously displayed along a particular navigation path. For certain applications, the report parts tool can configure a second report object as a destination report object by creating a navigation link between a first report object and the second report object. Such a navigation link can be created by specifying one or more report object parameters of the second report object and can be stored along with a report as a property of the report. In the example shown in
If desired, navigation functionality can be enhanced by further linking report objects. In the example shown in
Returning to
As discussed previously, various report objects can be linked to create a navigation path, and the report parts viewer can coordinate navigation requests with specific report objects to be displayed along the navigation path. For instance, the report parts viewer can coordinate a navigation request for the first report object with a second report object included in the same report. In particular, in response to the navigation request, the report parts viewer can identify the second report object as a destination report object. Such identification can be based on, for example, a navigation link between the first report object and the second report object. Multiple instances of the second report object can be defined, and the report parts viewer can facilitate navigation to one or more instances of the second report object by passing an appropriate data context to the second report object. The report parts viewer can then facilitate display of the second report object absent each remaining report object included in the first report. For certain applications, the report parts viewer can deliver data associated with the second report object to a computing device (e.g., the computing device 126), which can display the second report object.
Alternatively, or in conjunction, the report parts viewer can coordinate a navigation request for the first report object with a second report object of a set of report objects included in a second report. As discussed previously, the report parts viewer can facilitate navigation to one or more instances of the second report object by passing an appropriate data context to the second report object. The report parts viewer can then facilitate display of the second report object absent each remaining report object included in the second report.
Attention next turns to specific embodiments of the invention to further illustrate features and advantages of the invention. As discussed previously, a report object can be associated with a set of report object parameters, which can include a report URI, a report object name, and a data context.
A data context of a report object can indicate one or more hierarchy levels associated with a report and can define a region in the report in which one or more instances of the report object can be located. For certain applications, a data context of a report object can be specified using a format similar to Xpath (e.g., /USA or /USA/CA) or using a strongly-typed format (e.g., /Country[USA] or /Country[USA]/Region[CA]). A data context of a detail-level report object can be specified using a record number-based format (e.g., /Country[USA]/Region[CA]/RecordNumber[4]). All instances of a report object can be specified using a special character such as “*” (e.g., /Country[USA]/Region[*]). For certain applications, a data context of a report object can be specified using a formula-based format (e.g., “/”+{Table.Field} or “/”+{Table.Field}+“/”+{Table.Field}).
Referring to
When a user drills-down from the report object 700, a report parts viewer (e.g., the report parts viewer 122) can identify a data context of the report object 700 (e.g., /Country[USA]). The report parts viewer can produce a data context of the report object 702 (e.g., /Country[USA]/Region[*]) based on the data context of the report object 700. In particular, the report parts viewer can append “*” to the data context of the report object 700 to produce the data context of the report object 702. The report parts viewer can pass the produced data context to the report object 702 to retrieve a relevant instance (or relevant instances) of the report object 702. The report parts viewer can then facilitate display of the relevant instance (or relevant instances) of the report object 702.
In another scenario, the report parts viewer can identify a different data context of the report object 700 (e.g., /Country[Canada]). The report parts viewer can produce a data context of the report object 702 (e.g., /Country[Canada]/Region[*]) based on the different data context of the report object 700 and can pass the produced data context to the report object 702 to retrieve a relevant instance (or relevant instances) of the report object 702. For instance, instead of the chart shown in
When a user drill-downs from the report object 800, a report parts viewer (e.g., the report parts viewer 122) can identify a data context of the report object 800 (e.g., /Country[USA]) and can produce a data context of the report object 804 (e.g., /Country[USA]/Region[CA]) based on the data context of the report object 800. In the present embodiment, the report parts viewer can identify the target region 802 based on coordinates (e.g., x and y offsets) of the target region 802 as specified by the user. Once the target region 802 is identified, the report parts viewer can append “CA” to the data context of the report object 800 to produce the data context of the report object 804. The report parts viewer can pass the produced data context to the report object 804 to retrieve a relevant instance (or relevant instances) of the report object 804. The report parts viewer can then facilitate display of the relevant instance (or relevant instances) of the report object 804.
In another scenario, the report parts viewer can identify a different target region (e.g., a target region corresponding to NY) specified by the user. The report parts viewer can produce a data context of the report object 804 (e.g., /Country[USA]/Region[NY]) based on the different target region and can pass the produced data context to the report object 804 to retrieve a relevant instance (or relevant instances) of the report object 804. For instance, instead of the summary field shown in
Turning next to
When a user specifies a navigation request for the report object 900, a report parts viewer (e.g., the report parts viewer 122) can identify a data context of the report object 900 (e.g., /Bicycle). The report parts viewer can produce a data context of the report object 902 (e.g., /Bicycle) by applying “Bicycle” to the formula “/”+{Product.Product Class}. The report parts viewer can pass the produced data context to the report object 902 to retrieve a relevant instance (or relevant instances) of the report object 902. The report parts viewer can then facilitate display of the relevant instance (or relevant instances) of the report object 902.
In another scenario, the report parts viewer can identify a different data context of the report object 900 (e.g., /Accessory). The report parts viewer can produce a data context of the report object 902 (e.g., /Accessory) based on the different data context of the report object 900 and can pass the produced data context to the report object 902 to retrieve a relevant instance (or relevant instances) of the report object 902. For instance, instead of the chart shown in
When a user specifies a navigation request for the report object 1000, a report parts viewer (e.g., the report parts viewer 122) can identify a particular region (e.g., a crosstab row, a crosstab column, or a crosstab cell) of the report object 1000 specified by the user. In particular, the report parts viewer can identify the particular region based on coordinates (e.g., a column value, a row value, or both) of the particular region as specified by the user. The report parts viewer can produce a data context of the report object 1002 by applying a column value, a row value, or both, to a formula specified for the data context of the report object 1002. For instance, the report parts viewer can apply the column value “Accessory” to the formula “/”+{Product.Product Class} to produce the data context of the report object 1002 (e.g., /Accessory). The report parts viewer can pass the produced data context to the report object 1002 to retrieve a relevant instance (or relevant instances) of the report object 1002. The report parts viewer can then facilitate display of the relevant instance (or relevant instances) of the report object 1002.
In another scenario, the report parts viewer can identify a different region (e.g., a region corresponding to the column value “Bicycle”) of the report object 1000 specified by the user. The report parts viewer can produce a data context of the report object 1002 (e.g., /Bicycle) based on the different region and can pass the produced data context to the report object 1002 to retrieve a relevant instance (or relevant instances) of the report object 1002. For instance, instead of the chart shown in
For some embodiments of the invention, implementation of navigation functionality supports firing of events (e.g., server-side events). In particular, before a navigation is carried out, a server-side event can be fired to allow another executable program to control or modify the navigation. For instance, in response to a navigation request, another executable program can acquire a particular data context and perform a database query based on the particular data context. As another example, a report object can be incorporated in a particular web page. When a navigation request is specified for the report object, an event handler code can be applied to route the navigation request to another web page that incorporates a report (e.g., an entire report) that includes the report object.
For certain applications, navigation functionality can be implemented to allow for “forward” and “backward” navigation to facilitate viewing of subsets of various report objects or subsets of various instances of a report object. Such “forward” and “backward” navigation can be implemented in a manner similar to bookmarks in a document. When navigating “forward”, a report parts viewer (e.g., the report parts viewer 122) can configure a data context as a bookmark and can navigate to a data context of a next report object (or a next instance of a report object) in a hierarchy. Similarly, when navigating “backward”, the report parts viewer can configure a data context as a bookmark and can navigate to a data context of a previous report object (or a previous instance of a report object) in the hierarchy.
Navigation functionality as described herein can be effectively applied to a variety of user scenarios, including the rapid development of report aggregations by facilitating linking and use of “child” reports as data sources. For instance, navigation functionality as described herein can be applied to streamline the creation of trending reports or to facilitate navigation to “detail” reports where detail data resides. In addition, navigation functionality as described herein can be applied in conjunction with conventional report viewers, such as conventional page viewers.
It should be recognized that the embodiments of the invention discussed above are merely exemplary, and various other embodiments are encompassed by the present invention.
For instance, in some embodiments of the invention, a report parts viewer can be incorporated in a web page using the following sequence of operations:
The following provides an example of an Active Server Page (“ASP”) program that implements the sequence of operations:
When the ASP program is executed, a report object can be displayed by calling an OutputReport function and passing it to a report path constant:
As another example, an embodiment of the invention may include a help system, including a wizard that provides assistance to users, for configuring a computer network (e.g., the computer network 100) and its various components.
An embodiment of the present invention relates to a computer storage product with a computer-readable medium having computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”), ROM devices, and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions.
While the present invention has been described with reference to the specific embodiments thereof, it should be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the true spirit and scope of the invention as defined by the appended claims. In addition, many modifications may be made to adapt a particular situation, material, composition of matter, method, process step or steps, to the objective, spirit and scope of the present invention. All such modifications are intended to be within the scope of the claims appended hereto. In particular, while the methods disclosed herein have been described with reference to particular steps performed in a particular order, it will be understood that these steps may be combined, sub-divided, or re-ordered to form an equivalent method without departing from the teachings of the present invention. Accordingly, unless specifically indicated herein, the order and grouping of the steps is not a limitation of the present invention.
Number | Name | Date | Kind |
---|---|---|---|
5132899 | Fox | Jul 1992 | A |
5257185 | Farley et al. | Oct 1993 | A |
5555403 | Cambot et al. | Sep 1996 | A |
5606609 | Houser et al. | Feb 1997 | A |
5630122 | Kaplan et al. | May 1997 | A |
5634122 | Loucks et al. | May 1997 | A |
5664182 | Nierenberg et al. | Sep 1997 | A |
5710900 | Anand et al. | Jan 1998 | A |
5787416 | Tabb et al. | Jul 1998 | A |
5801702 | Dolan et al. | Sep 1998 | A |
5832504 | Tripathi et al. | Nov 1998 | A |
5844572 | Schott | Dec 1998 | A |
5978818 | Lin | Nov 1999 | A |
6073129 | Levine et al. | Jun 2000 | A |
6081810 | Rosenzweig et al. | Jun 2000 | A |
6088718 | Altschuler et al. | Jul 2000 | A |
6098081 | Heidorn et al. | Aug 2000 | A |
6108636 | Yap et al. | Aug 2000 | A |
6154766 | Yost et al. | Nov 2000 | A |
6160549 | Touma et al. | Dec 2000 | A |
6185560 | Young et al. | Feb 2001 | B1 |
6212524 | Weissman et al. | Apr 2001 | B1 |
6222540 | Sacerdoti | Apr 2001 | B1 |
6247008 | Cambot et al. | Jun 2001 | B1 |
6360246 | Begley et al. | Mar 2002 | B1 |
6377956 | Hsu et al. | Apr 2002 | B1 |
6397207 | Bleizeffer et al. | May 2002 | B1 |
6442714 | Griffin et al. | Aug 2002 | B1 |
6460058 | Koppolu et al. | Oct 2002 | B2 |
6477529 | Mousseau et al. | Nov 2002 | B1 |
6519571 | Guheen et al. | Feb 2003 | B1 |
6529217 | Maguire et al. | Mar 2003 | B1 |
6549906 | Austin et al. | Apr 2003 | B1 |
6569205 | Poggi | May 2003 | B1 |
6578027 | Cambot et al. | Jun 2003 | B2 |
6581068 | Bensoussan et al. | Jun 2003 | B1 |
6643635 | Nwabueze | Nov 2003 | B2 |
6647392 | Tagg | Nov 2003 | B1 |
6654770 | Kaufman | Nov 2003 | B2 |
6668253 | Thompson et al. | Dec 2003 | B1 |
6768994 | Howard et al. | Jul 2004 | B1 |
6775675 | Nwabueze et al. | Aug 2004 | B1 |
6801910 | Bedell et al. | Oct 2004 | B1 |
6826597 | Lonnroth et al. | Nov 2004 | B1 |
6831668 | Cras et al. | Dec 2004 | B2 |
6889210 | Vainstein | May 2005 | B1 |
6906717 | Couckuyt et al. | Jun 2005 | B2 |
6915289 | Malloy et al. | Jul 2005 | B1 |
6917937 | Rubendall | Jul 2005 | B1 |
6993533 | Barnes | Jan 2006 | B1 |
6995768 | Jou et al. | Feb 2006 | B2 |
7003506 | Fisk et al. | Feb 2006 | B1 |
7015911 | Shaughnessy et al. | Mar 2006 | B2 |
7093194 | Nelson | Aug 2006 | B2 |
7155439 | Cope | Dec 2006 | B2 |
7170519 | Patel et al. | Jan 2007 | B2 |
7243106 | Vierich et al. | Jul 2007 | B2 |
7310687 | Psounis et al. | Dec 2007 | B2 |
20010042080 | Ross | Nov 2001 | A1 |
20020035501 | Handel et al. | Mar 2002 | A1 |
20020042687 | Tracy et al. | Apr 2002 | A1 |
20020052954 | Polizzi et al. | May 2002 | A1 |
20020091681 | Cras et al. | Jul 2002 | A1 |
20020140699 | Miyadai | Oct 2002 | A1 |
20030004272 | Power | Jan 2003 | A1 |
20030023476 | Gainey | Jan 2003 | A1 |
20030028451 | Ananian | Feb 2003 | A1 |
20030046264 | Kauffman | Mar 2003 | A1 |
20030050919 | Brown et al. | Mar 2003 | A1 |
20030050927 | Hussam | Mar 2003 | A1 |
20030074456 | Yeung et al. | Apr 2003 | A1 |
20030101201 | Saylor et al. | May 2003 | A1 |
20030106016 | Kendrick et al. | Jun 2003 | A1 |
20030115207 | Bowman et al. | Jun 2003 | A1 |
20030151621 | McEvilly et al. | Aug 2003 | A1 |
20030196121 | Raley et al. | Oct 2003 | A1 |
20030208460 | Srikant et al. | Nov 2003 | A1 |
20030225747 | Brown et al. | Dec 2003 | A1 |
20040024763 | Anderson | Feb 2004 | A1 |
20040034615 | Thomson et al. | Feb 2004 | A1 |
20040078593 | Hind et al. | Apr 2004 | A1 |
20040117731 | Blyashov | Jun 2004 | A1 |
20040122730 | Tucciarone et al. | Jun 2004 | A1 |
20040153649 | Rhoads et al. | Aug 2004 | A1 |
20040153969 | Rhodes | Aug 2004 | A1 |
20050091581 | Bezrukov et al. | Apr 2005 | A1 |
20050165815 | Ozzie et al. | Jul 2005 | A1 |
20050169496 | Perry | Aug 2005 | A1 |
20050262047 | Wu et al. | Nov 2005 | A1 |
20060010060 | Jones et al. | Jan 2006 | A1 |
20060041589 | Helfman et al. | Feb 2006 | A1 |
20060271508 | Wu et al. | Nov 2006 | A1 |
20060277531 | Horwitz et al. | Dec 2006 | A1 |
20070073690 | Boal et al. | Mar 2007 | A1 |
20070198918 | Mor | Aug 2007 | A1 |
20070214112 | Towers et al. | Sep 2007 | A1 |
Number | Date | Country |
---|---|---|
2151654 | Dec 1996 | CA |
1014283 | Jun 2000 | EP |
1304630 | Apr 2003 | EP |
Number | Date | Country | |
---|---|---|---|
20070130517 A1 | Jun 2007 | US |