You are viewing limited content. For full access, please sign in.

Question

Question

Weblink URL pass login and search

asked on July 1, 2016

I am new to this and I am trying to figure out how to create a weblink url that will:

1: pass a person's login credentials

2: search for a particular document in a certain repository by field

I have tried many variations but none work.

For example:

http://servername/weblink/search.aspx?searchcommand-({LF:Basic-=%ef%bf%bd1600034570%ef%bf%bd%7d)

I never get past the login screen - once I login I always get no results.

If I manually login to weblink and type this for an advanced search : {[]:[incident number]="16000345*"}  it works........................

So how do I get it all to happen in one URL??!! Thanks!

0 0

Replies

replied on July 1, 2016

Your search URL has a couple issues. You have a - instead of a = before the search syntax, a stray - before your = inside the syntax, and incorrect/incomplete encoding.

Try the following:

http://servername/weblink/search.aspx?searchcommand=%7B%5B%5D%3A%5Bincident%20number%5D%3D%2216000345*%22%7D

(field search on incident number)

or 

http://servername/weblink/search.aspx?searchcommand=%7BLF%3ABasic%3D%2216000345*%22%7D

(LF:Basic search)

 

I use an encoding/decoding tool (such as this one) on the entire search syntax (but only the search syntax, not the URL before that).

0 0
replied on July 1, 2016

Great - that worked - thanks!! 

Last question (for today!!). 

Is there a way to do this without encoding it? What I am trying to do is have another program just call the url (it would have to update the search each time in order to locate the correct document). 

So they could simply type something like (and they could programatically change the number inside the ""): 

http://servername/weblink/search.aspx?searchcommand={[]:[incident number]="16000345*"}

 

Thanks!!!

0 0
replied on July 1, 2016

Actually that does work!! So now I just need to know if they can programatically change the number inside the ""! 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.