...
Currently this tool is only usable for development because it reads directly from the trace database, you should not run this tool on a live production database because it affects the performance on the Blueriq Runtime that is connected to this database.
Example
This is what a possible result in Disco when you use the trace-events from a simple Blueriq DCM application based on the DCM foundation:
Image Added
| Expand |
|---|
| title | Example XES file. Click here to expand... |
|---|
|
| Code Block |
|---|
| <?xml version="1.0" encoding="UTF-8" ?>
<!-- This file has been generated with Blueriq. -->
<!-- It conforms to the XML serialization of the XES standard for log storage and management.-->
<!-- XES standard version: 1.4 -->
<log xes.version="1.4" xes.features="nested-attributes" openxes.version="1.0RC7" xmlns="http://www.xes-standard.org/">
<extension name="Concept" prefix="concept" uri="http://www.xes-standard.org/concept.xesext"/>
<extension name="Time" prefix="time" uri="http://www.xes-standard.org/time.xesext"/>
<extension name="Organizational" prefix="org" uri="http://www.xes-standard.org/org.xesext"/>
<extension name="Identity" prefix="identity" uri="http://www.xes-standard.org/identity.xesext"/>
<extension name="Lifecycle" prefix="lifecycle" uri="http://www.xes-standard.org/lifecycle.xesext"/>
<extension name="Semantic" prefix="semantic" uri="http://www.xes-standard.org/semantic.xesext"/>
<global scope="trace">
<string key="concept:name" value="defaultname"/>
<string key="identity:id" value="defaultid"/>
</global>
<global scope="event">
<date key="time:timestamp" value="2010-12-17T20:01:02.229+02:00"/>
<string key="concept:name" value="defaultname"/>
<string key="org:resource" value="defaultresource"/>
<string key="lifecycle:transition" value="transition"/>
<string key="semantic:modelReference" value="process"/>
</global>
<string key="lifecycle:model" value="standard"/>
<classifier name="Activity" keys="concept:name"/>
<classifier name="Resource" keys="org:resource"/>
<trace>
<string key="identity:id" value="1"/>
<string key="concept:name" value="InitieerNieuwProces 1"/>
<event>
<string key="concept:name" value="IndienenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:54:12.287+00:00"/>
<string key="org:resource" value="Aanvrager"/>
<string key="lifecycle:transition" value="schedule"/>
<string key="semantic:modelReference" value="task"/>
</event>
<event>
<string key="concept:name" value="IndienenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:54:14.838+00:00"/>
<string key="org:resource" value="Aanvrager"/>
<string key="lifecycle:transition" value="start"/>
<string key="semantic:modelReference" value="task"/>
</event>
<event>
<string key="concept:name" value="IndienenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:54:19.884+00:00"/>
<string key="org:resource" value="Aanvrager"/>
<string key="lifecycle:transition" value="complete"/>
<string key="semantic:modelReference" value="task"/>
</event>
<event>
<string key="concept:name" value="BeoordelenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:54:20.079+00:00"/>
<string key="org:resource" value="Aanvrager"/>
<string key="lifecycle:transition" value="schedule"/>
<string key="semantic:modelReference" value="task"/>
</event>
<event>
<string key="concept:name" value="BeoordelenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:54:58.807+00:00"/>
<string key="org:resource" value="Behandelaar"/>
<string key="lifecycle:transition" value="start"/>
<string key="semantic:modelReference" value="task"/>
</event>
<event>
<string key="concept:name" value="BeoordelenAanvraag"/>
<date key="time:timestamp" value="2019-04-16T14:55:08.018+00:00"/>
<string key="org:resource" value="Behandelaar"/>
<string key="lifecycle:transition" value="complete"/>
<string key="semantic:modelReference" value="task"/>
</event>
</trace>
</log> |
|
Improve
Missing events in the trace log when mining? Please create an feature request so we can add it: Support Desk.
...