-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
4
-
Not defined
In certain situations it becomes necessary to reimport data from the process engine.
This is e.g. the case when we add new features (e.g. incident information) or new aggregations that require new data from the engine.
In certain scenarios the engine does not have the data anymore (e.g. because of history cleanup).
From Optimize perspective I still would like to use all the new functionality - even for old data - so that I do not have to reimport from the engine where the data does not exist anymore.
Potential solutions include:
- copy of engine history (Relational)
- raw history from engine in elastic without aggregations (complete dump)
This is the controller panel for Smart Panels app
[OPT-3688] (Data Warehouse) Make sure reimport from engine is not necessary
| Description |
Original:
What are the steps to reproduce your problem?
What is the problem? What would be the expected behavior: Hints (optional): |
New:
In certain situations it becomes necessary to reimport data from the process engine. This is e.g. the case when we add new features (e.g. incident information) or new aggregations that require new data from the engine. In certain scenarios the engine does not have the data anymore (e.g. because of history cleanup). From Optimize perspective I still would like to use all the new functionality - even for old data - so that I do not have to reimport from the engine where the data does not exist anymore. Potential solutions include: * copy of engine history (Relational) * raw history from engine in elastic without aggregations (complete dump) |
| Mentioned Roles |
| Mentioned Groups |
| Link | New: This issue is related to SUPPORT-7136 [ SUPPORT-7136 ] |
| Effort | New: Not defined [ 11259 ] |
| Epic Link | New: OPT-3745 [ 52417 ] |
| PM Priority | New: 3 |
| Labels | New: SUPPORT |
| Mentioned Roles |
| Mentioned Groups |