Linking business objects and documents

• US 10,585,947 B2
• Filed: 11/29/2017
• Issued: 03/10/2020
• Est. Priority Date: 06/22/2006
• Status: Active Grant

• Current Assignee: Open Text Corporation
• Original Assignee: Open Text Corporation
• Inventors: Walther, Michael H., Gavrysh, Viktor, Chaudhari, Sachin B.
• Primary Examiner(s): Lee, Bryan
• Application Number:
  US15/826,323
• Publication Number:
  US 20180081987A1
• Time in Patent Office: 832 Days
• CPC Class Codes: G06F 16/14 Details of searching files based on file metadata
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Managing content is disclosed. An indication is received that a content item comprising a body of managed content is associated with a business object not included in the body of managed content. The content item is linked with the business object.

Claims

1. A method of managing content comprising:

receiving, at a server, an indication that a content item in a body of managed content in a first repository used by a first application is associated with a business object in a second repository used by a second application and not included in the body of managed content;

using a processor, linking a content identifier identifying the content item to a business object identifier identifying the business object via a link, wherein linking the content identifier to the business object identifier comprises creating a link record containing the business object identifier and content identifier;

detecting, at the server, an event broadcast from the second application based on a user interaction at a client computer with an interface; and

in response to detecting the broadcast event, accessing the link using the business object identifier, determining the content identifier using the link and accessing the content item using the content identifier, the event broadcast including the business object identifier and an event type.

2. The method of claim 1, wherein the link is accessible from a document server.

3. The method of claim 1, wherein the link is accessible from a business server.

4. The method of claim 1, wherein access to the linked content item is provided automatically when an action is performed with respect to the business object.

5. The method of claim 1, wherein the linked content item is retrieved automatically when the business object is retrieved.

6. The method of claim 1, wherein accessing the content item comprises querying the first repository for documents linked to the business object identifier.

7. The method of claim 1, wherein creating the link record containing the business object identifier and content identifier comprises updating a table to associate the business object identifier and the content identifier.

8. The method of claim 1, wherein creating the link record containing the business object identifier and content identifier comprises creating a table to include the business object identifier and the content identifier.

9. A system for managing content comprising:

a processor; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to;

receive, at a server, an indication that a content item in a body of managed content in a first repository used by a first application is associated with a business object in a second repository used by a second application and not included in the body of managed content;

link a content identifier identifying the content item to a business object identifier identifying the business object via a link, wherein linking the content identifier to the business object identifier comprises creating a link record containing the business object identifier and content identifier;

detect an event broadcast from the second application; and

in response to detecting the broadcast event, access the link using the business object identifier, determine the content identifier using the link and access the content item using the content identifier, the event broadcast including the business object identifier, a type associated with the business object identifier and an event type.

10. The system of claim 9, wherein the link is accessible from a document server.

11. The system of claim 9, wherein the link is accessible from a business server.

12. The system of claim 9, wherein the processor is further configured to provide access to the linked content item automatically when an action is performed with respect to the business object.

13. The system of claim 9, wherein accessing the content item comprises querying the first repository for documents linked to the business object identifier.

14. The system of claim 9, wherein creating the link record containing the business object identifier and content identifier comprises updating a table to associate the business object identifier and the content identifier.

15. The system of claim 9, wherein creating the link record containing the business object identifier and content identifier comprises creating a table to include the business object identifier and the content identifier.

16. A non-transitory computer readable storage medium storing computer instructions for:

receiving, at a server, an indication that a content item in a body of managed content in a first repository used by a first application is associated with a business object in a second repository used by a second application and not included in the body of managed content;

using a processor, linking a content identifier identifying the content item to a business object identifier identifying the business object via a link, wherein linking the content identifier to the business object identifier comprises creating a link record containing the business object identifier and content identifier;

detecting, at the server, an event broadcast from an application; and

in response to detecting the broadcast event, accessing the link using the business object identifier, determining the content identifier using the link and accessing the content item using the content identifier, the event broadcast including the business object identifier and an event type.

17. The non-transitory computer readable storage medium of claim 16, wherein accessing the content item comprises querying the first repository for documents linked to the business object identifier.

18. The non-transitory computer readable storage medium of claim 16, wherein the link is accessible from a business server.

19. The non-transitory computer readable storage medium of claim 16, wherein the link is accessible from a document server.

20. The non-transitory computer readable storage medium of claim 16, further including instructions for automatically providing access to the linked content item when an action is performed with respect to the business object.

21. The non-transitory computer readable storage medium of claim 16, wherein accessing the content item comprises querying the first repository for documents linked to the business object identifier.

22. The non-transitory computer readable storage medium of claim 16, wherein creating the link record containing the business object identifier and content identifier comprises updating a table to include the business object identifier and the content identifier.

23. The non-transitory computer readable storage medium of claim 16, wherein creating the link record containing the business object identifier and content identifier comprises creating a table to include the business object identifier and the content identifier.