Page History
plugin-tracedao/target/TraceDao-Plugin-9.zip
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 plugintimeline component (Trace SQL Store component). With this plugin component, it is possible to store timeline entries from tasks, cases, documents and events. For storage there are two ways: either in memory or in file. The former can hold its information only during the session - after the session expires, the information is lost. The latter stores the information in the traceability database table. . The timeline container reads its information from the stored entries.
This container type uses the content style 'timeline'.
Max results
By default, the number of timeline entries is limited to 100, to prevent a huge impact on memory and performance when the database contains a lot of entries (which apply to the filter). You can override this default by setting the following property:
Code Block |
---|
blueriq.timeline.max-results=10 |
Parameters
Name | Description | Type | Required |
---|---|---|---|
Case ID | The case id for which you want to show the timeline. | Expression - Any | No |
User ID | The | ||
user id for which you want to show the timeline. | Expression - String | ||
No | |||
Display for period | A datetime that indicates the start of the period up to the current date, empty means unlimited. | Expression - Any | |
No | |||
Show cases | If case events are shown in the timeline. | Boolean | |
No | |||
Show tasks | If task events are shown in the timeline. | Boolean | |
No | |||
Show message events | If message events are shown in the timeline. | Boolean | |
No | |||
Show documents | If document events are shown in the timeline. | Boolean | |
No |
Info |
---|
When the |
...
Document specific Parameters
...
...
...
...
...
Case ID, User ID or Display for period parameter expression evaluate to unknown at runtime, an empty timeline is shown to prevent performance issues. This also happens when the Case ID or User ID parameter evaluates to an empty list at runtime. |