-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
2
-
M
-
3 - Expected
The Cloud team is migrating from ProcessInstanceID to ProcessInstanceKey to ensure a consistent experience across all components. Since Optimize is also deployed alongside these, we should use the Cloud terminology in the UI.
As a majority of our users are in Platform and Cloud APIs are not exposed, we don't need to change the Optimize backend in this iteration.
Hints:
- We should thoroughly go through the UI and find cases where there are inconsistencies. Perhaps cigdem.ilhan could help here, as she has good visibility across products and knowledge of Optimize
- We could also align at storage level and make sure that our reference to IDs/keys are consistent with Camunda 8 rather than 7 in the case of differences. This can also be handled later in a follow-up BE ticket
Justification:
Reduce confusion for the user when creating optimize entities
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10366. Please use this link for any future references and continue any discussion there.