Case management integration with external content repositories

• US 10,346,850 B2
• Filed: 10/22/2013
• Issued: 07/09/2019
• Est. Priority Date: 10/22/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Babich, Alan F., Feng, Xin, Marin, Mike A., Roberts, Cynthia M., Vo, Mimi P., Yaung, Alan T.
• Primary Examiner(s): McAtee, Patrick
• Application Number:
  US14/060,091
• Publication Number:
  US 20140114865A1
• Time in Patent Office: 2,086 Days
• Field of Search: None
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• CPC Class Codes: G06F 16/1844 Management specifically adapted to replicated file systems
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 30/016 After-sales

Abstract

A case creation event originating from an external content repository is detected by a processor executing an inbound event handler of a distributed integration framework that integrates a case management system with the external content repository. The case creation event is configured by the distributed integration framework to cause creation of a case within the case management system. The inbound event handler instructs the case management system to create the case within the case management system. An outbound event handler of the distributed integration framework instructs the external content repository to create a proxy case to remotely represent the case created within the case management system.

Claims

1. A method, comprising:

by a programmed processor(s) set that executes an external content repository-to-case management system (ECR-CMS) event to application programming interface (event-to-API) converter and a case management system-to-external content repository (CMS-ECR) event-to-API converter of a distributed integration framework that, as executed, each performs one or more of protocol, security, and version (PSV) conversion(s) that operationally integrate a case management system with an external content repository, where the case management system and the external content repository are respectively implemented using heterogeneous platform technologies that prevent direct integration of the case management system and the external content repository;

detecting, via the ECR-CMS event-to-API converter, a case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause creation of a case to be managed by the case management system, where one or more content objects within the external content repository will be associated with the case;

controlling, via the ECR-CMS event-to-API converter by converting the detected case creation system event into a case creation application programming interface (API) control compatible with PSV requirements of the case management system, the case management system to create the case within the case management system;

detecting, via the CMS-ECR event-to-API converter, a case creation acknowledgement system event originating from the case management system that invokes the CMS-ECR event-to-API converter to cause creation within the external content repository of a proxy case representation to remotely represent case content object linkages associated with the case as the case is managed by the case management system; and

controlling, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into a proxy case creation API control compatible with PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository;

where the distributed integration framework, as executed, provides automated computer-controlled device integration that (i) propagates through additional system-event-to-API conversions any update(s) performed on the proxy case representation within the external content repository to the case management system that manages the case and (ii) propagates through additional system-event-to-API conversions any update(s) performed on proxy document representations associated with the case within the case management system to the external content repository that stores actual documents for the case, where each additional system-event-to-API conversion is performed independently of any protocol, security, and version differences of the respective heterogeneous platform technologies upon which the case management system and the external content repository are implemented.

2. The method of claim 1, where detecting, via the ECR-CMS event-to-API converter, the case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause the creation of the case to be managed by the case management system comprises:

detecting, via the ECR-CMS event-to-API converter, creation of a document within the external content repository.

3. The method of claim 2, where controlling, via the ECR-CMS event-to-API converter by converting the detected case creation system event into the case creation API control compatible with the PSV requirements of the case management system, the case management system to create the case within the case management system comprises controlling the case management system to create a case folder, and further comprising, via the ECR-CMS event-to-API converter by use of respective API controls of the case management system:

controlling the case management system to create a proxy document representation locally to remotely represent (i) the document created within the external content repository and (ii) case content document linkages created within the case management system associated with the document; and

controlling the case management system to add the proxy document representation to the case folder that creates a case content document linkage between the document in the external content repository and the case managed within the case management system.

4. The method of claim 2, where controlling, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into the proxy case creation API control compatible with the PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository further comprises:

controlling, via the CMS-ECR event-to-API converter, the external content repository to create a proxy case folder representation associated with the created proxy case representation.

5. The method of claim 4, further comprising controlling, via the CMS-ECR event-to-API converter, the external content repository to add the created document to the proxy case folder representation that creates a local case content document linkage between the document in the external content repository and the case managed within the case management system.

6. The method of claim 1, further comprising:

detecting, via the ECR-CMS event-to-API converter, a document removal system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause removal of a document from the case within the case management system; and

controlling, via the ECR-CMS event-to-API converter, the case management system to un-file the document from the case, where the case management system un-files a proxy document representation that represents the document in the external content repository from a case folder associated with the case responsive to the API control.

7. The method of claim 6, further comprising:

determining, via the ECR-CMS event-to-API converter, whether the proxy document representation is associated with at least one other case managed by the case management system; and

controlling, via the ECR-CMS event-to-API converter, the case management system to delete the proxy document representation in response to determining that the proxy document is not associated with the at least one other case managed by the case management system.

8. The method of claim 1, where the distributed integration framework, as executed, integrates the case management system with a plurality of heterogeneous external content repositories and implements a distinct paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter for each respective heterogeneous external content repository that are each specifically designed to perform one or more of the protocol, the security, and the version conversion(s) that integrate the case management system with each respective heterogeneous external content repository, where the method further comprises for each paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter:

