Displays multiple menu items as a single page.
Each displayed menu item, a.k.a. part is defined by a link of type 'Multipart'. The same link may be used multiple times and may utlilize data supplied from the sql as passing fields.
Parts are layouted in a table like manner. Each part occupies a number of cells in the layout table. The height of rows and widths of columns in the table can be specified or computed automatically.
Retrieves a list of parts to display along with meta data describing column and row dimensions.
When rows or column dimensions are not fully specified the component will try to utilize the entire browser window to display the parts. If this is not possible due to the minimum dimensions specified occupy more space than available scrollbars will appear in the browser window.
If the contents of a part occupy more space than specified scrollbars will appear around the contents of the part. No scrollbars will appear around the header of a part, so make sure the minimum width specified is enough to display the entire header for a part.
|<min>-||The column will receive a final width no less than <min>.|
|<min>-<max>||The column is guaranteed to receive a final width somewhere between the <min> and <max> specification.|
|<width>||The width in pixels|
|null or empty||The width of the column will be the minimum required to display the contents of all parts occupying the column without scrollbars.|
|<height>||The height in pixels|
|<min>-||The row will receive a final height no less than <min>.|
|<min>-<max>||The row is guaranteed to receive a final height somewhere between the <min> and <max> specification.|
|null or empty||The height of the row will be the minimum required to display the contents of all parts occupying the row without scrollbars.|
Allows you to validate the parameters supplied by the user before any other SQL is run in the component. This call is only made if the component has visible parameters, the SQL is a stored procedure, and 'Validate parameters' is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.