Example 3: Aggregated Process Step Status Obsolete
The following tables 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 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 |
Event Processing |
SysA |
Start Time |
Entry 2 |
BP1 |
S1 |
Completed |
Create Loan Account |
Outgoing |
Event Processing |
SysA |
Start Time +1 |
Entry 1 The application in System A has created a loan account. The Change Notification Service has written a change pointer about this event.
Entry 2 An agent of the application Agent Framework (FS-FND-AF) reacts to the event Create Loan Account and sets the status of the change pointer to Completed in the Change Notification Service (CA-GTF-TS-CNS). The Process Step Journal reads the status change data from the Change Notification Service and displays it in the log.
The entries logged in System A lead to the aggregated process step status Obsolete for the underlying process step in the Process Activity Overview. This event is now no longer relevant for other systems. 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 |
– |
Obsolete |
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.