1. Field of the Invention
The present invention relates to the field of messaging and more particularly to the integration of business objects within a message.
2. Description of the Related Art
Messaging forms the heart of the Internet. The Internet with its global, continuous reach enables interpersonal activities from afar, including both asynchronous messaging like e-mail and document sharing and threaded discussions, to real time communications systems such as instant messaging and group chat. Electronic mail delivery systems, the prototypical asynchronous communications systems, in its time represented a giant leap forward in respect to global interpersonal communications. Prior to electronic mail, individuals primarily communicated via telephone, facsimile and post. With electronic mail, however, individuals expect near instant delivery of text, and even imagery, audio and video, without incurring the delay typical of the postal system, or the expense associated with telephony and fax technologies.
Despite the ubiquity of electronic mail, asynchronous communications systems lack several elements common in the realm of real time communications systems. In particular, the seemingly instant delivery of a message cannot be experienced in the world of electronic mail. In a real-time society, the minor latencies associated with electronic mail often cannot be suitable for the task at hand where a real-time conversation will be required in addressing a problem or performing a collaborative task. More importantly, often the feel and nature of a “conversation” as it is known to human beings only can be approximated through real time communications where the participants to a conversation feel the spontaneity of an exchange of ideas, much as is the case in a live, face-to-face conversation. Thus, the instant messaging environment has proven to be an invaluable compliment to e-mail as a real-time conversational mechanism.
Conventional messaging systems allow users to exchange messages across a network. As a stand alone application, messaging enjoys straightforward application as a conversational tool. Within, the business workflow environment, however, the role of the message, whether synchronous or asynchronous, is less clear. A business workflow generally involves the electronic and in person collaboration between collaborators in order to accomplish a goal. As part of the business workflow, collaborators receive documents electronically, amend the documents and ultimately approve or disprove of the distribution of the document. Business objects have been specifically incorporated into document editing and document viewing applications in order to permit the management of a document in a business workflow.
Specifically, a business object encapsulates traditional lower-level objects that implement a business process. Notably, business objects both simulate corporate procedures and translate smoothly into software objects. Historically, business objects have been embedded in Web pages and e-mail documents using client side extensions to browser clients. More recently, scripts disposed in client side content like Web pages and e-mail messages have been configured to maintain an active connection with underlying business objects to provide an integrated active view of the business objects. The integration of business objects, however, has largely eluded both asynchronous communications like e-mail, shared documents and threaded discussions, and synchronous real-time applications like instant messengers and group chat sessions.
Embodiments of the present invention address deficiencies of the art in respect to messaging and provide a novel and non-obvious method, system and computer program product for business object integration with messaging. In an embodiment of the invention, a method for messaging integration of a business object can be provided. The method can include embedding a business object in message text in a messaging session provided by a messenger, and applying an action to the business object from within the messaging session of the messenger. The method further can include identifying a pronoun in the message text referencing the business object, and visually distinguishing the identified pronoun in the message text to draw a correlation between the business object and the pronoun.
In a second aspect of the embodiment, the method further can include identifying a verb in the message text in association with a pronoun referencing the business object, and providing a context menu for the business object in the messaging session with entries in the context menu limited according to the identified verb.
Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:
Embodiments of the present invention provide a method, system and computer program product for integrating business objects in a messaging session. In accordance with an embodiment of the present invention, a business object can be embedded in a messaging session such as an e-mail exchange, instant messaging or chat session, threaded discussion, or shared document library, to name only a few. Thereafter, pronouns in the text of the session referencing the business object can be visually distinguished to assist in the understanding of the role of the business object in the session. Using the pronouns, a verb operating on the business object can be identified and the entries of a context menu for the business object can be reduced accordingly. Yet further, the business objects can be indexed and the index can be used when producing a transcript for the session. In this regard, the transcript can include separate views of the messaging text and the business object. Finally, the session can provide a justification for actions performed on the business object by forwarding a copy of the chat text to an external component supporting the business object.
In further illustration,
Notably, a context menu 150 can be provided for the business object 130 in the instant messenger 110. The context menu 150 can include entries 160 permitting actions to be performed in respect to the business object 130. The entries 160, however, can be reduced depending upon the context of the chat text 120. In this regard, different grammatical constructs relating to the pronouns 140 in the chat text 120 can be identified according to grammatical rules such as Sentence—>Noun Phrase+Verb Phrase, Verb Phrase—>Verb+Noun Phrase, and Noun Phrase—>article+Noun. Thereafter, the verbs acting on the pronouns 140 can be determined and matched to a reduced set of the entries 160 for the context menu 150. For example, as shown in
Once an action has been performed on the business object 130, the action can be communicated to the backend component 190A. To provide a justification for the action, the chat text 120 can be encapsulated in justification data 100 and provided to the backend component 190A for storage as a record in the data store 190B. In this way, one reviewing the action for the business object 130 will access the justification 100 to provide context for the action.
The instant messenger 110 can produce a chat transcript 180 of the chat text 120. To facilitate a viewing of the chat text 120, however, the chat transcript 180 can provide one transcript view 180A of the chat text 120 and another business object view 180B of the business object 130. In the business object view 180B, a listing of each business object 130 and the corresponding action taken upon the business object 130 can be provided. In this way, the viewer can readily identify actions taken upon business objects integrated into the instant messenger 110.
Finally, a keyword index 170 can be generated for the chat transcript 180 in order to facilitate the searching of the chat transcript 180. Though inverted indexing can be performed on the chat text 120, the business objects 130 can be indexed differently in that the business object 130 can be represented in the chat text 120 with attribute tags. In this way, the attribute tags for the business object 130 can be reflected in the index 170 as opposed to the business object 130, itself.
Importantly, the skilled artisan is to recognize that the exemplary use of an instant messenger 110 in
In further illustration,
Notably, business object integration logic 260 can be coupled to the messaging server 210 through the host server 200. Alternatively, the business object integration logic 260 can be coupled to one or more of the clients 220 or the business object integration logic 260 can be distributed between the host server 200 and the clients 220. The logic 260 can include program code enabled to integrate a business object into a messaging session and to provide integrative tools including reference marking, messaging transcript processing, context menu reduction, justification text transfer and business object indexing. To that end, the business object integration logic 260 can include a reference marking module 260A, an integrated messaging transcript module 260B, a context menu reduction module 260C, a justification text transfer module 260D and a business object indexing module 260E.
The reference marking module 260A can be enabled to identify pronouns in message text, to correlate the pronouns with a business object in the message text and to visually distinguish the pronouns so as to overtly specify the reference of the pronouns to the business object. The integrated messaging transcript module 260B can be enabled to provide a split view of chat text for a messaging session and business objects embedded in the messaging session and corresponding actions performed on the business objects. The context menu reduction module 260C can be enabled to identify and map verbs in message text in association with an embedded business object in order to produce a reduced set of entries to be rendered in a context menu for the business object in the messaging session. Specifically,
Beginning in block 310, chat text for a messaging session can be loaded and rules for locating pronouns can be loaded as well in block 320. In block 330, the message text can be parsed and in block 340 one or more pronouns referencing a business object can be located by applying the rules to the message text. Subsequently, a verb can be identified in association with a pronoun in block 350. In block 360, a set of menu entries associated with the verb can be located in a table and in block 370, a context menu can be populated with the set of menu entries. Finally, in block 380 the context menu can be displayed in association with the business object in the message session.
Returning to
Embodiments of the invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, and the like. Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system.
For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.
This application is a Continuation of U.S. application Ser. No. 11/948,370, filed on Nov. 30, 2007. This application is related to the following U.S. Patent Applications: U.S. patent application Ser. No. 11/948,342, entitled “BUSINESS OBJECT ACTION JUSTIFICATION FOR BUSINESS OBJECT INTEGRATION INTO MESSAGING” and filed on Nov. 30, 2007; U.S. patent application Ser. No. 11/948,323, entitled “SPLIT TRANSCRIPT VIEW FOR BUSINESS OBJECT INTEGRATION INTO MESSAGING” and filed on Nov. 30, 2007; and U.S. patent application Ser. No. 11/948,398, entitled “INDEXING A MESSAGING SESSION FOR BUSINESS OBJECT INTEGRATION INTO MESSAGING” and filed on Nov. 30, 2007.
Number | Name | Date | Kind |
---|---|---|---|
5793365 | Tang et al. | Aug 1998 | A |
8775513 | Hind et al. | Jul 2014 | B2 |
8782250 | Hind et al. | Jul 2014 | B2 |
8788698 | Hind et al. | Jul 2014 | B2 |
20020147645 | Alao et al. | Oct 2002 | A1 |
20030023691 | Knauerhase | Jan 2003 | A1 |
20030220784 | Fellenstein et al. | Nov 2003 | A1 |
20040059609 | Chatlain et al. | Mar 2004 | A1 |
20040083292 | Lueckhoff et al. | Apr 2004 | A1 |
20040268246 | Leban et al. | Dec 2004 | A1 |
20060123347 | Hewitt et al. | Jun 2006 | A1 |
20070124312 | Simpson et al. | May 2007 | A1 |
20070244811 | Tumminaro | Oct 2007 | A1 |
20080141146 | Jones | Jun 2008 | A1 |
20080243933 | Holtzman et al. | Oct 2008 | A1 |
20090043857 | Ferlitsch | Feb 2009 | A1 |
20090089250 | Stieber et al. | Apr 2009 | A1 |
20090129278 | Kumar et al. | May 2009 | A1 |
20090144371 | Hind et al. | Jun 2009 | A1 |
20090144372 | Hind et al. | Jun 2009 | A1 |
20090144373 | Hind et al. | Jun 2009 | A1 |
20090144386 | Hind et al. | Jun 2009 | A1 |
20140317209 | Hind et al. | Oct 2014 | A1 |
20140317534 | Hind et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
101447952 | Jun 2009 | CN |
101447953 | Jun 2009 | CN |
101447954 | Jun 2009 | CN |
101447955 | Jun 2009 | CN |
2003505794 | Feb 2003 | JP |
2005527878 | Sep 2005 | JP |
2006506740 | Feb 2006 | JP |
200937225 | Sep 2009 | TW |
200939707 | Sep 2009 | TW |
200939708 | Sep 2009 | TW |
0108065 | Feb 2001 | WO |
03034174 | Apr 2003 | WO |
2004046956 | Jun 2004 | WO |
Entry |
---|
U.S. Appl. No. 11/948,323, Non-Final Office Action, Sep. 18, 2009, 13 pg. |
U.S. Appl. No. 11/948,323, Non-Final Office Action, Apr. 10, 2010, 13 pg. |
U.S. Appl. No. 11/948,323 Final Office Action, Aug. 12, 2010, 20 pg. |
U.S. Appl. No. 11/948,323, Notice of Appeal and Appeal Brief, Nov. 9, 2010, 20 pg. |
U.S. Appl. No. 11/948,323, Examiner's Answer, Feb. 1, 2011, 24 pg. |
U.S. Appl. No. 11/948,323, Reply Brief, Mar. 27, 2011, 7 pg. |
U.S. Appl. No. 11/948,323, Decision on Appeal, Dec. 31, 2013, 9 pg. |
U.S. Appl. No. 11/948,323, Notice of Allowance, Mar. 11, 2014, 7 pg. |
U.S. Appl. No. 11/948,370, Non-Final Office Action, Sep. 18, 2009, 12 pg. |
U.S. Appl. No. 11/948,370, Non-Final Office Action, Mar. 12, 2010, 14 pg. |
U.S. Appl. No. 11/948,370, Final Office Action, Aug. 12, 2010, 21 pg. |
U.S. Appl. No. 11/948,370, Notice of Appeal and Appeal Brief, Nov. 9, 2010, 48 pg. |
U.S. Appl. No. 11/948,370, Examiner's Answer, Feb. 1, 2011, 23 pg. |
U.S. Appl. No. 11/948,370, Reply Brief, Mar. 27, 2011, 10 pg. |
U.S. Appl. No. 11/948,370, Decision on Appeal, Dec. 24, 2013, 9 pg. |
U.S. Appl. No.. 11/948,370, Notice of Allowance, Mar. 4, 2014, 7 pg. |
U.S. Appl. No. 11/948,398, Non-Final Office Action, Sep. 15, 2009, 12 pg. |
U.S. Appl. No. 11/948,398, Non-Final Office Action, Mar. 2, 2009, 13 pg. |
U.S. Appl. No. 11/948,398, Final Office Action, Aug. 13, 2010, 16 pg. |
U.S. Appl. No. 11/948,398, Notice of Appeal and Appeal Brief, Nov. 9, 2010, 43 pg. |
U.S. Appl. No. 11/948,398, Examiner's Answer, Jan. 31, 2011, 20 pg. |
U.S. Appl. No. 11/948,398, Reply Brief, Mar. 27, 2011, 9 pg. |
U.S. Appl. No. 11/948,398, Decision on Appeal, Dec. 31, 2013, 8 pg. |
U.S. Appl. No. 11/948,398, Notice of Allowance, Mar. 14, 2014, 7 pg. |
U.S. Appl. No. 11/948,342, Non-Final Office Action, Sep. 4, 2009, 11 pg. |
U.S. Appl. No. 11/948,342, Final Office Action, Mar. 9. 2010, 20 pg. |
U.S. Appl. No. 11/948,342, Notice of Appeal and Appeal Brief, Jun. 16, 2010, 43 pg. |
U.S. Appl. No. 11/948,342, Examiner's Answer, Aug. 25, 2010, 23 pg. |
U.S. Appl. No. 11/948,342, Reply Brief, Oct. 25, 2010, 15 pg. |
U.S. Appl. No. 11/948,342, Decision on Appeal, Nov. 29, 2013, 9 pg. |
U.S. Appl. No. 11/948,342, Request for Rehearing, Jan. 29, 2014, 12 pg. |
U.S. Appl. No. 11/948,342, Decision on Reconsideration Request, Feb. 26, 014, 6 pg. |
U.S. Appl. No. 11/948,342, Non-Final Office Action, May 12, 2015, 8 pg. |
U.S. Appl. No. 14/292,869, Non-Final Office Action, May 21, 2015, 10 Pg. |
U.S. Appl. No. 14/293,083, Non-Final Office Action, Apr. 9 , 2015, 11 Pg. |
Number | Date | Country | |
---|---|---|---|
20140317208 A1 | Oct 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11948370 | Nov 2007 | US |
Child | 14293022 | US |