controlling, via the inbound event handler respective ECR-CMS event-to-API converter, the case management system to perform application-level processing associated with system events originating from the respective heterogeneous external content repository; and

controlling, via the respective CMS-ECR event-to-API converter, the respective heterogeneous external content repository to perform application-level processing associated with system events originating from the case management system.

9. A system, comprising:

a processor(s) set programmed to;

execute an external content repository-to-case management system (ECR-CMS) event-to-API converter and a case management system-to-external content repository (CMS-ECR) event-to-API converter of a distributed integration framework that, as executed, each performs one or more of protocol, security, and version (PSV) conversion(s) that operationally integrate a case management system with an external content repository, where the case management system and the external content repository are respectively implemented using heterogeneous platform technologies that prevent direct integration of the case management system and the external content repository;

the processor(s) set being further programmed to;

detect, via the ECR-CMS event-to-API converter, a case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause creation of a case to be managed by the case management system, where one or more content objects within the external content repository will be associated with the case;

control, via the ECR-CMS event-to-API converter by converting the detected case creation system event into a case creation application programming interface (API) control compatible with PSV requirements of the case management system, the case management system to create the case within the case management system;

detect, via the CMS-ECR event-to-API converter, a case creation acknowledgement system event originating from the case management system that invokes the CMS-ECR event-to-API converter to cause creation within the external content repository of a proxy case representation to remotely represent case content object linkages associated with the case as the case is managed by the case management system; and

control, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into a proxy case creation API control compatible with PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository;

where the distributed integration framework, as executed, provides automated computer-controlled device integration that (i) propagates through additional system-event-to-API conversions any update(s) performed on the proxy case representation within the external content repository to the case management system that manages the case and (ii) propagates through additional system-event-to-API conversions any update(s) performed on proxy document representations associated with the case within the case management system to the external content repository that stores actual documents for the case, where each additional system-event-to-API conversion is performed independently of any protocol, security, and version differences of the respective heterogeneous platform technologies upon which the case management system and the external content repository are implemented.

10. The system of claim 9, where in being programmed to detect, via the ECR-CMS event-to-API converter, the case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause the creation of the case to be managed by the case management system, the processor(s) set is programmed to:

detect, via the ECR-CMS event-to-API converter, creation of a document within the external content repository.

11. The system of claim 10, where in being programmed to control, via the ECR-CMS event-to-API converter by converting the detected case creation system event into the case creation API control compatible with the PSV requirements of the case management system, the case management system to create the case within the case management system, the processor(s) set is programmed to control the case management system to create a case folder, and the processor(s) set is further programmed to, via the ECR CMS event-to-API converter by use of respective API controls of the case management system:

control the case management system to create a proxy document representation locally to remotely represent (i) the document created within the external content repository and (ii) case content document linkages created within the case management system associated with the document; and

control the case management system to add the proxy document representation to the case folder that creates a case content document linkage between the document in the external content repository and the case managed within the case management system.

12. The system of claim 10, where in being programmed to control, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into the proxy case creation API control compatible with the PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository, the processor(s) set is further programmed to:

control, via the CMS-ECR event-to-API converter, the external content repository to create a proxy case folder representation associated with the created proxy case representation.

13. The system of claim 12, where the processor(s) set is further programmed to control, via the CMS-ECR event-to-API converter, the external content repository to add the created document to the proxy case folder representation that creates a local case content document linkage between the document in the external content repository and the case managed within the case management system.

14. The system of claim 9, where the processor(s) set is further programmed to:

detect, via the ECR-CMS event-to-API converter, a document removal system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause removal of a document from the case within the case management system; and

control, via the ECR-CMS event-to-API converter, the case management system to un-file the document from the case, where the case management system un-files a proxy document representation that represents the document in the external content repository from a case folder associated with the case responsive to the API control.

15. The system of claim 14, where the processor(s) set is further programmed to:

determine, via the ECR-CMS event-to-API converter, whether the proxy document representation is associated with at least one other case managed by the case management system; and

control, via the ECR-CMS event-to-API converter, the case management system to delete the proxy document representation in response to determining that the proxy document is not associated with the at least one other case managed by the case management system.

16. The system of claim 9, where the distributed integration framework, as executed, integrates the case management system with a plurality of heterogeneous external content repositories and implements a distinct paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter for each respective heterogeneous external content repository that are each specifically designed to perform one or more of the protocol, the security, and the version conversion(s) that integrate the case management system with each respective heterogeneous external content repository, where for each paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter:

the processor(s) set is programmed to control, via the respective ECR-CMS event-to-API converter, the case management system to perform application-level processing associated with system events originating from the respective heterogeneous external content repository; and

the processor(s) set is programmed to control, via the respective CMS-ECR event-to-API converter, the respective heterogeneous external content repository to perform application-level processing associated with system events originating from the case management system.

17. A computer program product, comprising:

