|
| 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. |
| MetadataDescription | | The MetadataDescription can provide more detailed information related to a data source.
The text appears in the ActiveQueryBuilder as a tooltip. |
| MetadataName | | (Required) The MetadataName is shown to end-users when they are prompted to select a data source. |
| MetadataUrl | | Metadata definition files are stored in the application's _Metadata folder. Typically, the Studio Metadata Wizard is used to create and update the metadata file, and the Info Server reads the file from that location.
MetadataUrl allows metadata definition files to be read from alternative locations.
It is possible to build a custom solution which generates live metadata definitions during Info server requests. The solution would use a custom REST-style Web service, with the service's URL specified in this MetadataUrl attribute. For example:
http://myserver/mymetadataservice
The URL may also be a file URL, for example:
file:c:/myfolder/mymetadata.lgx |
| 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.
|