Using established conventions, such as those used for conditions syntax, you can create variables in a property definition URL. For more information, see Condition syntax.
-
Edge definitions are not supported since only a single relationship definition hop is supported from any URL property.
-
Multiple variables can be included in the URL if each traverses a single relationship definition hop. These can be in conjunction with one or more local properties and environment variables, provided each variable meets syntax rules.
-
Multiple values can be found if an object (such as a tag) belongs to many documents. For example, a URL property definition using a document relationship definition to point to the tag to pick up the Name property. In this example, a comma-separated set of values is added to the URL in place of the variable.
Variable examples
Variables are constructed differently for the Desktop Client and for the Web Client. For the Desktop Client, variables must be wrapped with ampersands (&). For the Web Client, variables must be wrapped with tildes (~).
Starting object properties
When you want a variable to display the value of a property definition from the starting object (native object), it should be constructed as follows:
-
&Obj.<Property Definition>& for the Desktop Client.
-
~Obj.<Property Definition>~ for the Web Client.
For example:
-
&Obj.Name& for the Desktop Client.
-
~Obj.Name~ for the Web Client.
Properties from related objects
When you want a variable to display the value of a related object, it should be constructed as follows:
-
&Obj-><Relationship Definition>_<Direction>.<Property Definition>& for the Desktop Client.
-
~Obj-><Relationship Definition>_<Direction>.<Property Definition>~ for the Web Client.
For example:
-
&Obj->DEVDocumentTag_21.Name& for the Desktop Client.
-
~Obj->DEVDocumentTag_21.Name~ for the Web Client.
Environment variables
When you want a variable to display a supported environment variable, it should be constructed as follows:
-
&ENV.<Variable>& for the Desktop Client.
-
~ENV.<Variable>~ for the Web Client.
For example:
-
&ENV.HOSTNAME& for the Desktop Client.
-
~ENV.HOSTNAME~ for the Web Client.
List view
When the URL is displayed in a list view, it is shown as a navigable link. When the link is clicked, the variables are resolved and the URL navigates to the value. The URL is shown as plain text to help performance. For example:
-
http://www.livelink.com/intergraph/&Obj.Name& for the Desktop Client.
-
http://www.livelink.com/intergraph/~Obj.Name~ for the Web Client.
The URL does not show the full name of a document, such as http://www.livelink.com/intergraph/C056-AA-ELE-05836-A.
Properties grid
When the URL property is displayed in the properties grid, it will be translated to include the derived values in place of the variables. You can review the URL before it is executed to resolve any limitations with the properties grid when the related object is accessed during click events.
Forms
When the URL property is displayed in the Query, Update, Create and Copy forms, it is shown inside of a text box so that you can edit and enter any text.
The URL property in the Details form is shown as a navigable link with any variables un-translated. This ensures that the URL property's appearance is consistent across all form types.
No variables embedded in the URL will be translated for these forms.
Business Intelligence
When a URL property is displayed in a list view in Business Intelligence, it is shown as a navigable link with any variables in their raw, un-translated state.