Example 2: Aggregated Process Step: In Processing
The following tables each show a section of the process activity log of the participating systems as well as the relevant process activity overview. The log and overview entries are fictitious and are shown in a simplified manner.
Process Activity Log System A:
Log Entry ID |
Business Process ID |
Message ID/Process Step ID |
Activity Status |
Name |
Message Direction |
Activity Category |
System ID |
Time Stamp |
|---|---|---|---|---|---|---|---|---|
Entry 1 |
BP1 |
S1 |
Started |
Create Loan Account |
Outgoing |
Service Call |
SysA |
Start Time |
Entry 1 System A sent a service call for the creation of of a loan account in System B by the application.
Process Activity Log System B:
Log Entry ID |
Business Process ID |
Message ID/Process Step ID |
Activity Status |
Name |
Message Direction |
Activity Category |
System ID |
Time Stamp |
|---|---|---|---|---|---|---|---|---|
Entry 2 |
BP1 |
S1 |
Started |
Create Loan Account |
Incoming |
Error processing |
SysB |
Start Time +1 |
Entry 2 System B has received the message. Because errors in processing occurred in System B, System B sent the message to the Error and Conflict Handler (CA-FS-ECH) application.
The entries logged in these two systems lead to the aggregated process step status In Processing for the underlying process step in the Process Activity Overview. The individual log entries are grouped as follows:
Message ID/Process Step ID |
Business Process ID |
Message ID/Process Step ID of the Predecessor |
Technical Reference ID |
Sender |
Recipient |
Aggregated Process Step Status |
Status History |
|---|---|---|---|---|---|---|---|
S1 |
BP1 |
- (No Predecessors) |
d0e4da50-4c2a-11de-8a39-0800200c9a66 |
SysA |
SysB |
In Processing |
Entry 1 and Entry 2 including all attributes |
The status history contains all the information about the individual log entries that the Process Step Journal used to derive the aggregated process step status for the preceding process step.