|
Condition | | (Required) An expression that evaluates to a value of True or False. Expressions should be in JavaScript (recommended) or VBScript syntax.
For .NET versions, the scripting language can be set in the _settings.lgx General element. For Java versions, the scripting language is always JavaScript.
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. |
ID | | 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. |
IncludeCondition | | An expression that evaluates to a value of True or False. If the expression is blank, or evaluates to true the element is processed. If the expression evaluates to false, the element is skipped.
Expressions should be in VBScript or JavaScript syntax. For .NET versions, the scripting language can be set in the _settings.lgx General element. For Java versions, the scripting language is always JavaScript.
Typically, you would compare values using an operator, such as "@Session.value~ < 0".
Use quotes when working with strings:
"@Session.myValue~" == "SomeValue"
|
SecurityFilterRightID | | (Required) Set the SecurityFilterRightID to point to a Right in Settings. Users that have that right will be able to see all records that match the Condition. A Condition is a VBScript or JavaScript expression, and usually contains tokens such as @Data that compare each data record with a value.
Note that when rights come from RightFromRole elements under Security/UserRights, and this element's SecurityFilterRightID 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.
|