You can use @OP tags as part of an URL to be altered at playback, and these are substituted just as they are for @OP tags in other situations, for example as part of SQL query strings. Common situations where the use of @OP tags might be required are when you need to parameterize parts of the URL path component – the section of the URL after the scheme/host/port, and before any query parameters. For example:
http://machine.sybase.com:4040/@OP[“path”=“whatever”]/index.html
It might also be necessary to use @OP tags to parameterize part of a query parameter. UA makes query parameters available for parameterization, but this only allows users to enter all the parameter values. If however, it is necessary to only replace a portion of a query parameter, then you need to use @OP tags. For example, assume you have a URL like:
http://machine.sybase.com:4040/path/index.html?complicatedparam=param1% 3Dvalue1%26param2%3Dvalue2
In this case, you want to make the individual components of complicatedparam individually
parameterizable. So you might change this to:
http://machine.sybase.com:4040/path/index.html?complicatedparam=param1%3D@OP [“param1”=”value1”]%26param2%3D@OP[“param2”=“value2”]
Then the user is presented with two parameters—param1 and param2— which
are substituted in the URL. Relying on “whole” parameter
substitution would mean that the user would have had to enter the
combined parameter.
The @OP tag must contain a suitable default
value, as this is used to determine the initial navigation point.
