[mapguide][MG224][New] Support additional expression functions for hyperlinks

Walt Welton-Lair walt.welton-lair at autodesk.com
Fri Apr 14 17:07:13 EDT 2006


You can view the artifact detail at the following URL:

    https://mapguide.osgeo.org/servlets/Scarab/id/MG224

Type
 Enhancement

Artifact ID
 MG224 (Support additional expression functions for hyperlinks)

Reported by
 Walt Welton-Lair
 waltweltonlair (walt.welton-lair at autodesk.com)

New artifact details:
---------------------------------------------------------

- Summary set to new value
  Support additional expression functions for hyperlinks
- Justification set to new value
  Allows hyperlinks to store feature identifying information.

- Description set to new value
  In order for hyperlinks to truly be useful, we need a way to tie the hyperlink to an actual feature.  That requires there be a way to include the feature ID, feature class, and layer ID with a feature's hyperlink.

A user could manually enter this information in the layer's tooltip string.  For example, if the name of the feature key property is KEY, the feature class name is "MyClass" and the layer name is "MyLayer", then they could enter a hyperlink expression like:

Concat(Concat('Hyperlink.php?FeatureID=', KEY), '&FeatureClass=MyClass&LayerID=MyLayer')

Every generated link will therefore have the required identifying information.  It's a bit tedious but it could work, unless you have multiple feature classes in the same layer, or you change the layer name.

An easier solution would be to define some additional functions:

MAPNAME
SESSION
LAYERID
FEATURECLASS
FEATUREID

that can be used in the hyperlink expression.

Now the hyperlink could be something like the following:

concat(concat(concat(concat(concat('Hyperlink.php?FeatureID=', FEATUREID()), '&FeatureClass='), FEATURECLASS()), 'LayerID='), LAYERID())

When generating the hyperlinks the server would automatically fill in the feature ID, feature class, and layer ID for each feature.  All-in-all this is much easier for the end-user.

No client-side code needs to be modified to support this.

- Artifact Status set to new value
  New
- Target milestone set to new value
  1.0
- Priority set to new value
  P2
- Artifact created

---------------------------------------------------------
This message was automatically generated by Project Tracker.








More information about the Mapguide_issues mailing list