Correlating process instance data across multiple applications

• US 7,693,916 B2
• Filed: 01/05/2004
• Issued: 04/06/2010
• Est. Priority Date: 01/05/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jason, Richard Zachary, Chkodrov, Gueorgui Bonov, Reel, Eric Anthony
• Primary Examiner(s): Cottingham; John R.
• Assistant Examiner(s): TIMBLIN, ROBERT M
• Application Number:
  US10/750,885
• Publication Number:
  US 20050149475A1
• Time in Patent Office: 2,283 Days
• Field of Search: 707/104.1, 705/35
• US Class Current: 707/804
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Abstract

Instance data is transmitted for Payload/Milestone events and for Enable-Continuation events. Payload/Milestone event data contains information describing an instance and/or providing a time of one or more portions of the processing of an instance. Included in the Enable-Continuation event data is an identifier associated with an instance by a first application and an identifier associated with the same instance by another application. The identifiers are placed in a continuation data table which is used to index the appropriate record of an instance data table. Out-of-order data for an instance is hidden from view until sequentially prior data for the instance is received.

Claims

1. In a system that includes a plurality of applications that perform different portions of a business process and that each represent data of the business process using a different identifier, a method for correlating the data of an instance of the business process generated by the applications, the method being performed by a processor in the system, the method comprising:

subsequent to a first application performing a portion of the business process, receiving first data from the first application that was generated during the performance of the business process, the first data being represented with a first identifier;

creating a record in an instance data table that stores the first identifier and the first data in fields of the record, the record including additional fields for data to be subsequently received, wherein the first identifier is stored in the record such that data entered into the additional fields is represented by the first identifier;

subsequent to the first application completing its portion of the business process, receiving a correlation event that includes the first identifier and a second identifier, the second identifier corresponding to a second application that performs a subsequent portion of the business process such that the second application represents data generated during the performance of the subsequent portion of the business process using the second identifier, the first identifier being different from the second identifier;

creating a record in a continuation data table that stores the first identifier in conjunction with the second identifier;

subsequent to the second application performing the subsequent portion of the business process, receiving second data from the second application that was generated during the performance of the business process, the second data being represented with the second identifier;

accessing the record in the continuation data table to determine that the second data represented by the second identifier corresponds with the first data stored in the record of the instance data table and represented by the first identifier;

storing the second data in the additional fields of the record in the instance data table such that the second data is also represented by the first identifier;

subsequent to the second application completing its portion of the business process, receiving a correlation event that includes the second identifier and a third identifier, the third identifier corresponding to a third application that performs a subsequent portion of the business process such that the third application represents data generated during the performance of the subsequent portion of the business process using the third identifier, the third identifier being different than the first and second identifiers;

searching the continuation data table for a record that includes the second identifier;

determining based on the record stored in the continuation data table that the second identifier is correlated with the first identifier

creating a new record in the continuation data table that correlates the first identifier with the third identifier;

subsequent to the third application performing the subsequent portion of the business process, receiving third data from the third application that was generated during the performance of the business process, the third data being represented with the third identifier;

accessing the record in the continuation table that stores the first and third identifiers to determine that the third data represented by the third identifier corresponds with the first data stored in the record of the instance data table and represented by the first identifier; and

storing the third data in the additional fields of the record in the instance data table such that the third data is also represented by the first identifier.

2. The method of claim 1 further comprising upon creating the new record, deleting the record that stores the first and second identifiers from the continuation data table.

3. The method of claim 1 wherein the first application receives the second identifier from the second application and the second application receives the third identifier from the third application, but no other communications occur between the applications.

4. A non-transient computer readable storage medium that stores computer executable instructions which when executed by a processor perform the method of any of claims 1-3.

5. In a system that includes a plurality of applications that perform different portions of a business process and that each represent data of the business process using a different identifier, a method for correlating the data of an instance of the business process generated by the applications, the method being performed by a processor in the system, the method comprising:

subsequent to an application performing a portion of the business process, receiving data from the application that was generated during the performance of the business process, the data being represented with an identifier;

searching a continuation data table, that stores correlated identifiers, for a record that includes the identifier such that;

upon locating a record that includes the identifier, a correlating identifier is retrieved from the record and used to locate a record in an instance data table that includes data represented by the correlating identifier, and upon locating the record in the instance data table, the data represented by the identifier is inserted into the record in the instance data table; and

upon failing to locate a record that includes the identifier, a new record is added to the instance data table that includes the data and the identifier;

subsequent to the application completing its portion of the business process, receiving a correlation event that includes the identifier and a subsequent identifier, the subsequent identifier corresponding to a subsequent application that performs a subsequent portion of the business process such that the subsequent application represents data generated during the performance of the subsequent portion of the business process using the subsequent identifier, the identifier being different from the subsequent identifier; and

searching the continuation data table for a record that includes the identifier in conjunction with a different identifier such that;

upon locating a record that includes the identifier, a new record is added to the continuation data table that correlates the different identifier with the subsequent identifier; and

upon failing to locate a record that includes the identifier, a new record is added to the continuation data table that correlates the identifier with the subsequent identifier.

6. The method of claim 5 wherein the different identifier corresponds with a first application, the identifier corresponds with a second application, and the subsequent identifier corresponds with a third application, wherein the first application performs a beginning portion of the business process, the second application performs an intermediate portion of the business process, and the third application performs an ending portion of the business process.

7. The method of claim 5 wherein the record in the instance data field further includes a first field for indicating whether the data in the record is visible to outside entities, and a second field for indicating whether the application corresponding to the identifier included in the record has completed it'"'"'s portion of the business process.

8. The method of claim 7 wherein the first field being set indicates that the record stores data from an application that performs a portion of the business process that is performed after a preceding portion for which no data has been received.

9. The method of claim 7 wherein if the first field is set, the data of the record will not be returned in response to a query that matched the data.

10. The method of claim 5 wherein the portion of the business process performed by the application includes multiple actions that each generate data, and wherein the generated data from all the actions are received in a batch that is pre-sorted by the application.

11. A non-transient computer readable storage medium that stored computer executable instructions which when executed by a processor perform the method of any of claims 5-10.