Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/api_guide/chap-red_hat_satellite-api_guide-using_the_red_hat_satellite_api#sect-API_Guide-Using_Extended_Searches

Section Number and Name:
5.5. Using Extended Searches

Describe the issue:
After a change in behaviour when moving from sat 6.8 to 6.9, customer has found that some search terms need to be urlencoded when previously they we not.

Suggestions for improvement:
Document what parameters need to be url encoded and expand more on coverting search terms from UI to API use.

Additional information:
Documentation looks similar across sat 6.9, 6.10 and 6.11 so probably valid for all

In this specific case a datestring was being used for a comparision and ">" not needs to be urlencoded i.e. "search=%3e1970-01-01"