L3 - Default Context:
- given:
- A Camunda Engine running
- I have running process instances that have running activity instances
- when:
- I configure the the connection to the engine in Optimize and
- I start Optimize
- then:
- the running activity instances are imported to Optimize
AT:
- running activity instances are imported
- the dynamic and static import performance tests are extended such that they also test this behavior
- the import overview section in the technical guide has a comment saying that this is actually the case
- it should be tested that the view flow node frequency grouped by flow node report also accounts the running activity instances
This is the controller panel for Smart Panels app
[OPT-1569] Import running activity instances
| Description |
Original:
*AT:*
* given: ** A Camunda Engine running ** I have a DMN tables in my process definition diagrams ** the DMN tables are executed in the engine and the history is set to full so that DMN history data is being produced and stored in the database * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the historic DMN data is imported to Optimize |
New:
*Context:*
* given: ** A Camunda Engine running ** I have running process instances that have running activity instances * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the running activity instances are imported to Optimize *AT:* * |
| Description |
Original:
*Context:*
* given: ** A Camunda Engine running ** I have running process instances that have running activity instances * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the running activity instances are imported to Optimize *AT:* * |
New:
*Context:*
* given: ** A Camunda Engine running ** I have running process instances that have running activity instances * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the running activity instances are imported to Optimize *AT:* * running activity instances are imported * the dynamic and static import performance tests are extended such that they also test this behavior * the [import overview section|https://docs.camunda.org/optimize/latest/technical-guide/import/import-overview/] in the technical guide has a comment saying that this is actually the case |
| Description |
Original:
*Context:*
* given: ** A Camunda Engine running ** I have running process instances that have running activity instances * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the running activity instances are imported to Optimize *AT:* * running activity instances are imported * the dynamic and static import performance tests are extended such that they also test this behavior * the [import overview section|https://docs.camunda.org/optimize/latest/technical-guide/import/import-overview/] in the technical guide has a comment saying that this is actually the case |
New:
*Context:*
* given: ** A Camunda Engine running ** I have running process instances that have running activity instances * when: ** I configure the the connection to the engine in Optimize and ** I start Optimize * then: ** the running activity instances are imported to Optimize *AT:* * running activity instances are imported * the dynamic and static import performance tests are extended such that they also test this behavior * the [import overview section|https://docs.camunda.org/optimize/latest/technical-guide/import/import-overview/] in the technical guide has a comment saying that this is actually the case * it should be tested that the view flow node frequency grouped by flow node report also accounts the running activity instances |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12306 ] |
| Remote Link | Original: This issue links to "Page (camunda confluence)" [ 12306 ] |
| Labels | New: current_release |
| Status | Original: Open [ 1 ] | New: In Development [ 10312 ] |
| Assignee | Original: Johannes [ johannes.heinemann ] | New: Sebastian Bathke [ sebastian.bathke ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Status | Original: In Review [ 10212 ] | New: Ready to implement [ 10000 ] |