Displays a detailed view of a database object, including tabbed miniviews consisting of linked menu items.
The InfoView mode is used when all you need to display is InfoSQL.
A Detailview can display any number of info boxes. Below the info boxes there can be zero or more tabs. A tab is an area with a Softadmin® component in it.
The tabs are situated below the info boxes. When the detail view is loaded, you can choose which tab is open initially. Please note that the tabs and the info boxes might compete for the vertical space if they both contain a lot of content.
If there is not enough space for a tab, you can collapse one or more info boxes (se above), or you can switch the tab to fullscreen mode.
You can display any number of info boxes. They are positioned right-to-left as far as the width of the browser window allows. The width of an info box can be set to span multiple normal info boxes. If so the widened info box will always be displayed on its own row. In the example below the first two boxes are set to span two and three columns respectively, followed by three boxes with normal width. Notice how the layout changes when the browser window is resized.
An info box can contain a list of field names and values. The "Car details" info box shown above has four field names: Model, Year model, Price (SEK) and Fuel.
An info box can also display free flowing text, as seen at the bottom of the "Car details" info box.
The appearance of the fields can be modified by setting their color and css-styles. You can also display an icon before the field text.
The up-arrow in an info box's header can be clicked, to collapse the box. It can be either collapsed or expanded by default.
An info box can be a pure text block. In this case html can be used.
The title of the info box as well as it's fields can be made into clickable links. The "E-mail" link in this case is a so called "content link", which opens the users preferred e-mail client instead of an internet browser.
You can convert a string of characters to a QR Code. The size of the QR code will vary depending on the length of the string. It can hold a maximum of 2 kB.
You can display a chart in an info box. See below for details. (For backwards compatibility, the now deprecated Chart component can also be used in an info box, but new applications should use the JSON-based Chart).
You can display one or more meters in an info box.
An info box can contain a frame with an external webpage. Make sure the webpage doesn't use cookies.
To grab the user's attention, you can display an error, warning, or an informational message as a special banner. In this example, one of each is shown, but you can display any number of error, warning, or info messages.
Charts are generated using JSON. Below you can see an example Chart with its corresponding JSON.
{
"Type": "Pie",
"ShowLegend": true,
"Heading": "Employees",
"Unit": "employees",
"LinkAlias": "ChartLink",
"PieValues": [
{
"Value": 25,
"Label": "HR",
"PassingFields": { "DepartmentId": 1 }
},
{
"Value": 18,
"Label": "Economy",
"PassingFields": { "DepartmentId": 2 }
},
{
"Value": 10,
"Label": "IT",
"PassingFields": { "DepartmentId": 3 }
}
]
}
Multiple charts can be shown side by side by putting them inside an array.
[{
// Chart properties
},
{
// Chart properties
}]
Type: The type of the chart, must be "Pie" for pie charts. (mandatory)
Heading: Heading displayed above the chart. (optional)
LinkAlias: Link to use for the pie slices. (optional)
ShowLegend: Whether or not to show the legend. Defaults to true. (optional)
LegendPosition: Where to show the legend. Defaults to "right". (optional)
Possible values | |
---|---|
Right | Legend is positioned to the right of the chart.. |
Bottom | Legend is positioned below the chart. |
NumberOfDecimals: The number of decimals shown for the value. Defaults to 0. (optional)
Unit: Unit to display after the value. (optional)
Prefix: Prefix to display before the value. (optional)
MaxWidth: The maximum width for the chart in pixels, use if the chart should be smaller than the infobox. Default fit to info box. (optional)
MaxHeight: The maximum height for the chart in pixels, use if the chart should be smaller than the info box. Default keep aspect ratio. (optional)
PieValues: Values to be shown in the chart. (mandatory)
GroupTinyValues: Small values that are grouped into a "Other slice". (optional)
Recommended to order by value for esthetic reasons unless there is a logical order.
Value: The decimal value. (mandatory)
Label: The label for the value. (mandatory)
Color: Color of the pie value, if not specified the default color scheme will be used (recommended). See Colors. (optional)
Tooltip: Custom tooltip to append to or override the default tooltip when the section is hovered. Shows the value and unit by default. (optional)
OverrideTooltip: Controls whether the custom tooltip overrides or is appended to the default tooltip. (optional)
PassingFields: Object containing the passing fields for the chart link as properties. (optional)
Label: Label of the group. (mandatory)
Threshold: All values smaller than this value are placed in the tiny value group. (optional)
ThresholdPercent: All values smaller than this percentage of the total are placed in the tiny value group. (optional)
The following query will produce the JSON used above.
SELECT
(
SELECT
'Pie' AS [Type],
1 AS ShowLegend,
'Employees' AS Heading,
'employees' AS Unit,
'ChartLink' AS LinkAlias,
(
SELECT * FROM (SELECT
10 AS Value,
'IT' AS Label,
3 AS DepartmentId
UNION ALL
SELECT
18,
'Economy',
2 AS DepartmentId
UNION ALL
SELECT
25,
'HR',
1 AS DepartmentId
) X(Value, Label, [PassingFields.DepartmentId])
ORDER BY
X.Value DESC
FOR JSON PATH
) AS PieValues
FOR JSON PATH
) AS Chart
Charts are generated using JSON. Below you can see an example combined bar and line chart with its corresponding JSON.
[
{
"Type": "xy",
"Heading": "Sales",
"XAxis": {
"Scale": "Ordinal",
"Values": [
{
"Value": "2019"
},
{
"Value": "2020"
},
{
"Value": "2021"
},
{
"Value": "2022"
},
{
"Value": "2023"
}
]
},
"YAxis": {
"Unit": "TSEK",
"Values": [
{
"Value": 0
},
{
"Value": 10000
},
{
"Value": 20000
}
]
},
"Lines": {
"Series": [
{
"Label": "Goal",
"LineShape": "smooth",
"Values": [
{
"xValue": "2019",
"yValue": 8001
},
{
"xValue": "2020",
"yValue": 8931
},
{
"xValue": "2021",
"yValue": 11203
},
{
"xValue": "2022",
"yValue": 10912
},
{
"xValue": "2023",
"yValue": 14412
}
]
}
]
},
"Bars": {
"Series": [
{
"Label": "Sales",
"LinkAlias": "ChartLink",
"PassingFields": { "SalesId": 1 },
"Values": [
{
"xValue": "2019",
"yValue": 9001
},
{
"xValue": "2020",
"yValue": 11931
},
{
"xValue": "2021",
"yValue": 13203
},
{
"xValue": "2022",
"yValue": 8912
},
{
"xValue": "2023",
"yValue": 15412
}
]
}
]
}
}
]
Multiple charts can be shown side by side by putting them inside an array.
[{
// Chart properties
},
{
// Chart properties
}]
Type: The value displayed. Must be a valid decimal type. (mandatory)
Heading: Heading displayed above the chart. (optional)
ShowLegend: Whether or not to show the legend. Defaults to true. (optional)
LegendPosition: Where to show the legend. Defaults to "bottom". (optional)
Possible values | |
---|---|
Right | Legend is positioned to the right of the chart.. |
Bottom | Legend is positioned below the chart. |
ShowValuesInLegendTooltip: Whether or not to show all the series values in the legend tooltip in addition to the label. Default only visible if there are 2 or fewer X-values for all series. (optional)
NumberOfDecimals: The number of decimals shown for the value. Defaults to 0. (optional)
ShowXGridLines: Whether or not to show X grid lines behind the chart. Defaults to false. (optional)
ShowYGridLines: Whether or not to show Y grid lines behind the chart. Defaults to true. (optional)
MaxWidth: The maximum width for the chart in pixels, use if the chart should be smaller than the infobox. Default fit to infobox. (optional)
MaxHeight: The maximum height for the chart in pixels, use if the chart should be smaller than the infobox. Default keep aspect ratio. (optional)
AspectRatio: The width to height aspect ratio specified as a decimal number. A value bigger than 1 indicates a chart wider than the height. (optional)
XAxis: Definition of a custom X-axis. See XAxis. (optional)
YAxis: Definition of a custom Y-axis. See YAxis. (optional)
Lines: Line chart lines. See Lines. (optional)
Bars: Bar chart bar. See Bars. (optional)
Scale: The scale to use. (mandatory)
Possible values | |
---|---|
Linear | A continuous linear number scale. |
Date | A continuous linear date scale. |
Ordinal | A scale with discrete values, for example names of categories. |
Log | A continuous logarithmic number scale. |
Label: The label on the whole X-axis. (optional)
Prefix: Prefix to display before label or value. (optional)
Unit: Unit to display after values. (optional)
LogBase: The base when using Scale="Log". (optional)
Values: An array of custom axis values. Default derive from data. See Values (Axis values). (optional)
Scale: The scale to use. Default "Linear". (optional)
Possible values | |
---|---|
Linear | A continuous linear number scale. |
Log | A continuous logarithmic number scale. |
Label: The label on the whole Y-axis. (optional)
Prefix: Prefix to display before label or value. (optional)
Unit: Unit to display after values. (optional)
LogBase: The base when using Scale="Log". (optional)
AdaptAxisToValues: Whether the Y-axis should adapts its Y-values if the values are out of range or if the value should go off the chart. Default false if values are explicitly set, true if there are no explicit values. (optional)
Values: An array of custom axis values. Default derive from data. See Values (Axis values). (optional)
Value: A custom axis value. (mandatory)
Label: Label to display instead of the value. (optional)
HideLabel: Hides the label on the axis, the label will still be displayed in the tooltip. (optional)
Series: An array of line series, each series will correspond to a line. See Series. (mandatory)
Series: An array of line series, each series will correspond to a set of bars of the same color, or for stacked bars a part in each stack. See Series. (mandatory)
Direction: The direction of the bars. Default "Vertical". (optional)
Possible values |
---|
Vertical |
Horizontal |
Stacked: Whether or not the bars are stacked. Default false. (optional)
ShowValuesAsLabel: Whether or not to show the values as labels in the chart rather than just with tooltip. Default false. (optional)
Label: The series label. (mandatory)
Tooltip: The series tooltip. (optional)
Values: An array of values. See Values (Series values). (optional)
Color: The series color. See Colors. (optional)
Type: The series line type. Only applicable to line series. Default "Line". (optional)
Possible values | |
---|---|
Line | A consistent line. |
Range | A range between two Y values. |
Point | Only the data points are plotted. |
LineShape: The line shape. Only applicable to line series. Default "Normal". (optional)
Possible values | |
---|---|
Normal | Straight lines between the data points |
Smooth | A smooth curve passing through all data points. |
Step | A line consisting of alternating horizontal and vertical lines. |
Markers: The line markers. Only applicable to line series. Default "None". (optional)
Possible values |
---|
None |
Round |
Label: The series label. (Mandatory)
LinkAlias: Alias of the link to use for the series. (optional)
PassingFields: Object containing the link's passing fields as properties. To use specific passing fields for each value, use the passing fields property on the values instead. (optional)
Tooltip: The series tooltip. (optional)
Values: An array of values. See Values (Series values). (optional)
Color: The series color. See Colors. (optional)
XValue: The X value. (mandatory)
YValue: The Y value, number. (mandatory)
Y2Value: The Y2 value, number. Used by line series type range. (optional)
Tooltip: A custom tooltip to append to or override the default. Default a tooltip indicating the X and Y value and the series. (optional)
OverrideTooltip: Controls whether the custom tooltip overrides or is appended to the default tooltip. (optional)
PassingFields: Object containing the link's passing fields as properties. (optional)
The following query will produce the JSON used above.
SELECT
(
SELECT
'xy' AS [Type],
'Sales' AS Heading,
'Ordinal' AS [XAxis.Scale],
(
SELECT
V.Year AS Value
FROM
(VALUES ('2019'), ('2020'), ('2021'), ('2022'), ('2023')) V(Year)
FOR JSON PATH
) AS [XAxis.Values],
'TSEK' AS [YAxis.Unit],
(
SELECT
V.Value AS Value
FROM
(VALUES (0), (10000), (20000)) V(Value)
FOR JSON PATH
) AS [YAxis.Values],
(
SELECT
V.SeriesName AS Label,
'smooth' AS LineShape,
(
SELECT
V.xValue,
V.yValue
FROM
(VALUES ('2019', 8001), ('2020', 8931), ('2021', 11203), ('2022', 10912), ('2023', 14412)) V(xValue, yValue)
FOR JSON PATH
) AS [Values]
FROM
(VALUES ('Goal')) V(SeriesName)
ORDER BY V.SeriesName DESC
FOR JSON PATH
) AS [Lines.Series],
(
SELECT
V.SeriesName AS Label,
V.LinkAlias,
V.SalesId AS [PassingFields.SalesId],
(
SELECT
V.xValue,
V.yValue
FROM
(VALUES ('2019', 9001), ('2020', 11931), ('2021', 13203), ('2022', 8912), ('2023', 15412)) V(xValue, yValue)
FOR JSON PATH
) AS [Values]
FROM
(VALUES ('Sales', 'ChartLink', 1)) V(SeriesName, LinkAlias, SalesId)
ORDER BY V.SeriesName DESC
FOR JSON PATH
) AS [Bars.Series]
FOR JSON PATH
) AS Chart
KPIs are generated using JSON. Below you can see an example KPI with its corresponding JSON.
{
"Label": "Monthly earnings",
"Value": 56000,
"NumberOfDecimals": 0,
"Prefix": "$",
"Link": "KpiLinkAlias",
"PassingField": {
"KpiId": 5
},
"Trend": {
"Value": 15,
"Direction": "decreasing",
"Type": "negative",
"Unit": "%",
"NumberOfDecimals": 0,
"Period": "jan-feb"
}
}
Multiple KPIs can be shown side by side by putting them inside an array.
[{
// KPI properties
},
{
// KPI properties
}]
Value: The value displayed. Must be a valid decimal type. (mandatory)
Label: Label displayed above the KPI. (optional)
NumberOfDecimals: The number of decimals shown for the value. Defaults to 0. (optional)
Unit: Unit to display after the value. (optional)
Prefix: Prefix to display before the value. (optional)
Link: Alias of the link to follow when clicking the KPI. (optional)
PassingField: Object containing the link's passing fields as properties. (optional)
Trend: Trend object to signify changes since previous period. (optional)
Value: The value displayed. Must be a valid decimal type. (mandatory)
Prefix: Prefix to display before the value. (optional)
Unit: Unit to display after the value. (optional)
NumberOfDecimals: The number of decimals shown for the value. Defaults to 0. (optional)
Period: Text that indicates which time period the trend refers to. (optional)
Direction: The direction of the arrow preceding the value. Defaults to none. (optional)
Possible values |
---|
increasing |
decreasing |
none |
Type: Indicates whether the change is positive or negative by the color of the trend. Defaults to neutral. (optional)
Possible values |
---|
positive |
negative |
neutral |
The following query will produce the JSON used above.
SELECT
(
SELECT
'Monthly earnings' AS [Label],
56000 AS [Value],
'$' AS [Prefix],
0 AS [NumberOfDecimals],
-- 'KpiLinkAlias' AS [Link],
5 AS [PassingField.KpiId],
15 AS [Trend.Value],
'decreasing' AS [Trend.Direction],
'negative' AS [Trend.Type],
0 AS [Trend.NumberOfDecimals],
'%' AS [Trend.Unit],
'jan-feb' AS [Trend.Period]
FOR JSON PATH
) AS Kpi
Meters are generated using JSON. Below you can see an example Meter with its corresponding JSON.
{
"Value": 4200,
"Heading": "Daily earnings",
"Prefix": "$",
"NumberOfDecimals": 0,
"Link": "MeterCellLinkAlias",
"PassingField": {
MeterId: 1
},
"Intervals": [
{
"IntervalStart": 0,
"IntervalEnd": 1000,
"ColorName": "red",
"Tooltip": "This is bad for business."
},
{
"IntervalStart": 1000,
"IntervalEnd": 2000,
"ColorName": "yellow",
"Tooltip": "This can be tolerated."
},
{
"IntervalStart": 2000,
"IntervalEnd": 5000,
"ColorName": "green",
"Tooltip": "The business is thriving."
}
]
}
Multiple meters can be shown side by side by putting them inside an array.
[{
// Meter properties
},
{
// Meter properties
}]
Value: The value displayed. Must be a valid decimal type. (mandatory)
Heading: Heading displayed above the meter. (optional)
NumberOfDecimals: The number of decimals shown for the value. Defaults to 0. (optional)
Unit: Unit to display after the value. (optional)
Prefix: Prefix to display before the value. (optional)
Link: Alias of the link to follow when clicking the meter. (optional)
PassingField: Object containing the link's passing fields as properties. (optional)
Intervals: Intervals to be shown in the meter. (mandatory)
IntervalStart: The start of the interval, must be exactly the end of the pervious interval if any. Must be a valid decimal type. (mandatory)
IntervalEnd: The end of the interval. Must be a valid decimal type. (mandatory)
ColorName: The name of the interval color, mandatory if more than one interval is specified. If not specified a neutral color will be used. (optional)
Possible values |
---|
green |
yelllow |
red |
Tooltip: Tooltip for the interval. (optional)
The following query will produce the JSON used above.
;WITH Intervals AS
(
SELECT
0 AS IntervalStart,
1000 AS IntervalEnd,
'red' AS ColorName,
'This is bad for business.' AS Tooltip
UNION ALL
SELECT
1000 AS IntervalStart,
2000 AS IntervalEnd,
'yellow' AS ColorName,
'This can be tolerated.' AS Tooltip
UNION ALL
SELECT
2000 AS IntervalStart,
5000 AS IntervalEnd,
'green' AS ColorName,
'The business is thriving.' AS Tooltip
)
SELECT
(
SELECT
'Daily earnings' AS [Heading],
4200 AS [Value],
'$' AS [Prefix],
0 AS [NumberOfDecimals],
-- 'MeterCellLinkAlias' AS [Link],
5 AS [PassingField.MeterId],
(
SELECT
I.IntervalStart,
I.IntervalEnd,
I.ColorName,
I.Tooltip
FROM
Intervals I
FOR JSON PATH
) AS Intervals
FOR JSON PATH
) AS Meter
Allows you to validate the SQL parameters before any other SQL is run in the component. This call is only made if the SQL is a stored procedure and Validate parameters is checked.
SQL that can have several resultsets that are displayed at top of component.
The main title.
Whether the infobox should start expanded or collapsed. NULL/Omitted means default behavior, where all boxes are expanded on big screens, and only the first box is expanded on small screens.
Displays the link with the specified alias in the title row of the box.
The link should be of type "Top link (InfoSQL)".
Columns named PassingField_<xxx> will not be shown in the box and can be referenced from the link as a Column value with name <xxx>.
Only one BoxLink per box can be used.
Not shown in InfoSQL. The corresponding link should be of link type "Top link (InfoSQL)", "InfoSQL cell link" or "InfoSQL warning link", and one of its passing fields should have a value matching <xxx>, and be of type "Column value".
Used in conjunction with "TopLink" to mark it as a primary link. Only one link may be marked as primary.
Used in conjunction with "TopLink" to create an indicator on the top link with a corresponding number.
Similar to BadgeCount, but BadgeCountUrgent indicates number of items that need user action.
If BadgeCountUrgent is 0 or NULL then BadgeCount is used instead. If BadgeCountUrgent > BadgeCount then an error is raised.
Value displayed in the box. Its label will be taken from the field information whose name matches <colname>.
If the field information has Allow HTML enabled, then its content will be treated as HTML, though unsafe tags will be stripped and newlines are converted to <br>
tags. If Allow HTML is not enabled then the content will be treated as text.
If the value is NULL
, both value and label will be omitted.
Sets the text color of <colname> to the specified color. See Colors.
Color to use for the icon specified in <colname>_Icon. See Colors.
Recommended to use <colname>_CellLink instead for better tracking of links.
Supplies a link to the menu item with the specified alias when used in conjunction with <colname>.
Only one of <colname>_CellLink, <colname>_LinkId, <colname>_MenuItem or <colname>_MenuItemId can be used at the same time.
The id of a box table to display in the box.
JSON to generate a row of charts. Read more
JSON to generate a KPI. Read more
JSON to generate a row of meters. Read more
A QR Code will be rendered containing the text in the column.
To generate Swiss QR Code for digital payments, return an XML with the root attribute Type="Swiss". See example-XML in the documentation for the RTF Document component.
Embeds content from an external server as an iframe in the infobox. The URL must be an absolute URL.
Used together with the ExternalEmbedUrl column to set the height (in pixels) of the generated frame.
Deprecated. Use TitleIcon instead.
Displays an icon next to the box title.
Deprecated. Avoid using badge icons.
Override menu item badge.
Deprecated. Use TopLink/BoxLink instead.
Displays the specified link among the top links and in the title row of the box. The link will only appear in the title row if no ordinary columns lie before it in the resultset.
Columns named PassingField_<xxx> will not be shown in the box and can be referenced from the link as a Column value with name <xxx>.
Only one of TopLink, LinkId, MenuItem and MenuItemId can be used at the same time.
Multiple LinkId columns may appear in a single resultset.
Deprecated. Recommended to use TopLink/BoxLink instead for better tracking of links.
Displays a link to the menu item with this alias among the top links and in the title row of the box. The link will only appear in the title row if no ordinary columns lie before it in the resultset.
Only one of TopLink, LinkId, MenuItem and MenuItemId can be used at the same time.
Multiple MenuItem columns may appear in a single resultset.
Deprecated. Use TopLink/BoxLink instead.
Displays a link to the menu item with this id among the top links and in the title row of the box. The link will only appear in the title row if no ordinary columns lie before it in the resultset.
Only one of TopLink, LinkId, MenuItem and MenuItemId can be used at the same time.
Multiple MenuItemId columns may appear in a single resultset.
Deprecated. Use TopLink with a link label instead.
Used in combination with menuitem/menuitemid to give the navigator link a text that differs from the name of the menu item.
Deprecated. Additional information to menuitem/menuitemid, appends values to querystring (supports simple Softadmin® parameters).
If multiple passingfield columns exists, only the first one is used and the others are disregarded.
Deprecated. Use <colname>_CellLink instead.
Creates a cell link with the specified link id for the <colname> cell.
PassingField_<xxx> columns can be referenced from the link.
Only one of <colname>_CellLink, <colname>_LinkId, <colname>_MenuItem or <colname>_MenuItemId can be used at the same time.
Deprecated. Use <colname>_CellLink or <colname>_MenuItem instead.
Supplies a link to the menu item with the specified menuitemid when used in conjunction with <colname>.
Only one of <colname>_CellLink, <colname>_LinkId, <colname>_MenuItem or <colname>_MenuItemId can be used at the same time.
Supplies the querystring when used in conjunction with <colname>_MenuItemId.
These columns are deprecated. Use either PlainText, Html or SafeHtml instead, depending on what behavior you need.
The content of this column will be treated as Html, but line breaks and non-breaking spaces will be converted to br-tags. In future versions this column will be escaped.
Used to manally layout boxes in columns by inserting breaks in between boxes.
May not be used together with ColumnSpan.
If this contains a non NULL value, the following box will be placed in a new column in relation to the previous box when <N> columns fit on the screen.
If any box contains a column break for the current total number of columns, then no boxes will be layouted in columns automatically. This means that if "BreakOn3Columns" has been used, the boxes will be layouted as follows:
The alignment of grid columns and InfoSQL values.
Possible value | Description |
---|---|
center | Only applicable to grid columns. |
left | |
right |
Extended description for the field.
Possible value | Description |
---|---|
boolean checkbox | Legacy alias. Use "checkbox" instead. |
boolean dropdown | |
chart | |
checkbox | |
checkbox tree | |
colorpicker | |
date | |
datetime | |
dropdown | |
file | |
file upload area | |
heading | |
heading with checkbox | |
hidden | |
html | Legacy alias. Use "html editor" instead. |
html editor | |
info text | |
listbox | |
multi-autosearch | |
multi-listbox | |
multi-picker | |
multirow | |
password | |
picture | |
radio buttons | |
radio cards | |
signature | |
textarea | |
textbox | |
textbox with autosearch | |
textbox with autosuggest | |
textbox with dropdown | |
textbox with popup | |
time | |
uneditable text |
Possible value | Description |
---|---|
Default | Inherit layout from menu item. |
LabelAbove | Full width, label above. |
LabelLeft | Label to the left. |
NoLabel | Full width, no label. |
Standard | Deprecated. Use LabelLeft instead. |
JavaScript that controls the mandatory status of the field, this overwrites nullchoice if set. This is only available to control types for which the mandatory JavaScript field is visible in the user interface.
Possible value | Description |
---|---|
Hyperlink | |
MailToLink | |
PhoneLink |
Which direction the script is written in. Not to be confused with the CellAlignment property.
Possible value | Description |
---|---|
default | System default. Not useful unless you are trying to override an already explicit text direction on existing field information. |
ltr | Left-to-right (for example English) |
rtl | Right-to-left (for example Arabic) |
The width of the control.
At one point, this was a pixel value. Back when Softadmin used Verdana 10px, and before fields had width-categories. Now, it is just a value that is converted to a width category.
The possible values listed below are just suggestions. For example, both 1 and 30 will be converted to shortest, and both 500 and 9999 to longest.
Possible value | Description |
---|---|
150 | Medium-long |
30 | Shortest |
300 | Long |
500 | Longest |
60 | Short |
90 | Medium short |
See the "Box" resultset for documentation.
See the "Box" resultset for documentation.
See the "Box" resultset for documentation.
See the "Box" resultset documentation.
See the "Box" resultset for documentation.
See the "Box" resultset for documentation.
See the "Box" resultset for documentation.
Deprecated, Use TopLink instead.
See the "Box" resultset for documentation.
InfoSQL can declare JavaScript used by the menu item.
Example
SELECT
'thirdPartyApi.showMap(street, city, country)' AS JavaScript,
StreetAddress AS street,
CityName AS city,
CountryName AS country
FROM
...
The value of this column is not used and it's only purpose is to mark this as a timeline table. Only one of this and TimelineBelow may be used.
The value of this column is not used and it's only purpose is to mark this as a timeline table. Only one of this and Timeline may be used.
Use this column instead of "Timeline" to render the timeline below the info boxes.
Possible value | Description |
---|---|
Current | This is the current step. |
Done | This step has been completed successfully. |
Failed | Something went wrong in this step. |
Future | This step is later on in the process. |
Defines a table that may be referenced by the BoxTableIdReference column in the Box resultset to display the table in an infobox.
The id of the table, must be the first column in the table.
May contain different values for each row to define multiple tables.
The content to be shown in a table column. The formatting of the value is determined by the connected field information.
Sets the CSS style for the <colname> cell. Never use a string from a user as part of this column for security reasons.
Sets the CSS style for the entire row. Never use a string from a user as part of this column for security reasons.
Displays a heading for the row.
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'.
The stored procedure should be named <Schema>.<Table>_GetDetails
.