Case management integration with external content repositories
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
exact text as granted — not AI-modified1 .- 8 . (canceled)
9 . A system, comprising:
a distributed integration framework that integrates a case management system with an external content repository; and a processor programmed to:
detect, at an inbound event handler of the distributed integration framework, a case creation event originating from the external content repository that is configured via the distributed integration framework to cause creation of a case within the case management system;
instruct, via the inbound event handler, the case management system to create the case within the case management system; and
instruct, via an outbound event handler, the external content repository to create a proxy case to remotely represent the case created within the case management system.
10 . The system of claim 9 , where in being programmed to detect, at the inbound event handler of the distributed integration framework, the case creation event originating from the external content repository that is configured via the distributed integration framework to cause the creation of the case within the case management system, the processor is programmed to:
detect, at the inbound event handler of the distributed integration framework, creation of a document within the external content repository.
11 . The system of claim 10 , where in being programmed to instruct, via the inbound event handler, the case management system to create the case within the case management system, the processor is programmed to instruct the case management system to create a case folder, and the processor is further programmed to:
instruct the case management system to create a proxy document locally to represent the document created within the external content repository; and instruct the case management system to add the proxy document to the case folder.
12 . The system of claim 10 , where in being programmed to instruct, via the outbound event handler of the distributed integration framework, the external content repository to create the proxy case to remotely represent the case created within the case management system, the processor is programmed to:
instruct, via the outbound event handler, the external content repository to create a proxy case folder associated with the created proxy case.
13 . The system of claim 12 , where the processor is further programmed to instruct, via the outbound event handler, the external content repository to add the created document to the proxy case folder.
14 . The system of claim 9 , where the processor is further programmed to:
detect, at the inbound event handler, a document removal event originating at the external content repository that is configured via the distributed integration framework to cause removal of a document from a case within the case management system; and instruct, via the inbound event handler, the case management system to un-file the document from the case, where the case management system un-files a proxy document that represents the document from a case folder associated with the case responsive to the instruction.
15 . The system of claim 14 , where the processor is further programmed to:
determine, via the inbound event handler, whether the proxy document is associated with at least one other case managed by the case management system; and instruct the case management system to delete the proxy document 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 integrates the case management system with a plurality of heterogeneous external content repositories and implements a paired inbound event handler and outbound event handler for each heterogeneous external content repository, where for each paired inbound event handler and outbound event handler:
the processor is programmed to instruct, via the inbound event handler, the case management system to perform application-level processing associated with events originating from the paired heterogeneous external content repository; and the processor is programmed to instruct, via the outbound event handler, the paired heterogeneous external content repository to perform application-level processing associated with events originating from the case management system.
17 . A computer program product, comprising:
a computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to:
detect, via an inbound event handler of a distributed integration framework that integrates a case management system with an external content repository, a case creation event originating from the external content repository that is configured via the distributed integration framework to cause creation of a case within the case management system;
instruct, via the inbound event handler, the case management system to create the case within the case management system; and
instruct, via an outbound event handler of the distributed integration framework, the external content repository to create a proxy case to remotely represent the case created within the case management system.
18 . The computer program product of claim 17 , where in causing the computer to detect, via the inbound event handler of the distributed integration framework that integrates the case management system with the external content repository, the case creation event originating from the external content repository that is configured via the distributed integration framework to cause the creation of the case within the case management system, the computer readable program code when executed on the computer causes the computer to:
detect, via the inbound event handler of the distributed integration framework, creation of a document within the external content repository.
19 . The computer program product of claim 18 , where in causing the computer to instruct, via the inbound event handler, 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 instruct the case management system to create a case folder, and the computer readable program code when executed on the computer further causes the computer to:
instruct the case management system to create a proxy document locally to represent the document created within the external content repository; and instruct the case management system to add the proxy document to the case folder.
20 . The computer program product of claim 18 , where in causing the computer to instruct, via the outbound event handler of the distributed integration framework, the external content repository to create the proxy case to remotely represent the case created within the case management system, the computer readable program code when executed on the computer causes the computer to:
instruct, via the outbound event handler, the external content repository to create a proxy case folder associated with the created proxy case.
21 . The computer program product of claim 20 , where the computer readable program code when executed on the computer further causes the computer to instruct, via the outbound event handler, the external content repository to add the created document to the proxy case folder.
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, at the inbound event handler, a document removal event originating at the external content repository that is configured via the distributed integration framework to cause removal of a document from a case within the case management system; and instruct, via the inbound event handler, the case management system to un-file the document from the case, where the case management system un-files a proxy document that represents the document from a case folder associated with the case responsive to the instruction.
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 inbound event handler, whether the proxy document is associated with at least one other case managed by the case management system; and instruct the case management system to delete the proxy document 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 integrates the case management system with a plurality of heterogeneous external content repositories and implements a paired inbound event handler and outbound event handler for each heterogeneous external content repository, where for each paired inbound event handler and outbound event handler:
the inbound event handler instructs the case management system to perform application-level processing associated with events originating from the paired heterogeneous external content repository; and the outbound event handler instructs the paired heterogeneous external content repository to perform application-level processing associated with events originating from the case management system.Join the waitlist — get patent alerts
Track US2014114864A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.