GetRequestInfo Browser differences
I Try to feed a workflow variable by using a url parametre. I therefor used this method to achieve my goal.
<-"You can use the following technique to access URL parameters from any workflow, no matter how it is launched.
1. First, use a 'GetRequestInfo' activity at the top of the workflow to populate a RequestInfo variable.
2. Then, create a new Uri object from the referrer:
referrer = new Uri(requestInfo.referrer)
3. Then the static method of HttpUtility 'ParseQueryString' may be used to get the individual parameter values, ie:
parcelID = System.Web.HttpUtility.ParseQueryString(referrer).Get("parcelID")
->
I use the silverlight application
But it only works in Google Chrome.
Chrome returns : "http://gis-vk/WebGIS/?parcelID=GIS-2012-00001"
If I try in Safari the refferer object is emty.
Safari returns : ""
If i try IE8 it returns the link the Silverlightviewer xap file
IE8 returns : "http://gis-vk/WebGIS/ClientBin/Geocortex.EssentialsSilverlightViewer.Viewer.xap
Can anybody pleace help me to solve this problem?
-
It is only when using Chrome the workflow return the ParselID.
I have tired debug what the RequestInfo.Referrer returned and it returned different for different browsers.
That i what i tried to explain in the question above.
0 -
Hello Sebastian,
Have you found a way to get the url parameter in IE8 and firefox? I run into the same problem with IE 8 and firefox while trying to get the url parameter in my workflow. Chrome works fine but firefox would throw "object reference not set to an instance of an object" error as the requestInfo object is not set,same with IE8.
Has anyone figured out an alternative way to get the url parameter in IE8 and firefox?
Thank you and regards,
Jin
0 -
You can use the "Get Browser Url" activity. This is a client activity that goes to the browser and gets the current URL. This should avoid any browser difference you are seeing with the referrer and Get Request Info.
--Ryan
0 -
Ryan,
Thanks for your response, appreciated!
Regards,
Jin
0
Please sign in to leave a comment.
Comments
4 comments