WCI Data Tags


This library provides data tags that retrieve WebCenter Interation (WCI) related data for use in creating links or finding out information about the current WCI page.

Data tags provide content for display tags, which format and display the content. The purpose of data tags is to retrieve various WCI data and set it in tag variables where the data is accessible for display tags. Display tags, such as the value tag in logic library or any of the tags in plugnav tag library, formats the data and generate HTML or javascript from it. For example, the plugnav:ptddmenutab tag generates HTML for a DHTML dropdown menu. It needs data from a data tag to populate the menu. Data tags are defined with a tag variable id. This id is passed to the plugnav:ptddmenutab through an attribute to tell the display tag where to find the data.

Data in tag variables is accessible from tag XML in portlets and layouts. The value of this is used to pass in Tag variable references as Tag attribute values, which allow portlet and layout developers to create portlets and layouts with dynamic data with XHTML in HTML files. It is no longer necessary to use IDK to retrieve WCI data.

Example:
<pt:ptdata.mandatorylinknamedata pt:key="title" />
<pt:logic.value pt:value="$title"/> // Outputs name of the current Page

The syntax for tag variable reference is the '$' character followed by the Tag variable name.

The mandatorylinknamedata tag sets a String value in the Tag variable. Most data tags set a data collections, bags of properties where each property is name/value pair. Properties in data collections are referenced in Tag attributes by appending '.' and the property name after the Tag variable name. The available properties on each data collection is described in the TagDocs for each data tag. The example below shows how to access the pageid property of the data collection that ptdata.currpagedata tag sets in the 'currpage' Tag variable.

Example:
<pt:ptdata.currpagedata pt:id="currpage" pt:noarray="true" />
<pt:logic.value pt:value="$currpage.pageid"/> // Outputs the value of the pageid property in data collection in 'currpage' Tag variable

Note that referencing Tag variables with the '$' notation only works inside Adaptive Tag attributes. Using a Tag variable reference within an HTML elements willnot work. Use the core.html tag to insert values in Tag variables to HTML elements.

Example:
<pt:ptdata.currpagedata pt:id="currpage" pt:noarray="true" />
<a href="$currpage.url">$currpage.title</a> // this does not work
<pt:core.html pt:tag="a" url="$currpage.url" /><pt:logic.value pt:value="#currpage.title"/></pt:core.html> // correct way

It is possible to aggregate data collections from multiple data tags into a single Tag variable. This is useful for creating a list of entries to use in for example a menu. By default, if a Tag variable contains one or more data collections (a list of collections), adding additional data collections to the Tag variable appends it to the existing collection list. The example below shows how data collections from three data tags are added to a single Tag variable. The result is one list of data collections containint data collections from all three data tags.

Example:
<pt:ptdata.currcommunitypagesdata pt:id="menu1" />
<pt:ptdata.communityactionsdata pt:id="menu1" />
<pt:ptdata.administrationdata pt:id="menu1" />

Data collections in lists are accessed from Tag expression language by iterating over the list using the logic.foreach tag. Tags in the plugnav tag library also expect Tag variables with list of data collections.

Example:
<pt:logic.foreach pt:data="menu1" pt:var="curr" />
 <pt:logic.value pt:value="" />
</pt:logic.foreach>

Note that by default data tags will create a list in a Tag variable even if the data tag only returns a single data collection. To avoid having to use a logic.foreach tag to iterate over a single data collection, use the 'noarray' attribute. Passing 'true' as value will tell the data tag to set the data collection directly in the Tag attribute without the list. This only works for data tags that always sets a single data collection. This attribute does not do anything for data tags returning multiple data collections. See TagDocs for each tag to find out whether a tag returns a single or multiple data collections.

Tag Library Information
Nameptdata
Version1.1
 

Tag Summary
addcommunityportletsdataCreates a single data collection with the link information for the Add Portlets on Communities editor (Editor to add and remove portlets in a Community).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

The data collection is only set on the Tag variable if the user has access to edit the current Community.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

