News Column

"User Interface Date Selectors for Historical Reports" in Patent Application Approval Process

July 8, 2014



By a News Reporter-Staff News Editor at Information Technology Newsweekly -- A patent application by the inventors ADAM, Abraham (San Francisco, CA); GITELMAN, Alex (Berkeley, CA); KAO, Daphne A. (San Francisco, CA); NASH, Eric (San Francisco, CA); BELLAMANE, Harish (Bangalore, IN); TANG, Michael (Petaluma, CA); EBERL, Stefan (San Francisco, CA); MEHTA, Twisha (Fremont, CA); MUTHUKRISHNAN, Venkatachalam (Tamilnadu, IN), filed on October 29, 2013, was made available online on June 26, 2014, according to news reporting originating from Washington, D.C., by VerticalNews correspondents.

This patent application is assigned to salesforce.com, inc.

The following quote was obtained by the news editors from the background information supplied by the inventors: "The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.

"In computer science, an object is a location in memory having a value and referenced by an identifier. Since the introduction of object-oriented programming, an object can refer to a particular instance of a class, and can include multiple fields that have their corresponding values. Relational database management systems may track historical changes to data objects to provide additional information to system users. For example, a salesperson who stores sales opportunity information using a database management system may benefit from accessing the history of the sales opportunity information for a prospective customer, such as changes to the sales opportunity amounts and the sales opportunity scheduled sales dates during the last year. On Friday morning September 13th, the salesperson accesses the database management system to determine what were the potential sales amount and the scheduled sales date for all of the salesperson's sales opportunities during the present month.

"The prior art user interface for the database management system permits the user to select either fixed dates or relative dates, such as the last day of each week or each day of the month. The weekly report would provide the requested data for the end of the day on Friday September 6.sup.th, which is not enough dates for the salesperson, while the daily report would provide the requested data for the end of the day on September 1.sup.st, 2.sup.nd, 3.sup.rd, 4.sup.th, 5.sup.th, 6.sup.th, 7.sup.th, 8.sup.th, 9.sup.th, 10.sup.th, 11.sup.th, and 12.sup.th, which is too many dates for the salesperson. If the salesperson wants a report with a number of dates between the number of dates provided by the weekly report and the number of dates provided by the daily report, the prior art user interface for the database management system permits the user to select fixed dates, such as identifying each date individually, which in many situations could become a time consuming process that may result in errors and/or user frustration."

In addition to the background information obtained for this patent application, VerticalNews journalists also obtained the inventors' summary information for this patent application: "In accordance with embodiments, there are provided systems and methods for user interface date selectors for historical reports. A user interface outputs a date selector including a calculated dates option, wherein the calculated dates option is based on a date frequency applied to a date range. For example, the user interface outputs a date frequency field and a date range field. The user interface receives a selection via the date selector. For example, the user interface receives the selection of an every third day frequency and a date range of the current month. Dates associated with the selection are identified. For example, the system calculates the selected days to be September 3.sup.rd, 6.sup.th, 9.sup.th, and 12.sup.th. The user interface outputs the dates as a preview of a historical report, wherein the dates are output in a chronological order. For example, the user interface outputs a preview of a historical report that includes the dates September 3.sup.rd, 6.sup.th, 9.sup.th, and 12.sup.th. Accordingly, systems and methods are provided which enable a database system to improve the performance, efficiency, and the ease of use of selecting dates for historical reports.

"While one or more implementations and techniques are described with reference to an embodiment in which user interface date selectors for historical reports are implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the one or more implementations and techniques are not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE.RTM., DB2.RTM. by IBM and the like without departing from the scope of the embodiments claimed.

"Any of the above embodiments may be used alone or together with one another in any combination. The one or more implementations encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments do not necessarily address any of these deficiencies. In other words, different embodiments may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

"In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples, the one or more implementations are not limited to the examples depicted in the figures.

"FIG. 1 is an operational flow diagram illustrating a high level overview of a method for user interface date selectors for historical reports in an embodiment;

"FIG. 2 is a screen shot illustrating frames of an example user interface screen of a display device supporting methods for user interface date selectors for historical reports;

"FIG. 3 illustrates a block diagram of an example of an environment wherein an on-demand database service might be used; and

"FIG. 4 illustrates a block diagram of an embodiment of elements of FIG. 3 and various possible interconnections between these elements."

URL and more information on this patent application, see: ADAM, Abraham; GITELMAN, Alex; KAO, Daphne A.; NASH, Eric; BELLAMANE, Harish; TANG, Michael; EBERL, Stefan; MEHTA, Twisha; MUTHUKRISHNAN, Venkatachalam. User Interface Date Selectors for Historical Reports. Filed October 29, 2013 and posted June 26, 2014. Patent URL: http://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=%2Fnetahtml%2FPTO%2Fsearch-adv.html&r=286&p=6&f=G&l=50&d=PG01&S1=20140619.PD.&OS=PD/20140619&RS=PD/20140619

Keywords for this news article include: inc., salesforce.com inc, Information Technology, Information and Data Management.

Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC


For more stories covering the world of technology, please see HispanicBusiness' Tech Channel



Source: Information Technology Newsweekly


Story Tools






HispanicBusiness.com Facebook Linkedin Twitter RSS Feed Email Alerts & Newsletters