-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
With Zeebe data exported to the Optimize Elasticsearch instance, Optimize should then convert this data to be usable in reports. Initially, the focus should be on making process instance and flow node reports evaluable (which also depends on deployments). As a stretch goal, we should also try to import User Tasks. Variables and Incidents are both considered lower priority for the immediate plans.
ATs:
- Process instance data is available in reports
- Flow node data is available in reports
- Optimize can be restarted and the import resumes from the same point as it left off
- (Stretch goal) User task data is available in reports
Hints:
- It is likely that Optimize needs to be configured to know where to communicate with the Zeebe instance that is the source of the data
This is the controller panel for Smart Panels app
- mentioned in
-
Page Loading...
1.
|
Zeebe Deployments are imported as Optimize process definitions |
|
Done | Unassigned |
2.
|
Zeebe Process instances are imported as Optimize process instances |
|
Done | Unassigned |
3.
|
Zeebe Importer metadata is saved in Elasticsearch |
|
Done | Unassigned |
4.
|
Optimize can configure a scheduler for a Zeebe data source |
|
Done | Unassigned |
5.
|
Clean up Zeebe templates before/after ITs finish |
|
Done | Unassigned |
6.
|
Save import data to definitions |
|
Done | Unassigned |
7.
|
Store full engine data as part of process instance DTO |
|
Done | Unassigned |