addmypageportletsdataCreates a single data collection with the link information for the MyPages Add Portlets editor (Editor to add and remove portlets from a user's MyPage).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

administrationdataCreates a single data collection the link information for the Administrative Portal.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the user does not have access to the Administrative Portal.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

advancedsearchdataCreates a single data collection with the link information for the Advanced Search Page.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

directorybrowsedataCreates a single data collection with the link information for the specified Knowledge Directory folder in browse mode.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

communityactionsdataCreates a list of data collections containing the link information for Community actions, such as 'Join Communities Editor' and 'Edit this Community' actions.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

communityhierdataThis tag takes one or more community ids and creates a hierarchical data collection of Subcommunities and Community pages for the specified communities. Hierarchical data tags are used with display tags with nested data such as a tree or multi-level dropdown menus.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

communitykddataCreates a single data collection with the link information for Community Knowledge Directory of the current Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

This data tag only creates this data collection when in a Community with Community Knowledge Directory enabled. Nothing is set in the Tag variable otherwise.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

mycommunitiesdataCreates a list of data collections with the link information for a user's My Communities (Communities a user has joined or is a mandatory member of).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

communitypagesdataCreates a list of data collections containing the link information for Community Pages in the specified Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Only the Pages the user has access to are included.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

pageid: Page Id
pagename: Page name
commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

createnewcommpagedataCreates a single data collection with the link information for the Create New Community Page editor (Page in the Community Editor to create new Community Pages).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if a user does not have access to create new Community pages.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

createcommpageoneclickdataCreates a single data collection with the link information for the One-click Create New Community Page (Link that creates a new Community without an editor).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Template and page inheritance rule can be overriden with the optional pagetemplate and inherittemplate attributes. The URL is only returned for users who has access to create new Community pages.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

createnewmypagedataCreates a single data collection with the link information for the Create New MyPage editor.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the user has created the maximum number of MyPages

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

createnewmypageoneclickdataCreates a single data collection with the link information for One-Click Create New MyPage (Link to create a New Page without an editor).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the user has already created the maximum number of MyPages.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

currcommunitydataCreates a single data collection containing the link information about the current Community, including the name, object id and URL to the Community home page.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the current page is not a Community page or if the current user does not have sufficient access to the current Community.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL


If used on a User Profile Page:
classid: Contains the value "1"
commid: User id of the displayed User Profile
commname: Name of the user
pageid: User Profile Page Id
pagename: Name of the User Profile Page

currcommunitypagesdataCreates a list of data collections with the link information for Community pages in the current Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the current user is not in a Community or does not have sufficient access to the current Community.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

pageid: Community Page Id
pagename: Community Page name
commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.


If used on a User Profile Page:
classid: Contains the value "1"
commid: User id of the displayed User Profile
commname: Name of the user
pageid: User Profile Page Id
pagename: Name of the User Profile Page

currpagedataCreates a list of data collections with the link information for the current page (Name, page id, url and more for MyPage or Community pages).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the current page is not a MyPage or Community page.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

pageid: Community Page Id
pagename: Community Page name
commid Community id
commname Community name
classid Set to '518' when on MyPages and '514' when on Community Pages
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

currparentcommunitydataCreates a single data collection with the link information for the Parent Community (The Community above the current Community in the administrative hierarchy) of the current Community .

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

currprofiledataCreates a single data collection with information about the current User Profile.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if this tag is not used on a User Profile page.
Note, this tag displays information about the user who's profile is being viewed; not the logged-in user.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

fullname, email, imuser, phone, employeeid, department, title, zipcode, manager, _profileuserid, _profileusername, _profiledescription, _profileloginname, _profileuniquename, _profileauthname, accessingfromintranet, hostpagequerystring
Note that not all UserInfo properties are set for every user.

currrelatedcommunitiesdataCreates a list of data collections with the link information for the Related Communities (other Communities in same level on the Admin Hierarchy) of the current Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

currsubcommunitiesdataCreates a list of data collections with the link information for the Subcommunity (Communities inside another Community in the Admin hierarchy) of the current Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if this tag is not used in a Community.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

deletemypagedataCreates a single data collection with the link information for the Delete My Page action (Deletes the current My Page a user is on).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if this tag is used on a user's Home Page, which is cannot be deleted.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

editcommunitydataCreates a single data collection with the link information for the Edit Community editor (Editor to edit different aspects of the current Community).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if the user does not have access to edit the current Community or when this tag is not executed in a Community.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

directoryeditdataCreates a single data collection with the link information for the specified Knowledge Directory Folder in edit mode. The link goes to the root folder if no folder ID is specified.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the Tag variable if a user does not have access to edit the Knowledge Directory.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

editmypageactionsdataCreates a single data collection with the link information for the Edit My Page editor (Editor to edit My Page name and layout).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

editmypageportletprefsdataCreates a single data collection with the link information for the Edit Portlet Preferences for MyPage editor (Editor to edit all portlet preferences on the current page).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

federatedsearchdataCreates a single data collection with the link information for the Federated Search Page.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

genericurlCreates a single data collection with configurable link information. Specify link data through the attributes.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

The imgproperty is only set if an image is specified.

helppagedataCreates a single data collection with the link information for the Online Help Page (Opens the online help for the current page).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
url: Returns # in standard display mode,since help is opened in a popup window. Use the jsaction propertyto get the javascript that opens the help popup. In Accessibility and low-bandwidth mode this property contains a URL to the help page.

jsarraydataformatThis tag is different from other data tag in that it does not set data in a Tag variable. Instead it is used to generate and output a JSON (Javascript object notation) representation of a single- or list of data collections. Data collection properties are represented as javascript object properties, data collection as javascript objects and lists as javascript arrays. Nested lists and collections are supported for use with hierarchical data tags. Used for:1. With menu and tree tag definitions2. Debugging property values in a data collection. Put this tag in an HTML comment or javascript block and pass in the data collection with the properties to inspect. View the values by looking at the HTML source for the page.
joincommunitiesdataCreates a single data collection with the link information for the Join Communities editor (Editor to select what Communities to display on users's My Community list).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

joincurrcommunitydataCreates a single data collection with the link information for the Join Current Community action (URL subscribes a user to the current Community).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

loginlogoffdataCreates a single data collection with the link information for Login/Logoff Action (Login link if the current user is not logged in or Logoff link if the current user is already signed in).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

mandtabcommsdataCreates a list of data collections containing users's Mandatory Communities (List of Communities a user cannot unsubscribe from) link information.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

mandatorylinksdataCreates a list of data collections with the link information for the current user's Experience Definition Mandatory Links

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Only URLs to objects a user has access are included.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

mandatorylinknamedataSets Subportal Mandatory Links Folder Name (Mandatory links are configured in Experience Definitions. The folder name is the string that is displayed as the header for these links. For example as the title of a tabthat opens mandatory links in a dropdown menu) in specified Tag variable.
myaccountdataCreates a single data collection with the link information for the user's My Account Page (Goes to the My Account page where users can change various portal settings such as locale and display options) link information.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

myhomedataCreates a single data collection with the link information to the user's Experience Definition Home Page.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

mypageactionsdataCreates a list of data collections with the link information for a users's My Page actions (My Page actions such as 'Create New MyPage' or 'Edit Page'. Some actions are only included when currently on a MyPage).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

mypagesdataCreates a list of data collections with the link information for the current users's My Pages.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

pageid: Page Id
pagename: Page name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

myprofiledataCreates a single data collection with the link information for the user's Profile Page (Goes to the User Profile page where users can view personal profile information).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

pagelinkThis tag will display a link back to the current page or to the base URL of the current page (without the ?). The HTTP entry point portion of the link can be modified.

This tag does not display the contents of the tag and should only be used as a singleton tag (i.e. <pt:ptdata.pagelink/>), rather than as a tag with both an open and close tag.

parentcommunitydataCreates a single data collection with the link information for the Parent Community of a specified Community (The Community above the specified Community in the Admin hierarchy).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the tag variable if the specified Community does not have a parent Community or if the specified Community cannot be found.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

relatedcommunitiesdataCreates a list of data collections with the link information for Related Communities (Communities in the same level of the Admin hierarchy) of the specified Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the tag variable if the specified Community does not have related Communities or if the specified Community cannot be found.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

rulesdebugdataCreates a single data collection with the link information for the Rules Debug Popup Page (Where users can view debug messages sent by the experience definition rules engine).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

subcommunitiesdataCreates a list of data collections with the link information for Subcommunities (Communities located below a Community in the Admin hierarchy) of the specified Community.

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

Nothing is set in the tag variable if the specified Community does not have Subcommunities or if the specified Community cannot be found.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

commid: Community id
commname: Community name
title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL
currpage: This property is only set on the data collection item containing information about the current page or community. Check for this property to locale the currently active Page or Community in a list of Pages or Communities. This allowsyou to for example bold the name of the currently active Page or Community.

unsubscribecommunitiesdataCreates a single data collection with the link information for the Unsubscribe from Communities editor (Editor where a user can remove Communities from their My Community list).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

unsubscribecurrcommunitydataCreates a single data collection with the link information for the Unsubscribe from current Community action (Clicking on the URL unsubscribes the user from the current Community and brings the user back to their Home Page).

The data collection is set in the specified Tag variable. By default, data tags store data collections in a list, even for a single collection. Data tags do not replace data in a Tag variable if something is stored there already but they append their new data to the existing data instead. Assembling a list of data from multiple data tags is done by specifying the data tags to use the same Tag variable. The downside with data collections stored in lists is that a single data collection is not directly referenceable using the '$' syntax. Instead of using a foreach tag to iterate over the list for a single data collection, use the 'noarray' attribute. See description for this Tag library for example.

A data collection is a bag of "properties": name/value pairs where values are typically Strings. When assigned in tag variables, data collections and their properties are accessible in tag attributes through a special syntax: ${tag variable name}.{property name}

Example:   <pt:logic.value pt:value="$mytag.nameproperty" />

When the tag framework executes the tags, the expression is replaced with the property value in the data collection. See description of ptdata tag library for more information and examples of tag collections.

Data properties
This data collection contains the following data properties:

title: URL display string, usually the name of target the Page or Community
url: Full URL to the target page
uri: URI (part of URL after the server name) to the target page
img: URL to the Icon associated with the target page
imgheight: Height of the icon in pixels
imgwidth: Width of the icon in pixels
params: Query string of the target URL

 


Java, JSP, and JavaServer Pages are trademarks or registered trademarks of Sun Microsystems, Inc. in the US and other countries. Copyright 2002-3 Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054, U.S.A. All Rights Reserved.