|
| Caption | | The Caption attribute identifies the text to be displayed.
For Image elements, Caption specifies the image filename. |
| Export | | UserDefined |
| PDF |
| Excel |
| CSV |
| Sets which exports are available on the report (comma-delimited list).
"Excel,PDF,CSV" |
| FrameID | | UserDefined |
| Top |
| Self |
| Parent |
| NewWindow |
| Sets the Frame for the target page. Leave blank for the current browser window, or enter NewWindow to open a new browser window. You can also specify an existing FrameID to re-use the same window for each request. |
| GroupFilterID | | Set GroupFilterID to the ID of a GroupFilter element under the DataLayer. |
| ID | | (Required) The ID attribute is a pervasive attribute that uniquely identifies an element within a definition file. The ID needs to be a unique value within the definition. |
| Image | | An image filename. The name can come from the images in the support files, or a relative URL within the same web application, or, for IndicatorState elements, a complete file system path. |
| SecurityRightID | | When entered, access to this element can be controlled with Logi security. Supply the ID of a right defined in the applications settings’ Security element. Only users that have a right in the SecurityRightID will be able to see the element.
Note that when rights come from RightFromRole elements under Security/UserRights, and this element's SecurityRightID does NOT match any of the Right IDs defined in the Settings definition, then the user DOES have access. But when Right IDs are instead derived from RightsFromDataLayer or RightsFromRoles elements, and the user DOES NOT have a matching Right, then the user DOES NOT have access.
You can enter multiple right IDs, separated by commas. In this case, the user sees the element if he has any one of the Rights.
|
| ShowModes | | ShowModes makes it possible to hide elements for some reports. Leave ShowModes blank for the element to always appear. Set it to None and it will be hidden. (You can make it appear later with an Action.ShowElement.) Set it to your own string value to have it appear only when the report's ShowModes includes that value. ShowModes can contain multiple, comma-delimited values.
Built-in ShowModes can be set on individual elements, without having to set a corresponding value in the report-level "Default ShowModes" list.To use built in ShowModes, set it to one of the pre defined values like
"rdBrowser","rdExport","rdExportPdf" etc from the dropdown list.
eg - Set ShowModes = "rdBrowser" for elements that should only appear in the browser and should be excluded from exports.Set ShowModes = "rdExport" for elements that should be exported but not shown in the browser.
|
| TemplateModifierFile | | Some elements employ a definition file as a template. The definition contains language and culture specific Caption attributes that you may want to change. Or you may simply want to change the captions to better suit your application.
The TemplateModifierFile is an XML file with elements pointing to other elements in the template to be changed. All other attributes get applied in the template.
For example, the Dashboard2 element has a template file (rdTemplate\rdDashboard\rdDashboard2Template.lgx) several Label elements. One has an ID="lblAddPanelsTitle". The Caption can be changed with the following XML in the TemplateModifierFile:
You can set attributes for any number of elements. Examine the template file to learn the ID and Caption attributes you may want to modify.
The above example shows how to identify template elements with an ID attribute. Alternatively, you can also identify elements with an XPath expression. In this example, we change an attribute of the InteractivePaging element:
For a more detailed list of modifier actions see the following DevNet article.
TemplateModifierFiles can be in any folder accessable to the web application. When a directory location is not specified, the default location is the _SupportFiles folder.
|