You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.

(plus)Trace SQL Store component

This container is able to show you a timeline of events. You can set a filter for a specific case and time period. To use this functionality, you need the trace engine component. With this component, it is possible to store trace data from tasks, cases, documents and events. The timeline container reads its information from the traceability database table. This container type uses the content style 'timeline'.

Parameters

Name
Description
Type
Required
Case IDThe case id for which you want to show the timeline.Expression - Anyfalse
User IDThe user id for which you want to show the timeline.Expression - Stringfalse
Display for periodA datetime that indicates the start of the period up to the current date, empty means unlimited.Expression - Anyfalse
Show casesIf case events are shown in the timeline.Booleanfalse
Show tasksIf task events are shown in the timeline.Booleanfalse
Show message eventsIf message events are shown in the timeline.Booleanfalse
Show documentsIf document events are shown in the timeline.Booleanfalse


When the container is configured to show document events on the timeline (using the "Show documents" parameter described above), two additional parameters can be use to further configure the container.

When the Case ID, User ID or Display for period parameter expression evaluate to unknown at runtime, an empty timeline is shown to prevent performance issues.


Document specific Parameters (until 13.11)

Name
Description
Type
Required
ConnectionsThe connection identifier(s) for which to show document events in the timeline.multi-valued Stringfalse
Show entries for unknown connectionsIf documents events that have no connection identifier are shown in the timeline.Booleanfalse


In 13.11, the memory backed implementation of the Timeline container has been removed. This implementation was not accessible since Blueriq 10, and it was not suitable for production scenarios. The Document specific Parameters mentioned above were only used by the memory implementation, so they have been removed from Studio as well.