[rt-users] Assembling Search URLs (reformulated)

[Jan Algermissen]

Stefan Seiz wrote:

> Allright, getting closer. So your "other application", how does it log into
> rt? See your browser has an open session when doing the search - some
> session-information is stored in a cookie AFAIK, so maybe your other APP
> would have to deal with this too?

The assembled URLs will be used within a browser, so if the cookie is not
set, I expect the login page to be shown and after that be taken to the
appropriate page (with the original (non-modified) URLs this works.)


> And you say "I don't get correct results", could you elaborate on this?
> Showing us what "not correct" means could certainly help. Something like "I
> did this", "expected this" but "go that" (incl. copies of your built urls
> etc.) would be realy helpful. Everything else is just plain guesswork and
> mind-reading ;-)

Here is what I do:

1) NewSearch -> Search on Queue IS "Incidents"

   (now the custom field "Related_CI" shows up in the search screen since it
   is present on that Queue only).


2) Refine search by setting  Related_CI IS "cs1"

   (I get the expected result (2 tickets)) and this bookmark URL:

http://rt.nec.dkrz.de/Search/Listing.html?Bookmark=FrT%3B%402%7C%254%7C%242%7C10%242%7C11%258%7C%2411%7CDESCRIPTION%245%7CFIELD%248%7COPERATOR%245%7CVALUE%2417%7CQueue%20%3D%20Incidents%245%7CQueue%241%7C%3D%249%7CIncidents%2510%7C%2411%7CCUSTOMFIELD%2411%7CDESCRIPTION%245%7CFIELD%248%7COPERATOR%245%7CVALUE%241%7C1%2431%7CCF.Incidents.%7BRelated_CI%7D%20%3D%20cs1%2425%7CCF.Incidents.%7BRelated_CI%7D%241%7C%3D%243%7Ccs1%242%7C12&TicketsSortBy=id&TicketsSortOrder=ASC&RowsPerPage=50

Decoded with Perl URI::Escape

http://rt.nec.dkrz.de/Search/Listing.html?Bookmark=FrT;@2|%4|$2|10$2|11%8|$11|DESCRIPTION$5|FIELD$8|OPERATOR$5|VALUE$17|Queue =
Incidents$5|Queue$1|=$9|Incidents%10|$11|CUSTOMFIELD$11|DESCRIPTION$5|FIELD$8|OPERATOR$5|VALUE$1|1$31|CF.Incidents.{Related_CI} =
cs1$25|CF.Incidents.{Related_CI}$1|=$3|cs1$2|12&TicketsSortBy=id&TicketsSortOrder=ASC&RowsPerPage=50

3) I substitute the two occurrences of cs1 with another CI-identifier but get exactly the original
   result and even the same information in the 'bookmark menu' (where one can deselect single
   criteria).

I expected the search to be cached, but since I learned that there is no hidden magic, I have
no idea anymore, what I do wrong.

Hints?

Jan
-- 
Jan Algermissen                           http://www.topicmapping.com
Consultant & Programmer	                  http://www.gooseworks.org