|DisableGalleryUpdates||Set to True to prohibit deletion of panels from this Gallery file.|
|GalleryCaption||When there are multiple galleries defined with ExtraGalleryFile elements, there may be a caption set for each. When the galleries are displayed, the user may select one from a drop-down list. Making a selection shows only visualizations from that gallery.|
|GalleryFile||(Required) With the AnalysisGrid's CustomDashboardPanels element, charts and tables may be copied to a SaveFile to be added by the user later to a Dashboard or ReportAuthor report.
The GalleryFile allows the visualizations to be stored outside of a specific dashboard file, so that they may be copied into multiple dashboards.
There are two methods for creating gallery files.
This first method uses a dashboard save file as a gallery file, so the gallery has panels that have been added to a dashboard. This method makes it easier to add and remove gallery items by working directly with a dashboard. Set the CustomDashboardPanels' DashboardSaveFile to a gallery xml file. This file will be created and updated as the user adds visualizations. Then, in the Dashboard or ReportAuthor element, set the GalleryFile to this same file.
The second method gets gallery items from a report definition .lgx file which has its own Dashboard and Panel elements. The panels will make up the gallery items.
Specify the gallery file's full path and filename.
GalleryFile information may be stored in a relational database. See the Settings FileToDatabaseMapping element.|
|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.|
|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.