In https://app.camunda.com/jira/browse/OPT-2463 and https://app.camunda.com/jira/browse/OPT-2736, the report, dashboard and collection creation endpoints were changed to accept definitions in the body of the request. Previously, entities were created empty and the definitions provided in a subsequent update request. Once the FE starts creating reports this way, we should refactor all of our integration tests that are creating reports to do similar, for two reasons:
- To make our tests mimic real behaviour
- So we can remove the collectionId from the request and all entities be created in a similar way
As a bonus, we can probably do some refactoring to tidy up report creating/updating in tests. There is a lot of repetition across tests that can be extracted.
AT:
- the collectionId query param is removed from the create endpoints (report, dashboard, collection)
- ATs are updated to create entities using the correct requests with definitions where possible, rather than the two stage empty create + update
- the API documentation is updated
This is the controller panel for Smart Panels app
- duplicates
-
OPT-2734 Remove collectionId query parameter from create endpoints
-
- Done
-