| request |
read for query parameters to be used as search criteria; use any combination of fields from tables:
movement - use movement or no prefixstop - use origin or destination prefixes as appropriatedriver - use driver1 or driver2 prefixes as appropriatetractor - use tractor prefixtrailer - use trailer1, trailer2 or trailer3 prefixes as appropriate
For example, /movements/search?brokerage=Y&origin.location_id=WARE*&destination.state=AL
would find brokered movements originating from locations starting with 'WARE' and destined for Alabama.
Sorting: To sort the result set, you can provide the following reserved query parameter: orderBy If the orderBy parameter is not provided a default sort of movement.id+DESC will be applied.
For example, /movements/search?movement.status=P&orderBy=movement.id+DESC would return all in progress movement records sorted descending by movement.id. Multiple sort columns can be provided in a comma delimited format. orderBy=prefix.field+direction,prefix.field+direction
Pagination: To page the result set, you can provide the following reserved query parameters: recordLength and recordOffset
For example, /movements/search?movement.status=P&recordLength=100&recordOffset=50 would return 100 records starting at the 51st record in the return record set. If no recordLength parameter is provided the search result maximum value in the mobile service control file will be applied. |
context
|
|
HttpServletRequest
|