RELATED IDEAS
ConnectorStates paging / maximum
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Customers using connectorstates |
What impact would it make? |
Memory usage / performance |
How should it work? |
Extra parameter(s) |
Why is it needed? |
There is only one option to retrieve connectorstates, and that is ALL connectorstates. When there are a 'lot' of connectorstates, you need to retrieve all, and it can be a large response. |
Additional feedback, background or context:
We are currently in implementation of an enterprise solution and the integration architecture at the customer does not allow push integrations between cloud services and their own cloud network. The suggestion from Inriver was as well to push entity listener events to a connector state and have a scheduled job pick the events up.
During periods of migration and bulk updates, we can easily accumulate hundreds of thousands of connector states which cannot be retrieved swiftly enough according to the integration architecture requirements.
We need pagination for this recommended integration to actually be a viable solution.