URL Properties
A URL can be configured as a property at many places throughout the system. These URL properties mostly have the same considerations:
An absolute URL begins with a protocol, usually http e.g. http://www.ebasetech.com. Note that the protocol is required for an absolute URL; if the protocol is missing, the URL will be treated as a relative URL.
A relative URL does not begin with a protocol and is resolved as being relative to the web application root. In the supplied Tomcat system, this is ../UfsServer/tomcat/webapps/ufs. E.g. a relative URL of images/helpimage1.gif will be resolved as ../UfsServer/tomcat/webapps/ufs/images/helpimage1.gif.
URL’s can contain field name and other variables as part or all of their content. These variables are then dynamically evaluated at runtime and substituted into the URL. Field variables and environment variables can be specified.
Substitution examples:
· &&VAR1
· images/&&{IMAGES_DIR}/&&{IMAGE_NAME}.gif
· &&{$ENV_IMAGES_ROOT}/help1.gif