|Class||Sets the Cascading Style Sheet class used by the element. When set, this class will also be used by all child elements that don't have their own class. The class should be defined in the report's style sheet file. |
Typically, you would compare values using a token, such as "@Data.value~ < 0" or "@Session.ShowCol1~=='true'". Elements are removed when the Condition evaluates to False.
Use quotes when working with strings:
"@Data.myColumn~" == "SomeValue"
If your data token may have a double quote inside of it, you should use single quotes:
'@Data.myColumn~' == 'SomeValue'
String valued data tokens with single and double quotes inside are not supported by the condition attribute.|
|FrameBorder||Determines if a border is drawn around the frame. The default value is True.|
|Height||The height of the element.
For some elements, leave the height blank to automatically size the element to the height of the content.|
|HeightScale||The width scale of the element. Value can be "px" for pixels, or "%" for percentage of the available height. Leave this value blank to have the frame automatically adjust to the size of its contents.|
|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.|
|Scrolling||Enables or disables scrolling within the frame. The default value is Auto.|
|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.
|Embedded||SubReports insert the contents of another report into the current report. They have modes - IncludeFrame and Embedded.
"IncludeFrame" causes the SubReport to be loaded by the browser into its own window within the current report. This is especially useful when the SubReport is initially invisible with ShowModes, and you only want to load the SubReport when it is made visible. You may set the Width and Height attributes to specific values to set the size of the window. Or the window will be automatically sized according to the size of its contents set by not entering Width and Height.
"IncludeFrameAsync" is similar to "IncludeFrame" except the server will process multiple SubReports simultaneously in multiple threads. This can provide improved performance, although note that session variables cannot be saved for SubReports run in async mode.
"Embedded" SubReports are run and directly inserted into the current report. The entire report is returned as a single page. This is best when SubReports are initially visible.
"Embedded" is the default value when the report format is "Printable" or exporting to Word and Excel. Otherwise, "IncludeFrame" is the default. When a SubReport is embedded, all of its nested SubReports, if any, must also be embedded.|
|Width||The width of the element.|
|WidthScale||The width scale of the element. Value can be "px" for pixels, or "%" for percentage of the available width.|