Context:
We currently have definition functionality spread across 3 root paths `process-definition`, `decision-definition` & `definition` while the latter is generic.
We should evaluate consolidating all functionalities into the generic `definition` endpoint.
AT:
- `process-definition`, `decision-definition` endpoints are removed and their functionality is covered by the `definition` endpoint
- frontend has migrated to the new endpoint (we may keep the old one till this is done and have a dedicated follow-up task to remove the deprecated endpoints)
Hint:
Considering the generic definition endpoint is not yet supporting tenant and version grouping we need to extend it before we can migrate to it, this is related to OPT-2871. We should consider what approach makes more sense, first doing OPT-2871 and then merging the functionality into the generic endpoint or leaving the existing process/decision definition endpoint implementations as they are and rather extending only the generic one in the scope of this task with the required tenant/version grouping and then skipping OPT-2871 entirely.
This is the controller panel for Smart Panels app
- depends on
-
OPT-2871 Create definition tenant and version grouping with an elasticsearch aggregation
- Done
- is depended on by
-
OPT-3373 Test that fetching of definitions work for DMN 1.2/1.3 diagrams as well
- Done
-
OPT-3352 Migrate frontend to new generic definitions endpoint
- Done
- is related to
-
OPT-2871 Create definition tenant and version grouping with an elasticsearch aggregation
- Done