Parameters (e.g. customer ID from a call) passed to a webpage in a Quick Launch are enclosed in double-quotes.

These double-coutes (") makes it impossible to pass valid parameters to certain web applications expecting just the value of the parameter, not the parameter string in quotes.

Example of problem

Suppose that I want to pass the customer's user id (e.g. ABC123) from a call in service manager to the parameter UserID in the following URL:
http://somewebapplication/profile?UserID=[$Lookup USER_ID|LOOKUP_CUSTOMER|USER_REF]

The problem is that the URL called is not http://somewebapplication/profile?UserID=ABC123 but http://somewebapplication/profile?UserID="ABC123" meaning that the web application will fail to show the resource needed since "ABC123" is not a valid parameter value when ABC123 would be.

The current functionality is not flexible and assumes that all applications called from Quick Launch accept parameters in the same way, with quotes, without encoding etc. and that's severely limiting the usage potential of Quick Launch actions!

Suggestions

To make the Quick Launch function useful we need the ability to control if and which way the parameter values passed are enclosed (quoted or not) and also to control which encoding to apply to the value.

URL-encoding would be a great option to have or other form of escaping relevant for different target environments, command prompts, powershell etc.

Being able to pass whole objects (in JSON, XML or other serialization format) would be really convenient.

Instead of having to type in the parameter string (e.g. [$Lookup USER_ID|LOOKUP_CUSTOMER|USER_REF]) it would be better if one could just pick one/several/all from a list among those available.