At the moment DataPage uses modelled filter set and sort set to deliver the data set. If there is need for use a slightly different filter set, we need to model a new endpoint.
We would like to be able to define a single endpoint maybe with some default filter set and sort set, but to enable clients to send requests to resort delivered data or filter them more. It should work the same way is Origam internal API works.
The filter/sort requests could be added as parameters after the endpoint and the server should be able to handle them.
I think it should be possible to explicitly enable this in the endpoint so it is
Safe (someone cannot misuse the API by entering malicious filters that e.g. are not indexed)
Backwards compatible (the developer will consciously choose to enable the filter and sort parameters, which could otherwise be already used in parameter mappings.
If enabled, we could also add a model integrity check on the parameter mappings to disallow filter and sort parameter mappings. Unless we want to interpret them (e.g. on Workflow Methods?). The same could apply to the pagination parameters.