a computer readable storage device having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to;

execute an external content repository-to-case management system (ECR-CMS) event-to-API converter and a case management system-to-external content repository (CMS-ECR) event-to-API converter of a distributed integration framework that, as executed, each performs one or more of protocol, security, and version (PSV) conversion(s) that operationally integrate a case management system with an external content repository, where the case management system and the external content repository are respectively implemented using heterogeneous platform technologies that prevent direct integration of the case management system and the external content repository;

detect, via the ECR-CMS event-to-API converter, a case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause creation of a case to be managed by the case management system, where one or more content objects within the external content repository will be associated with the case;

instruct control, via the ECR-CMS event-to-API converter by converting the detected case creation system event into a case creation application programming interface (API) control compatible with PSV requirements of the case management system, the case management system to create the case within the case management system;

detect, via the CMS-ECR event-to-API converter, a case creation acknowledgement system event originating from the case management system that invokes the CMS-ECR event-to-API converter to cause creation within the external content repository of a proxy case representation to remotely represent case content object linkages associated with the case as the case is managed by the case management system; and

control, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into a proxy case creation API control compatible with PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository;

where the distributed integration framework, as executed, provides automated computer-controlled device integration that (i) propagates through additional system-event-to-API conversions any update(s) performed on the proxy case representation within the external content repository to the case management system that manages the case and (ii) propagates through additional system-event-to-API conversions any update(s) performed on proxy document representations associated with the case within the case management system to the external content repository that stores actual documents for the case, where each additional system-event-to-API conversion is performed independently of any protocol, security, and version differences of the respective heterogeneous platform technologies upon which the case management system and the external content repository are implemented.

18. The computer program product of claim 17, where in causing the computer to detect, via the ECR-CMS event-to-API converter, the case creation system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause the creation of the case within to be managed by the case management system, the computer readable program code when executed on the computer causes the computer to:

detect, via the ECR-CMS event-to-API converter, creation of a document within the external content repository.

19. The computer program product of claim 18, where in causing the computer to control, via the ECR-CMS event-to-API converter by converting the detected case creation system event into the case creation API control compatible with the PSV requirements of the case management system, the case management system to create the case within the case management system, the computer readable program code when executed on the computer causes the computer to control the case management system to create a case folder, and the computer readable program code when executed on the computer further causes the computer, via the ECR-CMS event-to-API converter by use of respective API controls of the case management system, to:

control the case management system to create a proxy document representation locally to remotely represent (i) the document created within the external content repository and (ii) case content document linkages created within the case management system associated with the document; and

control the case management system to add the proxy document representation to the case folder that creates a case content document linkage between the document in the external content repository and the case managed within the case management system.

20. The computer program product of claim 18, where in causing the computer to control, via the CMS-ECR event-to-API converter by converting the detected case creation acknowledgement system event into the proxy case creation API control compatible with the PSV requirements of the external content repository, the external content repository from which the detected case creation system event originated to create the proxy case representation within the external content repository, the computer readable program code when executed on the computer causes the computer to:

control, via the CMS-ECR event-to-API converter, the external content repository to create a proxy case folder representation associated with the created proxy case representation.

21. The computer program product of claim 20, where the computer readable program code when executed on the computer further causes the computer to control, via the CMS-ECR event-to-API converter, the external content repository to add the created document to the proxy case folder representation that creates a local case content document linkage between the document in the external content repository and the case managed within the case management system.

22. The computer program product of claim 17, where the computer readable program code when executed on the computer further causes the computer to:

detect, via the ECR-CMS event-to-API converter, a document removal system event originating from the external content repository that invokes the ECR-CMS event-to-API converter to cause removal of a document from the case within the case management system; and

control, via the ECR-CMS event-to-API converter, the case management system to un-file the document from the case, where the case management system un-files a proxy document representation that represents the document in the external content repository from a case folder associated with the case responsive to the API control.

23. The computer program product of claim 22, where the computer readable program code when executed on the computer further causes the computer to:

determine, via the ECR-CMS event-to-API converter, whether the proxy document representation is associated with at least one other case managed by the case management system; and

control, via the ECR-CMS event-to-API converter, the case management system to delete the proxy document representation in response to determining that the proxy document is not associated with the at least one other case managed by the case management system.

24. The computer program product of claim 17, where the distributed integration framework, as executed, integrates the case management system with a plurality of heterogeneous external content repositories and implements a distinct paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter for each respective heterogeneous external content repository that are each specifically designed to perform one or more of the protocol, the security, and the version conversion(s) that integrate the case management system with each respective heterogeneous external content repository, where for each paired ECR-CMS event-to-API converter and CMS-ECR event-to-API converter the computer readable program code when executed on the computer further causes the computer to:

control, via the respective ECR-CMS event-to-API converter, the case management system to perform application-level processing associated with system events originating from the respective heterogeneous external content repository; and

control, via the respective CMS-ECR event-to-API converter, the respective heterogeneous external content repository to perform application-level processing associated with system events originating from the case management system.